New issue
Advanced search Search tips

Issue 830887 link

Starred by 1 user
Status: Fixed
Owner:
katie@chromium.org
Closed: Nov 12
Cc:
katie@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug
Team-Accessibility



Sign in to add a comment

STS focus ring movement too delayed while scrolling

Project Member Reported by leberly@chromium.org, Apr 9 2018 
Google Chrome 67.0.3383.0 (Official Build) dev (64-bit)
Google_Samus.6300.276.0
Chrome OS with flag enabled: #enable-experimental-accessibility-features

# Enable STS
# Invoke the feature on any page that allows you to scroll up and down, I used this one: https://en.wikipedia.org/wiki/Yinotheria
# Scroll up and down while content is being read

Expected: Focus ring disappears since the content is offscreen
Alternative expected: focus ring snaps to the top or bottom of the frame while scrolling (not as preferred as it disappearing)

Actual: the focus ring page stays in one location while the text underneath scrolls to another part of the page then eventually snaps to the top or bottom of the frame

I feel like if it's reading something offscreen the ring should disappear because if you were to switch tabs it disappears, but I'm ok with the alternative expected too to indicate that it's reading something above/below were you are.

Comment 1 by katie@chromium.org, Apr 10 2018

Labels: -Pri-1 Pri-3
Summary: STS focus ring movement too delayed while scrolling (was: STS focus ring not disappearing/not smoothly moving to the top/bottom of the page while scrolling )
The focus ring takes up to a second to react to scroll. We could reduce that by increasing the rate at which we check node state changes. However, the more frequently we check, the more likely we are to cause lag. There's probably some happy intermediate state, but I don't think it's P1 to find it.

The focus ring is expected to draw at the closest edge of the screen when the node is offscreen. That part is WAI.

It disappears when you switch tabs because then it's not on the active page. But when it's just offscreen, the visible edge of the focus ring is an indication of where the currently being spoken node has gone.

Comment 2 by leberly@chromium.org, Apr 12 2018 

Ok, fair enough. Pri change SGTM though I'd lean towards a p2 just because it's so easy for users to see.

Comment 3 by katie@chromium.org, Sep 27

Owner: katie@chromium.org
Status: Started (was: Available)
I'll change this from checking every second to checking every half-second. Let's start with that and see how it feels.
Project Member

Comment 4 by bugdroid1@chromium.org, Sep 28 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/b93c26786e50f3a77d177771a2a8ee955c4a5c5a

commit b93c26786e50f3a77d177771a2a8ee955c4a5c5a
Author: Katie D <katie@chromium.org>
Date: Fri Sep 28 00:24:53 2018

Increase rate at which Select-to-Speak checks for changes.

This will make Select-to-Speak appear more reactive when
the page updates during speech.

Bug:  830887 
Change-Id: Iffd09d486686fa39d34f9188a6238719e71e92c7
Reviewed-on: https://chromium-review.googlesource.com/1248134
Reviewed-by: David Tseng <dtseng@chromium.org>
Commit-Queue: Katie Dektar <katie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594932}
[modify] https://crrev.com/b93c26786e50f3a77d177771a2a8ee955c4a5c5a/chrome/browser/resources/chromeos/select_to_speak/select_to_speak.js

Comment 5 by katie@chromium.org, Nov 12

Status: Fixed (was: Started)
►

Sign in to add a comment