feat(a11y): keyboard-activatable table rows, live announcements, skip link - #319
Merged
Conversation
… link - Clickable table rows (issues, issue events, transactions) gain tabindex + Enter/Space activation via a shared rowKeyActivate helper and a visible focus outline - Screen-reader live regions announce loaded counts on the four data pages - Skip-to-content link in the dashboard shell; main landmark gets an id - Hamburger touch target raised to 44px; issue counts use tabular-nums
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
tabindex+ Enter/Space via a sharedrowKeyActivatehelper, plus a visible focus outline on the focused rowrole=status) announce loaded record counts on issues, transactions, release-health, and issue detail#main-contentlandmark)tabular-numsWhy
Rows were mouse-only (clickable
trwith no keyboard path) — keyboard and screen-reader users could not open issues or transactions. The mobile menu focus-trap concern was already solved by the Sheet in #317; this closes the remaining known a11y gaps.Testing
npm run check(0 errors),npm run build, unit tests 10/10, Playwright 16/16