E-mail List Archives
Re: Landmarks structures
From: Birkir R. Gunnarsson
Date: Apr 21, 2020 8:42PM
- Next message: Birkir R. Gunnarsson: "Re: sortable table/grid"
- Previous message: Murphy, Sean: "Re: Landmarks structures"
- Next message in Thread: Steve Green: "Re: Landmarks structures"
- Previous message in Thread: Murphy, Sean: "Re: Landmarks structures"
- View all messages in this Thread
<header> and <footer> elements map to banner/contentinfo roles when
they are children of the <body> element.
If, however, they are used inside <article> or <section> elements they
should not map to those landmarks, they mark the header/footer of that
region/article.
This definition is not consistent with how some screen readers treat
them, which is confusing.
I fail to grasp the argument for multiple or nested banner and
contentinfo landmarks on pages, the banner represents the page header,
contentinfo the page footer, there should only be one.
Yes, you could have a page with nested pages (e.g. iframes and such),,
particularly in crazy web design like social media sites, but I won't
allow it for standard pages and make sure it gets called out as a
fail.
For landmarks to be useful they need to be used systematically,
consistently and sparingly.
The <main> element does not count as a structural element in HTML5, I
can't remember why, but I had to look all over the HTML5 spec to find
it.
On 4/21/20, Murphy, Sean < <EMAIL REMOVED> > wrote:
> I agree with the statement of screen reader users not knowing how to
> navigate web pages effectively. Is it training or people getting used to how
> to do something and don't explore a different way, or not understanding the
> terminology being used. As this does get confusing for some.
>
> What I am struggling with is code testing tools like Ark and Axe reporting
> the use of nested banners (headers) and footers, Navs etc as failures based
> upon best practise. This W3C document which I am not sure is the latest
> version https://www.w3.org/TR/html53/sections.html does not indicate this at
> all. All the examples I have reviewed contained in the document supports the
> use of headers and navs inside articles and asides. I did not see any
> mention about the main section which supports Steev's comments. So I am
> wondering if this is the formal release of the HTMl 5 specs and how people
> came up with the best practise?
>
> Note: The document does mention sections become regions if you apply
> aria-label in an indirect way. The use of aria-label on article does not
> change it into a region from reading the above document.
>
>
>
>
> Sean Murphy | Digital System specialist (Accessibility)
> Telstra Digital Channels | Digital Systems
> Mobile: 0405 129 739 | Desk: (02) 9866-7917
>
>
- Next message: Birkir R. Gunnarsson: "Re: sortable table/grid"
- Previous message: Murphy, Sean: "Re: Landmarks structures"
- Next message in Thread: Steve Green: "Re: Landmarks structures"
- Previous message in Thread: Murphy, Sean: "Re: Landmarks structures"
- View all messages in this Thread