Issue metadata
Sign in to add a comment
|
ChromeVox: no spoken feedback on button press (v2) |
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Platform: 10323.67.0 (Official Build) stable-channel sentry Steps to reproduce the problem: 1. Turn on the screen reader built into chromeOS 2. Open up the example of accessible buttons from w3: https://www.w3.org/TR/2017/NOTE-wai-aria-practices-1.1-20171214/examples/button/button.html 3. Navigate to the mute toggle button 4. Press the mute toggle button What is the expected behavior? Some kind of feedback is given that a button has been pressed. What went wrong? Chromevox built into chromeOS gives no feedback on button press. Works well on voiceover and the chromevox browser extension. Did this work before? N/A Chrome version: 65.0.3325.209 Channel: stable OS Version: Flash Version: 29.0.0.150 Previous version of this bug used a different example: https://bugs.chromium.org/p/chromium/issues/detail?id=835427&can=2&start=0&num=100&q=&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified&groupby=&sort=
,
Jun 1 2018
Issue 835427 has been merged into this issue.
,
Jun 1 2018
Chrome: 69.0.3445.0 NVDA: 2018.1.1 Thank you so much for finding this example. I can confirm that ChromeVox does not announce the button state change NVDA in Windows does.
,
Jun 1 2018
,
Jul 10
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by shihuis@google.com
, Jun 1 2018Components: UI>Accessibility>Compatibility
Owner: lpalmaro@chromium.org