Re: [orca-list] Screenreader Accessibility Testers for Ubuntu

[Devin Prater <r d t prater gmail com>]

Sure, but it also means that if the DOM messes up, NVDA won't be stuck on some part of the page, like ChromeVox, VoiceOver, and all the screen readers that try to just work with the browser directly. I mean, yes it's websites' fault that stuff like that happens, but Windows screen readers take the more practical rout of dealing with what we have now, thus increasing productivity, rather than hoping things get better and being disappointed when they don't. See Joanie's commits to Github where she's like "this is why we can't have nice things."

Devin Prater

r d t prater gmail com

On Thu, Apr 7, 2022 at 8:14 AM Kyle via orca-list <orca-list gnome org> wrote:

J.G had this to say:
> but from accessibility perspective, I think, there are solutions,
> which are more matured than in Linux in general.


Older doesn't necessarily mean better. A mature wine is better than a
new wine, but old coffee is stale and tasteless. Just the fact that even
NVDA has to copy pages from any browser into a virtual screen reader
buffer just to read them somewhat correctly leaves a bad taste in my
mouth, as it always has. Every other a11y structure on the planet, no
matter how mature or how new, does not present this problem for screen
reader developers.

~Kyle

_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html