Improve how and what navigation block titles are communicating to screenreader users

Created on 9 April 2024, 9 months ago

Problem/Motivation

A follow up to πŸ“Œ Add Collapsed Status for Menu Block Title Active , I've noticed that the titles for navigation blocks cant receive focus when stepping (tabbing) through the navigation. since it is not focusable that structuring / wrapping element is unavailable for a user tabbing through the menu and is going announced/unnoticed to screenreaders in this context. the only cue and information are five headings (just looking at the activated titles for the default navigation blocks). the announcement in voiceover looks like this:

  • h3: Administrative toolbar content
  • h2: SHORTCUTS
  • heading level 4
  • h2: CONTENT
  • heading level 4
  • h2: ADMINiSTRATION
  • heading level 4
  • h3: Administrative toolbar footer
  • h4: RKOLLER

just based on the announcement it is not clear what shortcuts, content, administration, rkoller actually are, or better that shortcuts and the rest of the h2/h4 are actual navigation blocks. with the screenreader you are missing the visual context available to sighted users. about h4: RKOLLER, i would assume it is about my username but there is actually the top level menu item about help wrapped inside as well, therefore the username is inaccurate as a label for the two. In addition to that if the same pattern was followed as for the navigation blocks for the administrative toolbar content region rkoller would have to have h2 instead of h4.
it also has to be noted that there are three empty visually hidden h4 elements. and in general there is no consecutive way getting an announcement of the different parts of the navigation in consecutive order due to the fact that you have headings, and the top level menu items either being buttons (with submenu) or links (without submenu), you have to let voiceover start reading the entire page in consecutive order with (VO-A) to get all parts in context.

Proposed resolution

  • i wonder if it would make sense to append "navigation block" or "nav block" to each headline of an navigation block. by appending you have still the name frontloaded and the user is able to jump off at any time but in case the overall context is needed the user is able to keep listening. and example would be "Shortcuts navigation block" or "Shortcuts nav block"
  • In case the empty visually hidden h4 have no real purpose they might get simply removed?
  • Changing the heading level from h4 to h2 for the user?
  • Instead of using the username as a label use the actual label used on /admin/config/user-interface/navigation-block . so in my case the label would change from rkoller to user navigation block / or user nav block

if there is a proper technical way to announce also the navigation block title when for example tabbing through the navigation i am not sure since the title is only informational without any interactive aspect (neither a button, link or fieldset). not sure if anyone else might know an elegant way?

πŸ“Œ Task
Status

Active

Version

1.0

Component
NavigationΒ  β†’

Last updated about 19 hours ago

No maintainer
Created by

πŸ‡©πŸ‡ͺGermany rkoller NΓΌrnberg, Germany

Live updates comments and jobs are added and updated live.
  • Accessibility

    It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.

Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024