Navbar accessibility for keyboard users
See original GitHub issueCurrent Behavior Keyboard users can’t access the dropdown menu on the navbar. They can only be accessed when they are hover.
Desired Behavior They should have have access to those drop down menus.
Screenshots / Mockups
The dropdown menu is only available to mouse users.
Alternatives
Contributor Resources
The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master
branch.
- See contributing instructions
- See Layer5 site designs in this Figma project. Fill-in the Layer5 Community Member Form and join the Layer5 Community Slack for access.
Issue Analytics
- State:
- Created a year ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Keyboard Accessibility - WebAIM
Keyboard accessibility is one of the most important aspects of web accessibility. Many users with motor disabilities rely on a keyboard.
Read more >Keyboard Compatibility | Web Accessibility Initiative (WAI) - W3C
All functionality must be usable with the keyboard. That is, users can access and move between links, buttons, forms, and other controls using...
Read more >Keyboard-Only Navigation for Improved Accessibility
Keyboard users must be able to access all interactive elements, not just the main navigation or in-line links. This means that form elements, ......
Read more >Web Accessibility Criteria - Keyboard Accessibility
Keyboard accessibility is critical to ensure all users have access to information without requiring a mouse. To be keyboard accessible a web page...
Read more >Keyboard accessibility - University of Washington
Keyboard accessibility problems arise on websites when designers or developers use techniques that break standard keyboard functionality. The Techniques page ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Olaleye-Blessing @leecalcote I would love to work on this issue, can I take this up 😃
We can live with the accessibility, no need for this much granularity.