GNOME Bugzilla – Bug 649556
Need to start to check how eventual Wayland move would affect ATK/AT-SPI2
Last modified: 2021-05-20 06:51:21 UTC
Current accessibility stack is based on a X11 world. But a new actor has appeared recently, Wayland, and the linux stack would move to that eventually, as this mail summarizes:
And for example, clutter has already an experimental Wayland backend.
It's true that this move will not be soon, but it would be a good idea to check how this affects ATK and AT-SPI2.
In general ATK is agnostic to the window system, so this move would just affect some details of the implementation, like some AtkComponent method implementation (see ), or the a11y bus discovery (see ).
*But* some parts of the API are also tied to the window system (ie: key event definition), so it would be good to review how Wayland does that kind of things, to check if they are compatible, and how abstract that.
ATK Hackfest Conclusions:
* This is important.
* We need to track it.
* No one in the room has the needed experience to discuss it/make decisions.
[Mass-reassigning open atk bug reports for better trackability as requested in https://bugzilla.gnome.org/show_bug.cgi?id=653179 .
If you have watched the previous assignee of this bug report as a workaround for actually getting notified of changes in atk bugs, you yourself will now have to add email@example.com to your watchlist at the bottom of https://bugzilla.gnome.org/userprefs.cgi?tab=email to keep watching atk bug reports in GNOME Bugzilla.
Sorry for the noise: Feel free to filter for this comment in order to mass-delete the triggered bugmail.]
> * No one in the room has the needed experience to discuss it/make decisions.
OK, so which experience was missing, precisely?
(In reply to comment #3)
> > * No one in the room has the needed experience to discuss it/make decisions.
> OK, so which experience was missing, precisely?
Experience with Wayland. In short what happened if that we had plenty of tasks and discussions to make with respect to the accessibility stack, and taking into account that we didn't have anyone at the room with Wayland experience we decided to skip the item.
FWIW, GNOME is starting to coordinate the global effort:
And I have updated the accessibility section:
Assuming this is obsolete in 2021. (If not then please file dedicated issues in GNOME GitLab - thanks!)