This repository was archived by the owner on Apr 15, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 15, 2026. It is now read-only.
Android: Screen reader accessibility: Navigation by lines doesn't navigate by lines #1556
Description
Describe the issue
On Android, TalkBack's "navigate by line" feature has trouble when working with a CodeMirror editor. In particular, when navigating by lines,
- Using TalkBack's next/previous line navigation, focus often navigates to the next or previous region with syntax highlighting, rather than the next/previous line.
- See the attached screen recording.
- The content read by TalkBack often doesn't match the content near the cursor.
Screen recording
demo.mp4
The above screen recording shows:
- TalkBack reads text from near the start of the document when navigating by line near the end of the document.
- Navigation by line moves the cursor less than a full line.
- Navigation by line reads content not near the cursor.
Browser and platform
Chrome 135.0.7049.111 / Android 13
Activity
[-]Android: TalkBack: Navigation by lines doesn't navigate by lines[/-][+]Android: Screen reader accessibility: Navigation by lines doesn't navigate by lines[/+]marijnh commentedon Jun 3, 2025
I can confirm this. But TalkBack works just as terribly with a raw contenteditable field that has a similar structure (divs with text in them, some of which has spans covering it, which seems a rather reasonable DOM structure). So it seems this is a general issue with Chrome and/or TalkBack.
personalizedrefrigerator commentedon Jun 5, 2025
Thank you for checking!
I've opened an upstream issue: https://issues.chromium.org/issues/422686693. Edit: I'm now getting "Access is denied" when opening that issue. This seems to be the new issue.
marijnh commentedon Apr 15, 2026
This issue has been moved to issue #1556 on the repository's new home.