Skip to main content


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.

#GNOME #a11y #Linux #freedesktop #Wayland

This entry was edited (4 months ago)

reshared this

in reply to Sonny

good to know.

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.

in reply to Graham Sutherland / Polynomial

there is no "GNOME team"

It's a collaborative project from many different vendors. Ask vendors :)

This entry was edited (4 months ago)
in reply to Sonny

although I hope the foundation can play a bigger role overtime to help with critical matters such as a11y
This entry was edited (4 months ago)
in reply to Sonny

I meant Wayland, and was using the term "team" in a general sense rather than meaning any specific organised entity.
This entry was edited (4 months ago)
in reply to Graham Sutherland / Polynomial

@gsuberland 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

in reply to Sonny

I guess this will also be useful for other applications, like Input-Leap / Barrier or Workrave?
@matt @fedora