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
The navigation links currently are not accessible for either keyboard-only users or screen reader users. They can be made accessible by including a url in an href attribute. (Update: given current recommendations, it might make the most sense to make the items buttons so that they are keyboard accessible- see discussion below)
In the mobile layout, the navigation is accessed as a menu. The dropdown behavior pattern that I think makes sense here currently isn't implemented anywhere yet. I included comments about similar behavior in the PRs for context selector and select components, but maybe it would make sense to have a quick chat with everyone to understand if there's a simpler way to handle this interaction so that it can be easily reused across the different components?
hrefattribute. (Update: given current recommendations, it might make the most sense to make the items buttons so that they are keyboard accessible- see discussion below)