WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Visibly hidden headings to label regions and landmarks

for

From: Birkir R. Gunnarsson
Date: Sep 1, 2020 5:49PM

Technically, landmarks and headings are two different things:
* A landmark describes areas of the page (or screen), regardless of content
* A heading labels and describes the structure of the content on the page
Ideally users should be able to navigate successfully by either.
Unfortunately, labeled regions are spoken in context of navigation,
thus making heading navigation irritatingly verbose.

Keep in mind that landmarks only need accessible names if there are
multiple instances of the same landmark region on the page (banner,
main and contentinfo should never have an accessible name).

There is no strong WCAG SC that governs this scenario, (other than
4.1.2 if a landmark region requires an accessible name, you can look
that up in the landmark roles section of the ARIA spec).
It's been a 12-hour day so I just can't bother looking it up in the
spec today, though I might be able to muster up the courage tomorrow.
For each role definition, look in the characteristics table at the
bottom of the definition and see if it has an accessible name required
entry.


On 9/1/20, Murphy, Sean < <EMAIL REMOVED> > wrote:
> From a screen reader point of view. I see this as screen noise. If I have a
> region with the exact name as the heading, which is the next line. Then
> there is no added value due to both elements are page section components.
> This is over usage of aria when it is not required.
>
>
> If it actually fails a SC. This time of morning, I cannot recall our
> internal discussions on this point. As we have had them. My guidance is to
> use one or the other. As you don't need to have headings on a page if they
> are visually design that way. If you have headings visually designed, then
> you don't need the region section.
>
> Sean
>
> 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
> Vaibhav Saraf
> Sent: Wednesday, 2 September 2020 3:47 AM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: [WebAIM] Visibly hidden headings to label regions and landmarks
>
> [External Email] This email was sent from outside the organisation – be
> cautious, particularly with links and attachments.
>
> Hi Everyone,
>
> I have observed that many of the developers associate the visibly hidden
> headings with the page regions mostly with the use of aria-labelled-by
> attribute. So they will be announced to the screen reader as, for instance,
> navigation landmark (+) heading label (+) heading level. Many of the
> Google's websites extensively use this approach.
>
> I have also seen another implementation where the first element inside a
> region is a visibly hidden heading. They aren'y programmatically associated
> in the case. They work exactly the same with NVDA and JAWS as in the first
> case. My friend told me that this approach will face badly with VoiceOver, I
> have never used VO so seeking information about the same.
>
> How well is the thought of providing the label as a heading, what I prefer
> is that labelling should be done using 'aria-label' attribute and headings
> probably should be available to all. However this approach looks good as
> long it serves a pleasant experience to most combinations of browser and
> SRs.In my understanding WCAG has no direct emphasis around the topic I want
> to discuss or probably I am not able to understand it. I seek your opinion
> about the scenario.
>
> Thanks,
> Vaibhav
> > > http://webaim.org/discussion/archives
> > > > > >


--
Work hard. Have fun. Make history.