Comment by shakna

> NVDA looks like it is open source, it shouldn't be too hard to port.

Yup. Just gotta invent a Win32-compatible Wayland first. This... Is sorta a "whole fucking owl" moment.

> As explained above NVDA relies heavily on Windows specific API's and cannot be converted to run under Unix based systems without a lot of work. Given how small NVDA development team is spending time on making NVDA work under Linux at a level at which Orca works currently would take years and mean much less development for the version for Windows. In short the more reasonable course of action is to spend time on improving Orca or other Linux screen readers rather than porting (which in practice would mean almost rewriting from scratch) NVDA to run under a non Windows system. [1]

Accessibility in Wayland is still in staging. [0] There is not the APIs you need, to port anything to using them.

X-Windows only supports Class 1 info over AAC. Class 2 was only ever semi-implemented, and is the more important class of information for the user. You basically need an Optacon, and too bad if you don't want tactile.

NVDA does work under Wine! But only with well-behaving programs running under Wine. It won't work for the rest of the system.

Gnome's Orca only works with Gnome-aware apps. It is supposed to work with Plasma for KDE things, but its a dice roll. It works with Firefox, Chrome, etc, because they go out of their way to make accessibility work better.

But Orca is about half as decent as JAWS or NVDA. Its a step ten years backwards.

Voxin (paid) used to work well, but seems to now be unmaintained. Certs expired, no updates for two years, etc.

[0] https://gitlab.freedesktop.org/mwcampbell/wayland-protocols/...

[1] https://github.com/nvaccess/nvda/issues/13196