mastodon - Link to source
I'm willing to pay up to $10,000 (USD), to whomever I need to pay, to solve the #GNOME AT keyboard input handling problem once and for all. Currently, toolkits implementing AT-SPI have to pass all keyboard events to the AT-SPI registry, then wait for a response on whether the event should be processed as usual. No other platform does something like this, and this unique platform-specific requirement is a major complication for #AccessKit. I want to get this fixed. #accessibility
#Accessibility #gnome #accesskit

reshared this

in reply to Matt Campbell

mastodon - Link to source

Matt Campbell

Efforts to solve this have been in limbo for a while. The GTK team already refused to implement the legacy solution in GTK 4. So AT-SPI has a solution that kind of works when using X11. And there's a draft PR to solve the problem for GNOME Shell on Wayland, but it's only half done. And because the X11 solution introduces its own problems, Orca only uses it for GTK 4 apps. So I'm willing to invest in getting this solved completely.
in reply to Matt Campbell

mastodon - Link to source

Matt Campbell

I could, of course, jump into the code myself. But (1) I don't currently have time to spend significant time on this, and (2) I don't feel that I'm expert enough in AT-SPI, Orca, Mutter, X, Wayland, D-Bus, etc. to implement a solution at all relevant layers of the stack that will be accepted upstream. So I want to make it worthwhile for the experts to work on this.
in reply to Emmanuele Bassi

mastodon - Link to source

Emmanuele Bassi

@tristan957 In February, before FOSDEM, we're going to hold a GTK hackfest, and accessibility is on the agenda; I'll make sure to talk to Carlos about this issue. The main problem is not really going to be implementing an interface in GNOME Shell and GTK, though, but working on Orca and other ATs; sadly, we have not had much luck trying to involve AT maintainers, because there aren't many contributors on that side.
@Tristan Partin
in reply to Emmanuele Bassi

mastodon - Link to source

Matt Campbell

@ebassi @tristan957 Orca is already conditionally using a newer method of keyboard handling in at-spi2-core in GTK 4 apps. So my understanding is that there are two blockers: the X11 solution introduces its own problem (temporarily deactivating and reactivating the focused window), and the Wayland solution (a PR in Mutter) is incomplete.
@Emmanuele Bassi @Tristan Partin
⇧