New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 738609 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Oct 22
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug
Team-Accessibility



Sign in to add a comment

Localespans should also work for granularity movement with Talkback

Project Member Reported by vtsaran@chromium.org, Jun 30 2017

Issue description

Chrome Version: latest Canary
OS: Android 8.0

What steps will reproduce the problem?
1) Install one or more supported languages for Android TTS, e.g. German, Polish, Ukrainian, etc.
2) Launch TalkBack, Settings -> Accessibility -> TalkBack.
(3) Open Chrome and go to www.wp.pl as an example. Talkback should switch to Polish language once the page finished loading.
4) Navigate to one of the elements, a link or a text, by swiping left and right. Then, switch to "lines" or "words" granularity by swiping up. Then, navigate using that granularity by swiping left and right, observe.

What is the expected result?
The "lines" and "words" should be spoken in the language indicated by localespan.

What happens instead?
"lines" and "words" are spoken in the default system language, and not the one specified by the localespan.

Please use labels and text to provide additional information.


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.
 
Summary: Localespans should also work for granularity movement with Talkback (was: Localespans should also work for granularity movement)
Labels: triage-android-remaining
Owner: ibobra@chromium.org
Status: Assigned (was: Untriaged)
Isha, I don't really understand why this would be working differently.

Status: WontFix (was: Assigned)
This should be fixed in Talkback, not Chrome. I emailed Victor about it offline.

Sign in to add a comment