> There are ways to do all these things but they are compositor agnostic Maybe. But GNOME have found it difficult [0] [1], and the most basic of mouse control

> There are ways to do all these things but they are compositor agnostic Maybe. But GNOME have found it difficult [0] [1], and the most basic of mouse control required a truly massive patch to KDE [2]. Everyone else just shrugs and says to use XWayland. Meaning there is no consistency on how to make basic accessibility work. It isn't clear to me why reporting the mouse's location belongs in the compositor. You may not be rendering to a screen at all. The end result being... Accessibility under Wayland is crap. Accessibility under X11 mostly works. [0] https://gitlab.gnome.org/GNOME/mutter/-/issues/9 https://gitlab.gnome.org/GNOME/mutter/-/issues/9 [1] https://bugzilla.gnome.org/show_bug.cgi?id=709999 https://bugzilla.gnome.org/show_bug.cgi?id=709999 [2] https://phabricator.kde.org/D11468 https://phabricator.kde.org/D11468