New issue
Advanced search Search tips

Issue 835427 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 837802
Owner: ----
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

ChromeVox: no spoken feedback on button press

Project Member Reported by andrsm...@google.com, Apr 20 2018

Issue description

UserAgent: 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. Start the ChromeVox AT that's built into ChromeOS
2. Navigate to accessible region example that's referenced in w3.org: http://oaa-accessibility.org/example/20/ 
3. Tab to the "Show topic 1" button and press it.
4. Backward tab to the same button from step#3 that now reads "Hide topic 1"
5. Press the "Hide topic 1" button

What is the expected behavior?
Focus remains on the pressed button.  Screenreader provides some kind of feedback that the button has been pressed and the corresponding region has been collapsed.

What went wrong?
Screenreader does not provide any feedback on hide button press.

Did this work before? No 

Chrome version: 65.0.3325.209  Channel: stable
OS Version: 
Flash Version: 29.0.0.150

Works as expected on VoiceOver and also on ChromeVox browser extension on my Mac, but not the ChromeVox that's built into ChromeOS.
 
Components: UI>Accessibility>ChromeVox
Status: WontFix (was: Unconfirmed)
In the example, aria-expanded is set on the <div> with role="region", but it should be set on the <button> itself.

Since the aria-expanded is not on the button, there is no way for a screen reader to know what event triggered the button's text to change and thus would not announce the change.

Aria-expanded is used for buttons and links that control expandable content. Even if screen readers recognized it on the div, they would never see it when the div was collapsed since the region is no longer on screen.

The same behavior happens with JAWS 2018 and NVDA 2018.1 in Chrome and Firefox on windows.

Feel free to reopen this issue with more examples.
Feedback should be provided when a button is pressed though, irrespective of the button's intent, no?

For another example, please try the mute toggle button in this w3 doc on buttons: https://www.w3.org/TR/2017/NOTE-wai-aria-practices-1.1-20171214/examples/button/button.html

Mute button feedback works on voiceover and on chromevox extension, but not chromevox on chromeOS.

@dsexton How do I re-open this?
I'll just open a new bug with the new example, thanks.
Here's the new bug I've opened for this: https://bugs.chromium.org/p/chromium/issues/detail?id=837802
Mergedinto: 837802
Status: Duplicate (was: WontFix)

Sign in to add a comment