Issue metadata
Sign in to add a comment
|
ChromeVox is not reading specific labels in Accessibility>Manage Accessibility Features section in chrome://settings page |
||||||||||||||||||||||
Issue description72.0.3595.0 (Official Build) canary (64-bit) (cohort: Clang-64) Firmware Version: Google_Cave.7820.384.0 ChromeVox, Steps to repro: # With ChromeVox ON, goto chrome://settings page # Goto Accessibility>Manage Accessibility Features page # Check labels in that page for ex Enable Select to Speak, Text to Speech voice settings. Expected: These labels should be read aloud. Actual: Nothing is read aloud, so the context does not make sense as there is no labels. Focus is completely skipped even when reading line by line. Repeat the above for Chrome version:72.0.3590.0 (Official Build) dev (64-bit) (cohort: Dev) The results are same as above. Cannot test for Windows OS as Accessibility section is missing in Windows 10, it just has Add accessibility feature>open chrome web store
,
Today
(7 hours ago)
Reopening, requesting a comment by a PM: I think this bug and David's comments speak to confusion caused by a conflict between these three valid ideas: 1. Everything written visually should be available to screen reader users 2. The buttons should be linked to their labels so you always know what each button does. 3. Don't repeat the same words in multiple places to prevent overload/confusion. Shrija opened this bug thinking about idea number one while David T closed it in service of idea number three. Question for Laura A and Kara: Given that there are some users of ChromeVox who also have sight, is there any other way we can resolve this conflict between ideas? Should we keep it as-is? |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dtseng@chromium.org
, Today (8 hours ago)