Repository navigation
Make Navbar keyboard and screen-reader accessible #1973
Description
Problem
src/components/Navbar.tsx (898 lines) is untested, and nothing asserts its interactive elements are reachable by keyboard or announced correctly.
An interactive element that only responds to a mouse is unusable for keyboard and screen-reader users, and this is invisible to a visual review.
Scope
Add the missing coverage for src/components/Navbar.tsx. Do not change its behaviour unless a test proves it wrong.
Acceptance criteria
- Every interactive element is reachable by Tab in a sensible order
- Focus is visible at each stop
- Controls expose an accessible name
- Any state change that matters is announced
Validation
New tests beside the file. pnpm test passes.
Activity
rupesh-kumar-sah commentedon Oct 18, 2026
Hi maintainers,
I reviewed "Make
Navbarkeyboard and screen-reader accessible" and have a structured approach ready for implementation:I have reviewed the problem description and acceptance criteria for this issue. I have a clear, tested implementation ready with defensive error handling and 100% green CI proof.
I will deliver a clean, well-tested, and production-ready PR promptly upon assignment. Kindly assign this issue to me.
Thank you!
muokwejosh-cloud commentedon Oct 19, 2026
@muokwejosh-cloud has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @muokwejosh-cloud to this issue.
Songu3020 commentedon Oct 19, 2026
@Songu3020 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Songu3020 to this issue.
Jagadeeshftw commentedon Oct 19, 2026
@muokwejosh-cloud, this one is yours. Good luck!
Do read the complete description; the PR needs to cover every requirement and acceptance criterion listed. Please submit a quality PR with tests.
Please open the PR within 48 hours or you may be unassigned to free the issue up.
Join the Telegram group if you haven't already: https://t.me/+u5qmu35nZ7I0OTU1
drips-wave commentedon Oct 19, 2026
Congratulations, @muokwejosh-cloud! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @muokwejosh-cloud: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
feat(navbar): make Navbar keyboard and screen-reader accessible (#1973)…
grantfox-oss commentedon Oct 22, 2026
🎉 This issue has been marked as completed on GrantFox!
@muokwejosh-cloud's PR #2031 was approved and merged by @Jagadeeshftw.
🏆 @muokwejosh-cloud: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,252 total points). Track your full progress on GrantFox.
👏 Great work, @muokwejosh-cloud! Keep contributing to Fluxora-Org.
drips-wave commentedon Oct 22, 2026
This issue has been completed by @muokwejosh-cloud as part of the Stellar Wave Program's 10th Wave 🥳
😎 @muokwejosh-cloud: You earned 100 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.