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

Disclosure widget accessibility issues #371

Open
aardrian opened this issue May 18, 2024 · 0 comments
Open

Disclosure widget accessibility issues #371

aardrian opened this issue May 18, 2024 · 0 comments
Labels

Comments

@aardrian
Copy link

Using the Accessibility page from the latest (2023) survey, the disclosure widgets under Accessibility Pain Points have a few problems.

  1. They do not have an aria-expanded attribute to programmatically convey their state.
  2. Their accessible name changes when activated.
  3. Their focus styles do not match their hover styles (definitely in Firefox).

For item 1, I encourage you to use aria-expanded with true when expanded and false when collapsed. This will convey to screen reader users whether new content has been exposed or not. If you are unfamiliar with how disclosure widgets are exposed to screen readers, I have a video using JAWS / Chrome showing it in action.

For item 2, the accName changes from "+7" (or similar) to "-" (announced "hyphen" or "dash"). This change may not be communicated, or it may be communicated and then a voice user has an extra challenge while a screen reader user may not understand the context.

For item 3, I don't see a :hover selector, and so I am worried this is managed by JS. In Firefox, the only visual cue is the default browser focus indicator, which passes WCAG (on a technicality) but is essentially useless as a visual cue. There is no reason to leave Firefox and keyboard users in particular with an inadequate interface, particularly if this is the simple CSS fix I expect it would be.

@SachaG SachaG added the a11y label May 20, 2024
SachaG pushed a commit that referenced this issue May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants