fix: Make Toolbar and Menu Buttons Keyboard Accessible #5114
+862
−629
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issue:
Fixes #5113
Description:
This Pull Request addresses a significant accessibility barrier in the Music Blocks application. Many interactive elements in the main toolbar, auxiliary toolbar, and dropdown menus were implemented using
<a>tags withouthrefattributes. This prevented keyboard users from focusing on or activating these elements.Changes:
role="button"to all identified<a>tags that function as buttons.tabindex="0"to these same tags to make them focusable via the keyboard sequence.index.htmlusing Prettier for consistent code style.Affected Areas:
How to Test:
Tabkey repeatedly to navigate through the toolbar items.