Issue metadata
Sign in to add a comment
|
Dashes within flag names not read by TTS in chrome://accessibility |
||||||||||||||||||||||
Issue descriptionGoogle 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
,
Aug 27
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.
,
Sep 5
,
Sep 14
,
Sep 14
,
Sep 17
,
Sep 27
This bug requires a change to TTS to be completely fixed. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by leberly@chromium.org
, Aug 25