Unexpected screen reader behavior |
TalkBack navigates between keyboard items instead of moving focus out of the Gboard window when swiping |
| ID: 4445Status: ActiveVersion: from TalkBack9 and upReport Date: 13 May 2025Product: Android Accessibility Suite (TalkBack) | |
| Reporter | |
| Assignee | |
Description Issue Description: When using Gboard with TalkBack, swiping right or left to navigate to the next window (e.g., to access “Submit” or “Send” buttons) causes the cursor to move within the keyboard keys instead of navigating to the intended window. This issue first appeared in TalkBack 9 and remains unresolved in TalkBack 15.2. |
|
Donate to Us
To uphold the standards of a robust and fully accessible project, we graciously request your support. Even a modest contribution can have a profound impact, enabling Accessible Android to continue its growth and development.
Donations can be made via PayPal.
For alternative methods, please do not hesitate to contact us.
We deeply appreciate your generosity and commitment to our cause.
Subscribe to Blind Android Users mailing list
Accessible Android on Mastodon
- UntitledThird-Party Screen Readers: Are They a Security Risk? https://accessibleandroid.com/third-party-screen-readers-are-they-a-security-risk/
- UntitledNew app added to Accessible Android apps directory: Shortcut Menu accessible https://accessibleandroid.com/app/shortcut-menu/
- UntitledNew on Accessible Android: Accessibility RatingsYou can now rate apps in the Accessible Android Apps Directory from 1 to 5 based on accessibility.Add the screen reader and Android version you tested with, and optionally explain your rating with an accessibility note.Community ratings help others understand how accessible an app really is.Start rating the apps you […]
- UntitledNew app added to Accessible Android apps directory: Lexo Offline AI Voice Keyboard accessible https://accessibleandroid.com/app/lexo-offline-ai-voice-keyboard/

I agree. If one needs to actually find something on the keyboard, they might as well just explore it, isn’t it? This issue should be fixed.