New issue
Advanced search Search tips

Issue 877716 link

Starred by 1 user

Issue metadata

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


Show other hotlists

Hotlists containing this issue:
Hotlist-3


Sign in to add a comment

Dashes within flag names not read by TTS in chrome://accessibility

Project Member Reported by leberly@chromium.org, Aug 24

Issue description

Google Chrome	70.0.3524.2 (Official Build) dev (64-bit)
Firmware Version Google_Lulu.6301.136.57

# Navigate to chrome://accessibility 
# Enabled ChromeVox with ctrl + alt + z
# Navigate to --force-renderer-accessibility or --disable-renderer-accessibility
# Listen to speech: "two dashes force renderer accessibility" 
Expected: if the first two dashes are read, the dashes in the middle should be read, too.
Actual: dashes are not read (which is what happens in other situations)

# Turn off ChromeVox with ctrl + alt + z
# Enable Select To Speak via Settings > Manage Accessibility Features
# Invoke STS on --force-renderer-accessibility or --disable-renderer-accessibility
Expected: dashes read since ChromeVox reads them
Actual: no dashes are read
 
Labels: a11y-WebUI a11y-internals
chromeVox has a punctuation level command (Search+a, p) which makes punctuation like this read. Repeated characters (2 dashes) are in the "some" level while single dashes are in the "all" level. So, this is working as intended in ChromeVox.
Components: -UI>Accessibility>ChromeVox
Labels: pm-markchang
Labels: pm-markchang
Labels: -PM-markchang
Labels: STS_TTS
This bug requires a change to TTS to be completely fixed.

Sign in to add a comment