-
-
Notifications
You must be signed in to change notification settings - Fork 232
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
Bug: Improve accessibility of sidebar navigation #4185
Comments
Thanks for the issue, our team will look into it as soon as possible! If you would like to work on this issue, please wait for us to decide if it's ready. The issue will be ready to work on once we remove the "needs triage" label. To claim an issue that does not have the "needs triage" label, please leave a comment that says ".take". If you have any questions, please comment on this issue. For full info on how to contribute, please check out our contributors guide. |
Would you like to with in this @CorinaMurg ? If so, feel free to |
The issue you are trying to assign yourself is blocked until it can be triaged or by another label on the issue. |
1 similar comment
The issue you are trying to assign yourself is blocked until it can be triaged or by another label on the issue. |
The issue you are trying to assign yourself is blocked until it can be triaged or by another label on the issue. |
.take |
…ans with aria-hidden wrap lucide icons (used for open and close sidebar buttons) in spans with aria-hidden fix open-sauced#4185
… button of sidebar navigation fix open-sauced#4185
Describe the bug
The sidebar navigation and its toggle button have accessibility issues that affect keyboard and screen reader users:
aria-expanded
attribute to convey to screen reader users that activating the button will open a menuThese are fixes that will allow keyboard and screen reader users access the button. There are a few other issues affecting elements inside the navigation and should be part of another ticket.
Steps to reproduce
https://app.opensauced.pizza/
. If already on the page, just refresh.tab
until you reach the navigation button. (Testing with a screen reader will announce the button just as "button".)Enter
to activate the button and open the menu. (The screen reader will not announce anything, so the user does not know that the navigation menu is open)tab
again. The focus will go to theCreate Insights
button on the main page, and not inside the navigation.The text was updated successfully, but these errors were encountered: