W3C home > Mailing lists > Public > public-html-comments@w3.org > October 2015

Re: FOOTER and HEADER elements defined as landmarks in HTML5

From: Martin Janecke <w3.org@prlbr.com>
Date: Fri, 2 Oct 2015 22:10:25 +0200
To: public-html-comments@w3.org
Message-ID: <560EE4B1.5090003@prlbr.com>

I agree that something should to be tweaked here. The HTML spec suggests 
to use the header element to group taglines etc. with a heading.[1] To 
me, the examples suggest that this is both applicable for site-specific 
banner-like headings and page-specific/article-specific headings.

That is what I use the header element for and it's usually with the main 
heading for the page – i.e. page-specific, not site-specific – and 
outside section or article elements.[2]

I do not have an opinion (yet) whether the association with the landmark 
role should be changed or the recommendation to use the header element 
for grouping headings with taglines etc. But I think that keeping both 
as they are now would be a problem.


[1]: See 
[2]: Two examples:

On 02.10.15 17:46, Steve Faulkner wrote:
> Hi Jon,
> I agree, from looking at usage of the elements that map to landmark
> roles, that some tweaking is needed (main usage being the least
> problematic by far, from recent data anaylisis 98% of pages using <main>
> use 1)
> Can you provide some idea of the logic for such restrictions to be
> implemented in browsers?
> for example
> "only the first header in DOM scoped to the body is mapped to banner"
> "only the last footer in DOM is mapped to contentinfo"
> Would these result an acceptable majority of use being covered?
> here are some example pages conatining header and footer
> http://www.html5accessibility.com/HTML5data/header-footer/index-all.html
> --
> Regards
> SteveF
> Current Standards Work @W3C
> <http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>
> On 1 October 2015 at 17:06, Gunderson, Jon R <jongund@illinois.edu
> <mailto:jongund@illinois.edu>> wrote:
>     Steve,
>     I would like to file an issue with the current API mappings for the
>     HEADER and FOOTER.
>     Right now they will be defined as a BANNER or CONTENTINFO landmarks,
>     except when they are descendants of ARTICLE or SECTION elements.
>     http://www.w3.org/TR/html-aapi/
>     I am curious why other sectioning elements like ASIDE, MAIN and
>     NAVIGATION were not also included.
>     My main concern is that many people use the HEADER and FOOTER
>     elements outside of ARTICLE and SECTION elements, and I don’t think
>     they mean to create BANNER and CONTENTNFO landmarks.
>     Typically a page only needs at most one of BANNER and CONTENTINFO
>     landmarks, so I think it should be harder to make them automatically
>     using the HEADER and FOOTER elements.
>     We have a set of rules related to BANNER and CONTENTINFO landmarks:
>      1. Must be top level landmark
>      2. Only one
>      3. Restriction of what can be in the landmarks
>     Rule Details:
>     http://fae20.cita.illinois.edu/rulesets/rc/#id_h3_ID_LANDMARKS
>     Look forward to your response,
>     Jon
Received on Friday, 2 October 2015 20:10:52 UTC

This archive was generated by hypermail 2.3.1 : Friday, 2 October 2015 20:10:52 UTC