Skip to content
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

accessibility: items not read on main screen with screen reader #1093

Open
vortex1024 opened this issue Aug 10, 2022 · 0 comments
Open

accessibility: items not read on main screen with screen reader #1093

vortex1024 opened this issue Aug 10, 2022 · 0 comments

Comments

@vortex1024
Copy link

Summary:
after the google map, swiping or exploring with talkback e enabled speaks "space" instead of stop/bus names
Summarize your issue in one sentence (what goes wrong, what did you expect to happen)

Steps to reproduce:
turn on talkback, open onebusaway, select a zone if you haven't already and explore the screen
How can we reproduce the issue?

Expected behavior:
talkback shoud read the stops/lines, I don't really know what they are since they are not read :)
What did you expect the app to do?

Observed behavior:
reading "space"
What did you see instead? Describe your issue in detail here.

Device and Android version:
sony xz1, android 12
What make and model device (e.g., Samsung Galaxy S3) did you encounter this on? What Android version (e.g., Android 4.0 Ice Cream Sandwich) are you running? Is it the stock version from the manufacturer or a custom ROM? What version of Google Play Services is running on your device?

I wonder if this is something related to my setup, as I've seen other blind people around here who seem to be using onebusaway with success.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant