Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] a11y: header section - Menu label is verbose - Short description of the bug #2074

Open
GoCHacpie opened this issue Aug 16, 2022 · 1 comment

Comments

@GoCHacpie
Copy link

GoCHacpie commented Aug 16, 2022

Required information

Describe the bug
[Issue]
When focus moves on the Menu button, screen reader announces the instructions to access the menu items. There is no need to provide the access instructions as the provided keyboard support is standard and known to assistive technology users.

Also the escape key does not close menu as required for keyboard accessibility

[User Impact]
Overly verbose labels are often annoying to screen reader users.

[Code Reference]
Main Menu

[Recommendation]
Remove aria-label used on the element. An inner text for button, "Main menu" is sufficient to access the menu.

Not an accessibility failure. More of a accessibility-usability experience issue.
Severity: 2/10

To Reproduce
Steps to reproduce the behaviour:

  1. Turn on screen reader NVDA with Chrome/Windows and navigate with keyboard Tab key to Menu button'
  2. Listen to super lengthy announcement. Screen reader user must listen to this lengthy announcement everytime that navigate in the menu.

Expected behaviour
recommended use of short label = "Main menu"

Who shall do the work?
not sure.

Additional information (optional)

Version of WET-BOEW/GCWeb you are using
e.g. v4.0.36

Desktop/Smartphone (please complete the following information)
Browser chrome/firefox/safari/edge

Screenshots
If applicable, add screenshots to help explain the bug.
image

Additional context
2 corporate accessibility consultants recommend keeping expandable menu button label simple. However, if this long explanation text was added due to a usability study and an explicit request to add, then keep. This would be surprising though.

The Menu should be able to close with ESC key though for Keyboard accessibily and WCAG compliance

@ghost
Copy link

ghost commented Sep 21, 2022

This be more suited over at https://github.com/wet-boew/GCWeb. @duboisp should be able to transfer it over.

I am just a volunteer on this GitHub project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
WCAG 2.1 Level AA review
  
Awaiting triage
Status: No status
Development

No branches or pull requests

2 participants