[NFBCS] GoogleDocs accessibility

[Rynhardt Kruger]

Hi John,

I agree with you that Google Doc's accessibility is unnecessarily complex.
It essentially has two modes. From the issues you are describing it sounds
like you are in its default mode, where it runs its own screen reader so to
speak. The other mode is called Braille mode, and can be turned on in
accessibility settings under the tools menu. In my view it is incorrectly
named, as it actually envolves a propper ARIA implementation for Docs,
which I find to work better with screen readers regardless if one is using
Braille or not. With Braille mode, you should for example, be able to do a
normal say-all, and also use your screen reader's own keys to navigate
tables, etc. You should also be able to explore the document in brows mode.

Regards, and hope this helps,

Rynhardt

On Sun, 26 Mar 2023, 20:24 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/rynkruger%40gmail.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20230326/226065d0/attachment.html>