New issue
Advanced search Search tips

Issue 801421 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
Team-Accessibility

Blocked on:
issue 801422



Sign in to add a comment

a11y ChromeVox: focus box not following text/clipping on read.amazon.com

Project Member Reported by leberly@chromium.org, Jan 12 2018

Issue description

ChromeOS Version 65.0.3316.0 (Official Build) canary (64-bit)
Firmware Version Google_Samus.6300.174.0

# Enable ChromeVox 
# Load read.amazon.com and sign in with an Amazon account that contains at least one book sample. This is the same as if you had loaded the Amazon Cloud Reader app from the Chrome Web Store - it just routes you to read.amazon.com 
# Load any book which could include a free sample 
# Start to linear navigate across the contents of the book by using Search + arrow keys. 
Expected: focus ring follows the word spoken
Actual: focus ring is highlighting words that are not on the actual page. For example, it is showing a few pages in while the focus ring and words being read are many pages after the page shown. In another test, the focus ring was clipped - the top of the focus ring is off the top of the screen. 


 

Comment 1 by katie@chromium.org, Jan 16 2018

Cc: -katydek@google.com katie@chromium.org

Comment 2 by katie@chromium.org, Jan 16 2018

Cc: dtseng@chromium.org dmazz...@chromium.org leberly@chromium.org
It looks like ChromeVox is allowing linear navigation through elements that are offscreen. These elements are actually in the html source tree, so it kind of makes sense that Chromevox can access them. Since they are not visible on the screen, the focus rects are all clipped.

Kindle seems to be loading the page as you go through it, so even though the behavior is weird for sighted users, it seems that a Chromevox user can actually get to every word in the book.

What behavior would you want here?
Blockedon: 801422
Katie and I talked about this. We actually don't need a UI change, it's technically working as intended. We just need the overall behavior to be like when the onscreen content matches what ChromeVox is speaking. 

- the clipping is happening because Chromevox is reading offscreen content
- if ChromeVox is reading onscreen content, the focus rectangle is in the appropriate place 
- this is now blocked by 801422, the experience won't be correct until that bug is resolved
- select to speak works properly with this content since it can read words in individual spans smoothly 
Project Member

Comment 4 by sheriffbot@chromium.org, Yesterday (46 hours ago)

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment