WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: The importance of landmarks to screen readers?

for

From: Murphy, Sean
Date: Apr 1, 2021 4:07PM


All,

Very interesting discussion. The standards for HTMl5.2 really make some of the different type of sections (regions) such as header, footer and main fairly clear from a document structure view. EG: the main must be a child of the body. While footer and header can be a child of the body or the main. From memory Nav is not so clear. They do provide good guidelines on usage. They do provide code examples as well. I haven't seen any conversation or references related to the standards here. The standards also discuss ARIA usage.

From a practical and user point of view. The average screen reader user on desktop I do not think knows the concept of regions. Thus they don't use them. I would have to double check mobile, but I don't think you can navigate by regions on voiceover or talkback. I have seen web sites which over use landmark regions. Thus the page becomes very noisy for the screen reader user.

The core principle of what a region function is over a header I think is the key to the confusion. I see a region of a means of grouping a common components or information together. If you have 10 product cards for example. Then a <section aria-label="Product cards"> would be a means of assisting the user to understand the structure of the page. Then the headers within the section can break up each product. This is a good usage of a section.

The HTML 5 standards are not the easiest to read and hence, leads to confusion.

Regards
Sean Murphy

Sean Murphy | Senior Digital System specialist (Accessibility)
Telstra Digital Channels | Digital Systems
Mobile: 0405 129 739 | Desk: (02) 9866-7917
Digital Systems Launch Page
Accessibility Single source of Truth

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Peter Weil
Sent: Thursday, 1 April 2021 1:45 AM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] The importance of landmarks to screen readers?

[External Email] This email was sent from outside the organisation – be cautious, particularly with links and attachments.

There's also a really good ongoing discussion about this entire issue, with links to related discussions:

https://github.com/w3c/html-aam/issues/86#issue-221936168

It sounds as though they're moving towards restricting mapping <aside> to complementary under certain circumstances (among other things), so that it's not always a landmark. And also allowing <aside> as a landmark within <main>. But the specs, the best practices, the guidelines, the examples, etc., all need to be brought into alignment.

Peter


On 3/30/21, 10:23 AM, "WebAIM-Forum" < <EMAIL REMOVED> > wrote:

The best place to get an official decision from the Accessibility Guidelines working group on a situation that is not already documented in materials is to log a github issue at: https://github.com/w3c/wcag/issues

This isn't a legal source but it's the best place we have now on what the group that created WCAG has come to consensus on.

Jonathan