New issue
Advanced search Search tips

Issue 822556 link

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



Sign in to add a comment

STS reading radio button and label may feel too verbose

Project Member Reported by leberly@chromium.org, Mar 16 2018 
Google Chrome 67.0.3369.0 (Official Build) canary (64-bit)
Firmware Version Google_Samus.6300.276.0
Flag enabled: #enable-experimental-accessibility-features

# Enable Select To Speak in Chrome Accessibility Settings
# Create a new Google Form that includes a question with multiple answers such that multiple radio buttons will be rendered. 
# Press preview button to create the preview/submission page
# Hold down Search and drag highlight around the resulting radio buttons
Expected: just the text characters after each button are read once
Actual: text is read twice

This does NOT happen if text is selected first and then search + s is used. 

This does NOT happen on the ARIA example page for radio: https://www.w3.org/TR/2016/WD-wai-aria-practices-1.1-20160317/examples/radio/radio.html

This also does NOT happen when ChromeVox has focus on this radio group. ChromeVox will instead read the text, then radio button, etc. If you linear navigate again to the text after focus was on the button itself, the text will be read on its own.

Please kindly revert to a11y-testers if this is an authoring error on the Forms side and we'll open an internal bug.

Comment 1 by katie@chromium.org, Mar 19 2018

Components: UI>Accessibility>SelectToSpeak

Comment 2 by katie@chromium.org, Mar 19 2018

Components: -UI>Accessibility

Comment 3 by katie@chromium.org, Mar 28 2018

Labels: -Pri-2 Pri-3
Summary: STS reading radio button and label may feel too verbose (was: STS reading radio buttons twice in Forms preview/submission page )
This is working as intended. STS reads the content description of radio buttons and other controls.

A long-term feature request would be to come up with a way to avoid repeating if the control is next to its label, so I'll leave this open to address that. We'd need to think about how to make this less verbose without losing information, maybe if the label and the radio button have the exact same string and are in a row, we can find a way to highlight both and read it just once?

Note: This does happen with chromevox if you used search plus arrows to go between a radio button and its label.
►

Sign in to add a comment