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

Issue 830106 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

STS reading text with user-select:none if it is within a selected region

Project Member Reported by leberly@chromium.org, Apr 6 2018

Issue description

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
# Navigate to https://en.wikipedia.org/wiki/Echidna 
# Use mouse to highlight "Etymology The echidnas are named after Echidna" including the word edit between those phrases. 
# Note that the word edit is not highlighted as being selected
# Invoke STS with search + s
Expected: since the word edit is not selected, it shouldn't be read
Actual: STS will put a highlight on the bracket next to the word edit, read out edit while not having any text highlighting on, and then continue reading. 
 

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

Cc: nek...@chromium.org dmazz...@chromium.org dtseng@chromium.org
Labels: -Pri-3 Pri-2
Summary: STS reading text with user-select:none if it is within a selected region (was: STS reading text that doesn't have a visual highlight indicating selection)
This is an interesting one!

Sample html:
data:text/html,<p>One <span style="user-select:none">two</span> three</p>

If you try to copy the text on this page, you don't get the 'two', because it is user-select:none. What should STS search+s do in this case?

Should STS search+s respect the user-select CSS tag, and not read nodes with user-select:none? I'm not sure if it should, as that means an STS user would need to switch start speech methods to get that text verbalized.

+dtseng, nektar: do we need to make changes to selection code to reflect user-select:none?
I don't see that user-select is reflected in the a11y tree, so it might be that we can't tell the difference at all.

+dmazzoni interested in your opinion on this as well.
Labels: STS_selection
This bug requires improvements to selection and may automatically be fixed when relevant selection fixes are available through the automation API.

Sign in to add a comment