Fix accessibility issues across SelectedRowPanel, GridHeader, and ColumnTitle components #36
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.
This PR addresses several critical accessibility issues that were preventing screen reader users and keyboard-only users from effectively navigating and understanding the application interface.
Issues Fixed
1. Incorrect ARIA Usage in ColumnTitle Component
The column menu button was using
aria-labelledby="Column menu"but no element with that ID existed, causing screen readers to announce nothing useful.Before:
After:
2. Missing Labels in GridHeader Component
Multiple interactive elements lacked proper accessibility labels:
Improvements:
aria-label="Search grid content"to search inputaria-label="Go back to home",role="button", andtabIndex={0}3. Poor Semantic Structure in SelectedRowPanel Component
The row details panel lacked proper semantic structure and accessible interaction patterns:
Collapsible Content Enhancement:
aria-expandedandaria-controlsattributes to expand/collapse buttonsSemantic Structure Addition:
role="complementary"witharia-label="Row details panel"to main containerrole="banner"for header androle="main"for content arearole="region"with proper labeling for issue content sectionsrole="group"and contextual labels like "Navigate between rows"role="heading"andaria-level={1}Impact
These changes significantly improve the accessibility of the application for:
Technical Details
The changes are minimal and surgical, focusing specifically on accessibility without disrupting existing functionality or visual design.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.