E-mail List Archives
From: glen walker
Date: Oct 13, 2021 4:50PM
- Next message: Peter Shikli: "Re: Section 508 testing_Reports"
- Previous message: Jon Gunderson: "Re: landmarks/regions"
- Next message in Thread: None
- Previous message in Thread: Jon Gunderson: "Re: landmarks/regions"
- View all messages in this Thread
Correct, Jon. You basically re-worded what I said last week (the
asterisk'ed section) but hopefully made it clearer.
On Wed, Oct 13, 2021 at 4:23 PM Jon Gunderson < <EMAIL REMOVED> >
> The header and footer elements only generate landmarks when they are in a
> certain contexts of a web page (e,g, scoped to body element), see ARIA
> Authoring Practices for more information on using HTML elements to create
> Guidance URL:
> Example URL:
> Another document that defines the roles of the the W3C ARIA in HTML
> document has specifications for the HEADER and FOOTER elements:
> Hope this helps,
> On Sat, Oct 9, 2021 at 4:14 PM glen walker < <EMAIL REMOVED> > wrote:
> > >
> > > What surprised me the most is that headers and footers were not
> > > automatically landmarks.
> > >
> > Just to clarify, the header and footer elements are absolutely (*)
> > roles by default. Now, whether the verbosity setting on your screen
> > is set to announce them is another issue but any tool you use to
> > all the landmarks will show the header and footer elements.
> > (*) Ok, maybe not "absolutely" because if a header or footer is a child
> > an article, aside, main, nav or section element, then the header or
> > does not have a role (https://w3c.github.io/html-aria/#el-header). I
> > don't
> > see that structure very often, though. Most scanning tools don't honor
> > spec even though the accessibility tree is correct (at least in Chrome
> > Firefox). That is, scanning tools will complain that there are two
> > landmarks if you have something like this:
> > <header>stuff</header>
> > <article><header>more stuff</header></article>
> > Even though the second header is marked as "role: HeaderAsNonLandmark" in
> > the a11y tree.
> > Keep preaching semantic html.