New issue
Advanced search Search tips

Issue 766875 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug
Team-Accessibility



Sign in to add a comment

a11y: Focus ring does not always resize when window resizes or moves

Project Member Reported by katydek@google.com, Sep 19 2017

Issue description

Chrome Version: 62.0.3198.0
OS: ChromeOS

What steps will reproduce the problem?
(1) Enable chromevox, select a page element or the search bar
(2) Take the window out of full screen, or move it
(3) Observe that sometimes the focus ring has not moved to follow the focused element

What is the expected result?
Focus ring moves when window moves or resizes

What happens instead?
Sometimes the focus ring does not move or resize with the window. Sometimes it does work.

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.

 

Comment 1 by katydek@google.com, Sep 19 2017

You can not only move or resize the window -- closing the window also leaves the focus ring on the screen where the element was before.
Components: -UI>Accessibility UI>Accessibility>ChromeVox
Status: Available (was: Untriaged)
Categorizing this as a ChromeVox bug because I think it's going to require at least some work in ChromeVox, even though we may end up improving internals/bindings too.

Labels: Visuals
Project Member

Comment 4 by sheriffbot@chromium.org, Sep 27

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
Cc: dtseng@chromium.org
Status: Available (was: Untriaged)
In Select-to-Speak, we set a timeout in order to check and update the node bounds as needed. Could we do the same in Chromevox?
Or, per a comment from David, could we get Chromevox to listen for automation tree changes related to position changes?

Sign in to add a comment