I wonder if the Linux/free desktop ecosystem will eventually hit a tipping point where new applications and toolkits exclusively target Wayland, and users who stick with X have to run a rootless Wayland compositor on top of their X session, as opposed to Wayland users running a rootless X server (Xwayland).
My new accessibility architecture is certainly Wayland-first, if not Wayland-only. It looks like the protocol that toolkits need to support is going to be way simpler than AT-SPI, and for #AccessKit, it would certainly be attractive to not have to bloat the code with either a new fallback protocol for X, or the old AT-SPI.
Add comment