-
Notifications
You must be signed in to change notification settings - Fork 13k
Fix(accessibility): add screen reader support to RewindViewer #20750
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
Merged
Adib234
merged 10 commits into
google-gemini:main
from
Famous077:fix/rewind-screen-reader-accessibility
Mar 6, 2026
Merged
Changes from 1 commit
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
e2fa35c
fix(accessibility): add screen reader support to RewindViewer
Famous077 4b3bb8f
fix(accessibility): use BaseSelectionList for interactive screen read…
Famous077 05f403d
fix(accessibility): address screen reader review feedback for RewindV…
Famous077 0b59a52
Merge branch 'main' into fix/rewind-screen-reader-accessibility
Famous077 80fa113
fix(accessibility): address screen reader review feedback for RewindV…
Famous077 d4330a5
Merge branch 'main' into fix/rewind-screen-reader-accessibility
Famous077 e70d028
Merge branch 'main' into fix/rewind-screen-reader-accessibility
Famous077 311f249
fix(accessibility): remove dev comments, redundant prop, and fix scre…
Famous077 55e32cf
Merge branch 'main' into fix/rewind-screen-reader-accessibility
Famous077 58b890d
Merge branch 'main' into fix/rewind-screen-reader-accessibility
Famous077 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
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 current implementation for the screen reader view renders a static list of items using
items.map(). This makes the list non-interactive, as the key press handlers for navigation (arrow keys) and selection (Enter) fromBaseSelectionListare not being used. As a result, screen reader users can see the list but cannot interact with it, which prevents them from using the rewind functionality and negates the goal of this accessibility fix.To address this, you should use the
BaseSelectionListcomponent for the screen reader view as well, but with a simplifiedrenderItemfunction that produces plain text output. This will provide the necessary keyboard interactivity.As a follow-up, you could extract the
onSelecthandler into a named function to avoid duplicating it between the screen reader and visual rendering paths.References
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.
Updated successfully