New issue
Advanced search Search tips

Issue 833046 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
katie@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

STS OOBE reading invisible words on first and language screen

Project Member Reported by leberly@chromium.org, Apr 14 2018 
67.0.3383.0 (Official Build) dev (64-bit)
Google_Samus.6300.276.0

# Powerwash to go to OOBE
# Enable STS using the a11y settings (flag not enabled here)
# Use search key + mouse around first screen
Expected: only words read 
Actual: one invisible word read and highlighted - "language" 
# Navigate to the language screen and hold down search while dragging mouse around this screen
Expected: only words read 
Actual: one invisible word read and highlighted - "language" - at the top. Separately, focus lands on the entire window at one point and says "language" 

Marking as P2 since this is a "first impression" for users. Please feel free to mark p3 at your discretion. 

Screenshots of issues are attached.
OOBEfirstscreen.jpg
121 KB View Download

Comment 1 by leberly@chromium.org, Apr 14 2018

OOBElanguage1.jpg
104 KB View Download
OOBElanguage2.jpg
89.0 KB View Download

Comment 2 by katie@chromium.org, Sep 27

Labels: STS_visibility
This bug is related to overflow and visibility. Select-to-Speak cannot determine when an element is visible or invisible if that is not reflected in the a11y tree. For example, a 1px by 1px element that is on the screen may be read whether or not it has overflow:hidden.
►

Sign in to add a comment