WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: Visibly hidden headings to label regions and landmarks


Number of posts in this thread: 1 (In chronological order)

From: barry.hill3@sky.com
Date: Wed, Nov 25 2020 7:28AM
Subject: Visibly hidden headings to label regions and landmarks
No previous message | No next message

I thought that use of hidden elements should be avoided as much as possible
and Aria should be a last resort if semantic mark-up cannot be used.
Personally, as a screen reader user, I prefer headings to be used only for
content structure.



-----Original Message-----
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of
Vaibhav Saraf
Sent: 01 September 2020 6:47 PM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: [WebAIM] Visibly hidden headings to label regions and landmarks

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.