After reading this thread, I don't want a new Mac anymore. I do wish there were posts like this going over Android and Windows' accessibility frameworks, but I'll take what I can get.

applevis.com/comment/188396#co…

#apple #accessibility #VoiceOver #MacOS #mac #blind

in reply to Devin Prater :blind:

They wrote:

> On macOS, the accessibility infrastructure is completely orthogonal to the window server, as is also likely the case on Linux, since if I recall correctly it usually works on top of DBus

Yes, that's definitely the case with AT-SPI on Linux (and other free Unixes). That's one of the issues I aimed to fix with Newton, the prototype ground-up redesign of the accessibility stack that the GNOME Foundation funded last year. I hope I can resume work on that soon.

in reply to Matt Campbell

@matt Well, is it as much of a mess as MacOS'? Undocumented, single-threaded, all that? Granted, I didn't get much out of all that system programming language, but the single-threaded stuff, locking threads for VO to figure out all the things it *can't* work with, and definitely the 20 year old depricated framework sounds like a nightmare for both Apple and third-party developers.