You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is about increasing the efficiency of use for keyboard users when tabbing through the toolbuttons container (e.g. the ones in the bottom right corner of the map of the sample app).
Currently the whole container is marked as role="toolbar". Due to the "toolbar" role, a screenreader user expects the following behavior (which is useful for all other keyboard users too):
The whole container (the one with role="toolbar") is focusable by tabbing onto it
As soon as the container is focused, the tools inside can be navigated through the arrow keys on keyboard. If a tool is disabled, it is skipped.
Pressing tab again, move the focus away from the toolbar over too the next focusable element (which is not a tool inside the container of course).
Please also consider a correct aria-orientation attribute with a value of either "horizontal" or "vertical", depending of the alignment of the toolbuttons.
Issue description
This issue is about increasing the efficiency of use for keyboard users when tabbing through the toolbuttons container (e.g. the ones in the bottom right corner of the map of the sample app).
Currently the whole container is marked as role="toolbar". Due to the "toolbar" role, a screenreader user expects the following behavior (which is useful for all other keyboard users too):
Example: https://www.w3.org/WAI/ARIA/apg/patterns/toolbar/examples/toolbar/
Please also consider a correct aria-orientation attribute with a value of either "horizontal" or "vertical", depending of the alignment of the toolbuttons.
Validations
The text was updated successfully, but these errors were encountered: