Recent searches
Search options
Administered by:
Now that the storm has passed — I can share an update on screen reader support under Wayland.
As part of STF; GNOME has been working since the end of last year on resolving the matter.
The main issue is that we currently lack a way to “snoop on” or “grab” key events from the compositor.
We now have a draft protocol and implementation in Orca and Mutter thanks to @matt
We are doing our best to get it ready for GNOME 47.
It's part of the bigger Newton project which you can read about here https://blogs.gnome.org/a11y/2024/06/18/update-on-newton-the-wayland-native-accessibility-project/
unless one has already been done and I just haven't seen it, it would be good to have the team do a retrospective on why the prerequisite capabilities for screen readers weren't seen as mandatory design elements during planning, and document the changes they're making in policy and procedure to avoid these oversights in future. not to admonish, but there are clearly lessons to be learned here.
@gsuberland @matt there is no "GNOME team"
It's a collaborative project from many different vendors. Ask vendors :)
@gsuberland @matt although I hope the foundation can play a bigger role overtime to help with critical matters such as a11y
@gsuberland @matt i understand, from my perspective a team is an organized entity.
The broad Linux Wayland transition, while necessary, has been difficult but with each roadblock out of the way we are one step further putting it behind us and focus on improving the Linux freedesktop for everyone
@gsuberland My main guess as to why is probably because its better to have *something unfinished* to build onto than *something theoretical* that nobody can use. It definitely should have been addressed earlier though.
@sonny That's great to see! 
