[NFBCS] GoogleDocs accessibility

[Curtis Chong]

Hello:

I am not able to respond at length to John’s questions regarding Google Docs at this point on my iPhone. I will say, that in using Google Docs, one has to turn on both accessibility and braille modes, then turn off the JAWS virtual cursor to achieve best results. Vispero has put on a couple of webinars on using Google Docs with JAWS. Despite this worthy effort, however, it is fair to say that Google’s architecture forces nonvisual users to use strategies that are a significant departure from the traditional screen reader training available today. There are lots of things that need to be learned simply to use the Google Workspace products. In the worsd case, one can simply download the Google Docs file as a Word document if all you want to do is to glean the information you need from it.

Trainers who teach this stuff to the blind are forced to expand their teaching topics to cover all of this. Unfortunately, if they don’t, our ability to compete in today’s workforce will be severely diminished.

Kind wishes,

Curtis Chong

On Mar 27, 2023, at 3:53 AM, John Gardner via NFBCS <nfbcs at nfbnet.org> wrote:

Hello again all. This note is mostly a complaint about Google Docs for not being more accessible. And a request for help with a couple of issues. If any of my complaints are wrong-headed I'm happy to be set straight. I'll send this on to Google after hearing feedback from this list.

My gripes start with the observation that Google Docs has a (imho unnecessarily large) learning curve, so that blind people who are not expert techies have a hard time of it. Google has admittedly put a lot of effort into promoting accessibility but I do not find Google Docs very usable. You cannot even start with a Google Doc unless you know that the screen reader has to be in forms mode. And I really object to being required to change my screen reader hot keys to avoid conflict with Google Docs hot keys. It should be the other way around. I also find it confusing that feedback during editing is so different from what NVDA and Jaws say in other apps. It is really hard, for me anyhow, to collaborate because I find it so hard to edit anything.

I have other little gripes but I don't want to rant. I do have two specific questions that I hope somebody can answer.
* Is there any way to "read from cursor to end" in Google Docs with either NVDA or Jaws? Not having this feature makes it really painful to read large documents.
* Can you (if so how) alter any of the editing spoken feedback?

Thanks all. 

John Gardner
President
541.754.4002 x 200
www.viewplus.com


PRIVILEGED AND CONFIDENTIAL: This message and any files transmitted with it may be proprietary and are intended solely for the use of the individual to whom they are addressed. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited; please notify the sender and delete the message. ViewPlus Technologies, Inc. accepts no liability for damage of any kind resulting from this email.


_______________________________________________
NFBCS mailing list
NFBCS at nfbnet.org
http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
To unsubscribe, change your list options or get your account info for NFBCS:
http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/chong.curtis%40gmail.com