themesberg / themesberg/flowbite
sticky navbar example not in tab order
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 9.4k
- Forks
- 862
- PR merge metrics
- No merged PRs in 30d
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the sticky navbar example and reproduce the issue by moving through its navigation with the Tab key. Check that focus proceeds from the logo through the center navigation items and then the “get started” button in left-to-right order; the issue is done when the tab sequence is logical for keyboard-only users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, tailwindcss
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100