Keep a screen reader from skipping over rows of a list - #2007
Open
mehranlatifi83 wants to merge 1 commit into
Open
Keep a screen reader from skipping over rows of a list#2007mehranlatifi83 wants to merge 1 commit into
mehranlatifi83 wants to merge 1 commit into
Conversation
mehranlatifi83
force-pushed
the
fix/talkback-list-rows-read-as-one
branch
6 times, most recently
from
August 2, 2026 00:50
4df6cfa to
99c9268
Compare
mehranlatifi83
changed the title
Going through the list of people to mention with a screen reader skips over entries, and so does going through the results of an inline bot: it happens at the point where the list has to scroll to carry on. A list scrolls by a whole page when it is asked to, which is a page worth of rows at once, while a screen reader moves one row at a time and asks for that scroll when it reaches the last one it can see. The rows in between are carried past before it can land on them. Scroll by a row instead, so the one that follows is there to be read. A row of the mention list is also built from an avatar, a name and a username, none of which is tied to the row it belongs to, so it is read as three separate stops: let the row say all of it and leave its parts out of what is read. A result of an inline bot that is only a picture has nothing to say at all, and a row with nothing to say is passed over: fall back to what the result is called, or to what it is.
mehranlatifi83
force-pushed
the
fix/talkback-list-rows-read-as-one
branch
from
August 3, 2026 17:16
99c9268 to
46fb5db
Compare
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.
Summary
Going through the list of people to mention with a screen reader skips over entries, and so does going through the results of an inline bot: it happens at the point where the list has to scroll to carry on.
A list scrolls by a whole page when it is asked to, which is a page worth of rows at once, while a screen reader moves one row at a time and asks for that scroll when it reaches the last row it can see. The rows in between are carried past before it can land on them. Scroll by a row instead, the smallest one there is, since a list can hold a spacer as tall as itself, so the row that follows is there to be read.
A row of the mention list is also built from an avatar, a name and a username, none of which is tied to the row it belongs to, so it is read as three separate stops: let the row say all of it and leave its parts out of what is read. A result of an inline bot that is only a picture has nothing to say at all, and a row with nothing to say is passed over: fall back to what the result is called, or to what it is.