-
Notifications
You must be signed in to change notification settings - Fork 0
🎨 Palette: Accessibility & Keyboard Navigation Improvements #23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Gamepulse
wants to merge
1
commit into
Dev
Choose a base branch
from
palette/ux-accessibility-improvements-2206975824834784227
base: Dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,3 @@ | ||
| ## 2026-05-05 - [Accessibility & Keyboard Navigation in Card-based UIs] | ||
| **Learning:** Interactive cards that contain nested buttons (like tags, status badges) require careful event management. Using `tabIndex={0}` on the container makes it keyboard-accessible, but an `onKeyDown` handler must use `if (e.target !== e.currentTarget) return;` to prevent the card's primary action (navigation) from firing when a nested interactive element is activated. Semantic `<button>` elements should always be preferred over `<span role="button">` to ensure consistent screen reader behavior and native keyboard support. | ||
| **Action:** Use semantic `<button>` for all interactive elements and implement specific target checks in parent container key handlers to prevent event collision. |
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The card wrappers are now keyboard-focusable (
tabIndex={0}) and handle Enter/Space activation, but they remain plain<div>elements without an interactive role, so screen readers can announce them as generic containers instead of actionable controls. This creates an accessibility gap where keyboard users can trigger the card but assistive-technology users may not realize it is clickable; the same pattern is repeated in grid/compact/list variants, so these wrappers should expose button/link semantics (role="button"or native interactive elements).Useful? React with 👍 / 👎.