Describe the bug
The sticky navbar example has a WCAG 2.1 accessibility violation where the tab order of nav items is not in logical order. It tabs from the logo to the "get started" button and then back to the center nav items. The order should go from left to right in order to provide a better experience for keyboard only users
To Reproduce
Steps to reproduce the behavior:
Go to sticky navbar component
use tab key across all nav items
tab focus goes from logo to "get started" button
See error
Expected behavior
tab order goes left to right across all nav items
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: [e.g. iOS]
Browser chrome
Version [e.g. 22]
Smartphone (please complete the following information):
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional context
I wasn't sure where exactly to put this. It's an accessibility bug, but in reality it's a documentation issue with your examples. If this is the wrong area please advice me on where to create tickets like this in the future. Thanks
Describe the bug The sticky navbar example has a WCAG 2.1 accessibility violation where the tab order of nav items is not in logical order. It tabs from the logo to the "get started" button and then back to the center nav items. The order should go from left to right in order to provide a better experience for keyboard only users
To Reproduce Steps to reproduce the behavior:
Expected behavior tab order goes left to right across all nav items
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context I wasn't sure where exactly to put this. It's an accessibility bug, but in reality it's a documentation issue with your examples. If this is the wrong area please advice me on where to create tickets like this in the future. Thanks