@ariadne You're right that AT-SPI, the current accessibility protocol, is independent of both X and Wayland. And you _really_ wouldn't want to run that chatty interface over a network with any significant latency, though you theoretically could, since it's D-Bus-based. In certain scenarios it's already bad enough doing chatty IPC between local processes, as are other platform accessibility APIs.
undefined
Matt Campbell
@matt@toot.cafe
Post
-
What really frustrates me about Wayland is we're replacing an old system with lots of structural problems with a new system with lots of structural problems, and when it comes down to it X and Wayland are problemy for the same reason: They both farm ou... -
What really frustrates me about Wayland is we're replacing an old system with lots of structural problems with a new system with lots of structural problems, and when it comes down to it X and Wayland are problemy for the same reason: They both farm ou...> that someone is trying to improve on this by integrating screen reader hints and other accessibility features into wayland itself is an improvement over X11.
Hi. I think you're talking about my project. It's been on hold for a year now; the last status update was: https://blogs.gnome.org/a11y/2024/06/18/update-on-newton-the-wayland-native-accessibility-project/
What I like about my approach is that accessibility tree updates are serialized, unlike any existing platform accessibility API I know of... so they could efficiently be pushed over a network.
-
"So many conferences are mid.@dotstdy Thank you, was just reading that article.
And the two pieces of "much needed software" that I could download for free, File Pilot and RAD Debugger, aren't at all screen reader accessible. And unlike with some genres of games, there's no reason those kinds of tools can't be accessible. This is a common problem with GUI software from the Handmade crowd.