Issue metadata
Sign in to add a comment
|
Windows Narrator does not read toggle of checkboxes
Reported by
tdunke...@gmail.com,
Dec 7 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Edge/16.17046 Steps to reproduce the problem: 1. Start Windows Narrator 2. Open Chrome 3. Navigate to http://www.oaa-accessibility.org/example/8/ 4. Tab to a checkbox 5. Toggle the state with spacebar What is the expected behavior? The new state is announced What went wrong? The new state is not announced. This is likely an issue between Narrator inspecting with UIA and Chrome implementing IAccessible2/MSAA Did this work before? N/A Chrome version: 58.0.3029.110 Channel: n/a OS Version: 10.0 Flash Version:
,
Dec 20 2017
I can confirm that this issue exists on the latest stable version of chrome. 1. Navigate to http://www.oaa-accessibility.org/example/8/ 2. turn on narrator. 3. tab until you get to the check boxes, note that their state is read correctly. 4. Press space on one of the check boxes. Its state changes, but the changed state is not announced. What should happen: When pressing space on a checked check box, Narrator should say "unchecked" to indicate the new state. If space is pressed on an unchecked check box, Chrome should say "checked" to indicate the new state. What actually happens: Pressing space to toggle a check box state results in no announcement by Narrator. Work-around: If I shift+tab away from the check box and tab back to it again, I can hear the updated state. Put another way, resetting focus causes the correct state to be read. Additional notes: I should note that this seems to be specific to Narrator, this behavior does not seem to occur in NVDA and ChromeVox.
,
Jan 2 2018
,
Jan 2 2018
Confirmed with Narrator and Chrome 65.0.3309.0 Also, NVDA 2017.4 has trouble focusing the example and exiting the example once focused. Indicating there may be more going on with this particular page.
,
Jan 17 2018
,
Jan 18
(4 days ago)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by vamshi.k...@techmahindra.com
, Dec 8 2017Labels: Triaged-ET Needs-Milestone Needs-Feedback
7.8 MB
7.8 MB View Download