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

Button doesn't communicate danger state to screen reader users #8220

Closed
dakahn opened this issue Mar 30, 2021 · 1 comment · Fixed by #8222
Closed

Button doesn't communicate danger state to screen reader users #8220

dakahn opened this issue Mar 30, 2021 · 1 comment · Fixed by #8222

Comments

@dakahn
Copy link
Contributor

dakahn commented Mar 30, 2021

image

If the danger state is important visual information that calls warning to potentially destructive or irreversible processes/actions we need to communicate that to our screen reader users as well.

This can be done a few ways, but off the top of my head I might try adding a visually hidden span with a unique id that can be referenced in an aria-describedby attribute on the button itself something like this perhaps

image

@dakahn dakahn changed the title Button's don't communicate danger state to screen reader users Buttons don't communicate danger state to screen reader users Mar 30, 2021
@dakahn dakahn changed the title Buttons don't communicate danger state to screen reader users Button doesn't communicate danger state to screen reader users Mar 30, 2021
@joshblack
Copy link
Contributor

@dakahn is there a good rule to cite for this requirement from WCAG?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants