fix: improve dashboard header keyboard navigation#1987
Conversation
|
@Namratha36 is attempting to deploy a commit to the PRIYANSHU DOSHI's projects Team on Vercel. A member of the Team first needs to authorize it. |
GSSoC Label Checklist 🏷️@Priyanshu-byte-coder — please apply the appropriate labels before merging: Difficulty (pick one):
Quality (optional):
Validation (required to score):
|
There was a problem hiding this comment.
Thanks for your first PR on DevTrack! 🎉
A maintainer will review it within 48 hours. While you wait:
- Make sure CI is passing (type-check + lint)
- Double-check the PR description is filled out and the issue is linked
- Feel free to ask questions in Discussions if you need help
If you find DevTrack useful, a ⭐ star on the repo is always appreciated — it helps the project grow and attract more contributors!
c17643e
into
Priyanshu-byte-coder:main
|
🎉 Merged! Thanks for contributing to DevTrack. If the project has been useful to you, a ⭐ star on the repo is the easiest way to support it — it helps DevTrack get discovered by more developers. Keep an eye on open issues for your next contribution! |
Summary
Improved keyboard accessibility in the dashboard header by removing an unnecessary explicit
tabIndex={0}from the GitHub profile avatar link.Anchor elements with a valid
hrefare already keyboard focusable by default, so the explicit tabindex was redundant. This change preserves the natural DOM focus order and relies on native browser behavior.Closes #1074
Type of Change
Changes Made
tabIndex={0}fromUserAvatar.tsxHow to Test
Checklist
npm run lintpasses locallyAccessibility