Re: google docs, help needed
well, if only in screen reader mode, the thing basically sends messages to the screen reader as usual for web apps nowadays, through area widgets...anyways, the entire navigation is then provided by google docs itself, making the screen readers functions kinda not needed. Thing is, however, in screen reader mode only, the app sends every leter, symbol or whatever else through to the screen reader, like it implemented a screen reader of its own, that only uses nvda/jaws/orca as a speech service, kinda how we do it with the tolk library or similar.
So then, as you can imagine, the time that area widget takes to update is becoming significant after a while, even more so because it sends every tiny thing through, not the smartest implementation, if you ask me. Then, another can of worms is opening...
So, as the screen reader has its own navigation shortcuts and stuff, it will occasionally try to take control, not knowing it's only used as a speech service. So, that's why you hear the letter or symbol spelled twice if you have character echo turned on in your screen reader. You hear it once from your own screen reader, the other from the docs built-in thing. As if it wants to be even worse, docs uses the set lokal and region in your google account, so the docs instance might say the punctuation or other such symbols in the language your account is set in, while your screen reader, set to english, will say them in english. Just imagine how horid and confusing beyond hell that is. I don't usually enable braille mode...DK why, maybe because I don't really like it for some reason, instead I just turn off character echo alltogether while using docs.
Now to braille mode. Remember how I spoke above about the screen reader being used more like a speaking service and nothing more? Well, docs recognising the fact the screen reader needs to have more controll, since it's presumably communicating with a braille display, the screen reader then gets controll over the text almost entirely. So, the previous weird kind of edit field is replaced perhaps with an area widget that's more mimicking an edit field, even though it presumably looks the same, google won't want to damage their fabulous visual aspect of their work with screen reader accessibility, now would they?
Now, as the screen reader is working with something looking like a normal web edit field to it, it can navigate through it like it was one, so there's noticeably less delay, as the accessibility thing in the webpage doesn't get bombarded with so many messages it has to send through.
However, there is a disadvantage to braille mode. So, you know when you made a mistake, maybe spelling based, and docs was warning you where it starts, ends, and that correction suggestions are available in that place? well, now that the screen reader has controll and it's navigating through an edit field, maybe the mistakes would be red underlined as in word, but, like in word, it would no longer be automatically read to us, unfortunately. The formatting things aren't read like in the self-contained screen reader of docs, either, I have to rely on the screen reader formatting keyboard shortcuts, like nvda+f, I wish it would be read automatically.
Now, I hope my two dollars worth of ramblings is useful to anyone, I'm done, bgt lover logged out of the server, lol.
-- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
