CODEWITHSUNDEEP
htmlaccessibilitywai-ariasemantic-markupoutliner
natevw
natevw

Reputation: 17902

What's the best way to provide alternate headings for purposes of screen reader navigation?

I have been tasked with marking up a document whose visual headings have been authored something like:

My concern is that the way the headings are worded will make them tedious to navigate via screen reader. For example if I want to jump to the "impressionist movement" section I will have to listen to lots of repeated "XY within fine arts results" prefixes ahead of the actual info distinguishing each heading from the other.

This is not my content and I am not allowed to change the headings, nor will the authors. However, I have been given permission to adjust the markup so as to present a modified semantic "outline" view that differs from the visual one. Feedback welcome, but I think an outline like the following would be more useful to someone navigating by screen reader:

My question is, how do I accomplish this in a way that real-world screenreading utilities will pick up?

If I simply take each heading like:

<h4>Fine arts sector progress at XYZ within the impressionist movement</h4>

And add an aria-label with the shortened version like:

<h4 aria-label="impressionist movement">Fine arts sector progress at XYZ within the impressionist movement</h4>

Will that be an effective and appropriate solution? Is there a way I can test the results using something built into the OS like VoiceOver or ChromeVox, or do the paid utilities like JAWS behave quite a bit differently in this regard?

Upvotes: 1

Views: 619

Answers (2)

xzap
xzap

Reputation: 65

I would avoid making too many assumptions about the content that screen reader users want to read, as the aim of accessibility is to provide an equivalent user experience for people with disabilities (according to the W3C).

Given that the wordy content is the core issue, the ideal thing would be to fix that, ideally backed up by research including people with disabilities. If this is outside your remit then keeping the content the same for all users is likely to reduce confusion.

People who use screen readers still scan over content they're not interested in the same way as sighted users can, it's just with the help of technology. This article by Léonie Watson talks more about letting screen reader users decide what's important.

Upvotes: 1

slugolicious
slugolicious

Reputation: 17475

From a basic user experience (UX) perspective, you typically want to put the most important information first so that users can quickly scan the text and find what they need. Your example of finding "impressionist movement" is difficult even from a sighted perspective. My eyes have to scan the beginning of the text and sort of "filter" it out until I get to the text that is important, which is near the end of each heading. I find your second outline much easier to read/scan.

That same concept applies for screen reader users too. If they can hear the important text first, then they can quickly move on if the text isn't what they're looking for.

Screen readers users can quickly jump to various heading levels. If I knew that "impressionist movement" was heading level 4, <h4>, then I could press the 4 key to jump to the next heading level 4 so I wouldn't have to slog through every heading. That helps but I would still have to listen to the same repeated text at the beginning of the heading before I heard the important part at the end.

aria-label works best when used on interactive elements, not static text. You'd have to test on a variety of screen readers to see if it is honored on headings. There's a "Practical Support for aria-label" document on the W3.org website that mentions that aria-label might not be honored for headings.

  • Don't use aria-label or aria-labelledby on any heading elements because it overrides them on NVDA, VoiceOver and Talkback. JAWS ignores them.

If you want to go the route of providing alternative text for the heading, a better way would be to use visibly hidden screen reader text. This is done by defining a CSS class that fakes out the browser into not displaying the text but the text is really there so a screen reader user can still hear it. You can call the CSS class anything you want but a common name to use is sr-only. You can see a definition of that class at What is sr-only in Bootstrap 3?. (You don't have to use bootstrap to get that class. Just copy the CSS from that article.)

So your code would have the current visible text from your first outline but you'd hide that text from screen readers via aria-hidden and then you'd have visibly hidden text that the sighted user can't see but the screen reader can. It would look something like this:

<h4>
  <span aria-hidden="true">Fine arts sector progress at XYZ within the impressionist movement</span>
  <span class="sr-only">impressionist movement</span>
</h4>

Upvotes: 2

Related Questions