Issue metadata
Sign in to add a comment
|
Focus issues with Google Docs when using VoiceOver
Reported by
mjanusau...@gmail.com,
Jul 29
|
||||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3506.0 Safari/537.36 Steps to reproduce the problem: 1. With VoiceOVer running (CMD + F5) open a Google Doc. 2. Previously you would hear "document content", "top of document" when the doc had loaded and it was possible to immediately begin navigating the document contents using the arrow keys. 3. Observe that now when the document loads only "frame 2" is spoken by the screen reader and pressing the arrow keys speaks nothing. Somtimes it is possible to regain focus and keyboard access to the document contents by turning Voiceover off, and then back on again by pressing CMD + F5 twice with a few seconds in between. What is the expected behavior? A Google doc should load and speak helpful and correct status messages by the screen reader, and be immediately navigable with the keyboard. What went wrong? This is a regression. Now only "frame 2" is spoken by the screen reader and the arrow keys do not allow moving through the document contents with spoken feedback. Did this work before? Yes Chrome version: 70.0.3506.0 Channel: canary OS Version: OS X 10.14.0 Flash Version:
,
Jul 31
Tested this issue on reported chrome version 70.0.3506.0 using Mac 10.13.5. Attaching screen-cast for reference. Steps: --------- 1. Launched reported chrome 2. Enabled Voice Over on Mac 10.13.5 3. Opened google doc sheets As we are able hear and see the Voice Over @Reporter: Please find the attached screen-cast and let us know if we have missed anything in the process. Also mention that is it related to Mac 10.14.0. Thanks.!
,
Jul 31
Sorry the silent screen recording is not accessible to me as a blind screen reader user. The bug report was regarding a Google Doc document and not a spreadsheet. The behavior regarding focus and keyboard navigation upon load is very different and a regression between Chrome beta and Canary. Perhaps someone on the accessibility team could have a look with a Mac and VOiceOver?
,
Aug 17
Adding UI>Accessibility.
,
Sep 7
,
Sep 7
We had a recent regression with ARIA live region announcements on mac OS. I hope that this covers the behavior seen in this report. Otherwise please re-open the bug.
,
Sep 7
To elaborate further: The live regions bug prevented Google Docs from verbalizing anything. Cursor keys stopped reading the contents of the document, for example. With the recent fix, everything should be fine in the upcoming mac OS version Mojave. Unfortunately, it will remain mostly broken in pre-Mojave. The user needs to sometimes quit and relaunch Chrome. Not sure what, if anything, we can do about that.
,
Sep 17
|
|||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||
Comment 1 by swarnasree.mukkala@chromium.org
, Jul 30