-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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
Try to improve a11y for the "button groups" in the SecondaryToolbar/Sidebar (issue 14526) #14554
Conversation
bb1276e
to
17276fe
Compare
Were you able to test this with a screen reader or the a11y tree in Firefox? |
Well, I've got no screen-reader unfortunately. |
4a3cfa2
to
3225757
Compare
/botio-linux preview |
From: Bot.io (Linux m4)ReceivedCommand cmd_preview from @Snuffleupagus received. Current queue size: 0 Live output at: http://54.241.84.105:8877/d6b1fac070aeff2/output.txt |
From: Bot.io (Linux m4)SuccessFull output at http://54.241.84.105:8877/d6b1fac070aeff2/output.txt Total script time: 2.61 mins Published |
@seahawksq Please check if the preview above is enough to address the issue! |
@jcsteh maybe you can help here? |
…idebar (issue 14526) *Please note:* I don't really know anything about a11y, hence it's possible that this patch either doesn't work correctly or at least isn't a complete solution. In both the SecondaryToolbar and the Sidebar we have "button groups" that functionally acts essentially like radio-buttons. Based on skimming through [this MDN article](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/radio_role) it thus appears that we should tag them as such, using `role="radiogroup"` and `role="radio"`, and then utilize the `aria-checked` attribute to indicate to a11y software which button is currently active.
3225757
to
d65169d
Compare
Looks like this fixes the issue Here's the output of NVDA: Before:
After:
|
It has been fixed, thanks for the quick turnaround! |
Please note: I don't really know anything about a11y, hence it's possible that this patch either doesn't work correctly or at least isn't a complete solution.
In both the SecondaryToolbar and the Sidebar we have "button groups" that functionally acts essentially like radio-buttons. Based on skimming through this MDN article it thus appears that we should tag them as such, using
role="radiogroup"
androle="radio"
, and then utilize thearia-checked
attribute to indicate to a11y software which button is currently active.