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

Issue 700473 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

[A11y Assessment - Omnibox] Issues navigating suggested URLs and terms in omnibox with ChromeVox

Project Member Reported by lpalmaro@chromium.org, Mar 10 2017

Issue description

Chrome Version: 57.0.2955.0
OS: Chrome


What steps will reproduce the problem?
(1) Enable ChromeVox
(2)Navigate to the url bar (ctrl + L) and type some text
(3) Use the arrow down key to navigate through suggestions. 

First, there is no verbalization that suggestions are even available. This context is missing to blind users who aren't able to see the suggestions appear visually. 

Second, there seems to be some strange behavior going on with What ChromeVox reads. It reads the actual page, but not the source - for example, if I go to a suggested site in the list "translate.google.com" ChromeVox reads the site aloud, but NOT the corresponding info to the right of it which says "Google Translate". Same for terms that it suggests -- it reads the suggested term itself, but then doesn't read "Google Search", which visually appears directly to the right in the list of suggestions. 

Third, there is some weird intonation going on. The list seems inconsistent with ChromeVox -- sometimes ChromeVox speaks normally, and other times it speaks at a lower pitch as if something is being deleted. But nothing has been deleted. It should all be the same intonation when navigating through the suggestions in the list. This is happening because as you arrow through the list items, the item you have focus on gets placed in the URL bar. Therefore, every time you choose a suggestion that has less characters than the previous one that was in the url bar, then it speaks it in the lower tone as if something was deleted. Then if you choose a suggestion with a larger amount of characters, it reads it normally. This is strange behavior, since the user isn't actually deleting anything and shouldn't have to worry about why the intonation is changing. 
 
Labels: NewComponent-Accessibility NewComponent-Accessibility-ChromeVox
Labels: -NewComponent-Accessibility-ChromeVox NewComponent-Accessibility-Browser
Labels: -newcomponent-accessibility-browser -newcomponent-accessibility
Owner: ----
Status: available (was: Assigned)
This appears to require a lot of views related work. This isn't exclusive to ChromeVox and we should trigger various behaviors as one arrows down:
- post a notification to announce any additional UI as it appears e.g. google translate should probably have a selection event fired upon it as you down arrow
- the weird verbalizations from ChromeVox are its way of reading the difference between the previous string and the current one.

so

previous: "this is a test"
current "this is a "

would read as
"test deleted"

because that's at a raw sense, what happened.

This is not the desired behavior though however, so we might simply special case or read the entire string.
Cc: omrilio@chromium.org
Owner: omrilio@chromium.org
Status: Assigned (was: Available)
Omri/Rachel, can you help to triage? 
Owner: rpop@chromium.org
Friendly ping - any updates on this? 

Sign in to add a comment