It is true to in Wayland you can write protocol extensions or custom compositors to get around these limitations. However, what many fail to realize is that the primary challenge in Linux accessibility is not just a technical problem as it is getting people to actually implement specs and care about it. Even with atspi itself, a standard that has existed for over a decade, major apps like Firefox often do not implement the atspi Collection interface. This is not a criticism but rather a practical statement that accessibility needs to be standardized and easy to implement for it to actually have any use. Orca works on Wayland but only in certain compositors. For assistive technology software developers, this pattern of supporting specific compositors is not feasible. It is important to understand that we need to support assistive tech generally. Not just ad hoc extensions for certain types of disabilities.
Wayland has no concept of global coordinates or global key bindings. The protocol itself is designed around atomicity which is a nice concept, but is fundamentally in conflict to the need of assistive technologies to control the entire state of the desktop globally. As such, atspi methods like get_accessible_at_point are impossible in Wayland.
I agree that X11 cannot be carried on forever, but with the current state of Wayland, the phasing out of X11 will have the effect of drastically harming the accessibility ecosystem. Accessibility is not a "nice to have", it is essential to the mission of community inclusion and wider goals of adopting desktop Linux in education and government.
There is a long tail of more-or-less critical stuff that depend on X11 and do not have working Wayland substitutes. While the tail has been shrinking for every year, it will be decades if ever until all can be realistically migrated. Consider the Lindy Effect and that some of these systems have been running for >10y already. Consider shared but secured environments at universities and research institutes. Consider obscure hardware incompatibilities and hardware-specifix performance issues which might never be fixed.
On the software side, acessibility aside, there are a lot of VNC and other remote-X setups out there with no viable replacement in sight (yet).
Alsa, pulseaudio, pipewire and jack can all coexist and so can display servers.
I understand GNOME and RedHat will do things their way. I understand distro and GUI framework maintainers wanting to reduce their load. I understand people who like Wayland, want it to succeed, and want to evangelize. I do not appreciate when it turns into tribalism, forcing of monoculture and insisting "X11 is deprecated".
---
OP is from 2023 but as they note in their update, the situation is fundamentally not that different 2y later. Are maintainers and decision-makers really sincerely imagining that a supposed deprecation and removal of X11 can be forced onto the wider community over a couple of years from now?
I've been using wayvnc for probably 5 years now? Works great. Sway can output fine to virtual-crtc out for headless mide; I expect other compositors can use this part of your GPU too. If you really desperate & your Wayland server just can't for no reason, get a DisplayPort dummy plug for $15.
I know less about others but krfb and gnome-remote-desktop are both there. KDE is recently kicking off a bunch of work to make sure their login manager is remote friendly too.
> I do not appreciate when it turns into tribalism, forcing of monoculture and insisting "X11 is deprecated".
Most of the devs doing X11 agreed en masse that it was at a dead end and not worth caring for anymore. It's not tribalism. It's technics.
Still, the gaps are there and don't seem to be filled anytime soon, despite the progress you mention.
For example, mouse and keyboard support and libei, libinput, or nothing (looking at you, weston). You never know what you're going to get and so applications that need to do basic keyboard/mouse things have to guess. It doesn't work all the time. In X11 it does.
Another example, accessibility features. The only wayland compositor that supports screen reading is GNOME's. They invented two new protocols, incompatible with all existing linux accessibility libraries. Only GNOME's wayland compositor and userspace applications use them.
So, in summary: one's experience can't be extrapolated with wayland because there is no single wayland.
* With 0 implementations, Wayland is good for 100.0% of users
* With 1 implementations, Wayland is good for 95.0% of users
* With 2 implementations, Wayland is good for 90.2% of users
* With 3 implementations, Wayland is good for 85.7% of users
* With 4 implementations, Wayland is good for 81.5% of users
* With 5 implementations, Wayland is good for 77.4% of users
* With 6 implementations, Wayland is good for 73.5% of users
* With 7 implementations, Wayland is good for 69.8% of users
* With 8 implementations, Wayland is good for 66.3% of users
* With 9 implementations, Wayland is good for 63.0% of users
* With 10 implementations, Wayland is good for 59.9% of users
From day 0 Wayland put their idea of a beautiful design above the needs of users. It's hard to see how we can claim to be inclusive when even our most basic decisions are hostile to large groups of users.
I never thought I would say this, but after 30 years of open source and Linux I don't see much of a bright future. Everyone I know from the community back then has moved on to using a Mac because of these issues.
I'm not sure about the modern state of Wayland but last time I saw it the situation was terribly messy and I was forced back to X11 because I rely on screensharing to do my job properly.
It's your bubble.
At the same time, I know many who have been forced to use Macs (macOS is new windows), but keep using Linux outside of work.
The problem, at root, is Wayland. Zoom has some kind of workaround it seems, but it's not working yet in COSMIC.
The result was sad: speakers having to speak with their slides being run by one of the remote speakers, and anyone who recognized the computer running Zoom as Linux surely strengthened their conviction never to try that.
It always boggles me how supporters of Wayland (or other things that are new and better and worth deprecating the old one for) miss this. It only takes one experience like this to make the average person view Wayland (or Linux as a whole) as a total failure.
I use Gnome, and Wayland sessions have been flawless for years. Screen sharing works, everything works.
Also, I've seen colleagues struggle to get screen sharing working on both Windows and Mac; most OSes now don't just allow any program to read from any window, so if someone forgets to allow a permission somewhere, no screen sharing.
https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_arti...
In many in-person conferences in my field they started to request a copy of the pdf file before the talk, that will be projected and shared using a dedicated computer.
Screen sharing worked fine for me on Wayland 3+ years ago (and still works today), so Wayland isn't inherently the issue.
The most promising work towards improving accessibility support in Wayland was the work done on the Newton protocol:
https://blogs.gnome.org/a11y/2024/06/18/update-on-newton-the...
Unfortunately, the project appears to have stalled. I think the Linux desktop just lacks important strategic investments, and this is one of them. For now, existing accessibility bus support in UI toolkits is mostly being leveraged. Some compositors (i.e. KDE's kwin) also can support some old X11 features used for automation/accessibility (i.e. XTEST works, although applications will need to be granted permission first)
The situation is somewhat similar for IME: There are a few protocols for handling basic IME/text input, but it's not really finished, and further work on text input protocols has stalled.
This is not an ideal state of affairs at all, and it is a major threat to the future of the Linux desktop. I doubt many Wayland proponents (of which I do consider myself to be one) seriously believes that shipping Wayland-only without robust support for accessibility or internationalization is really a good idea. It's basically only happening because progress on Wayland has been rather slow, for many reasons, a lot of which really aren't in the control of open source contributors or maintainers. However, at the same time, maintaining both X.org and Wayland paths everywhere forever is also not sustainable: with limited resources, there simply has to be a point at which the line is drawn. X.org outside of XWayland has been unmaintained for a fairly long time.
On the flip side, if anyone working on Newton or Wayland accessibility has any idea what anyone on the outside can do to help things along, we'd love to know. I really hope that one of the major investors in the free software desktop (Valve? Red Hat?) can be convinced to help shift some resources to this. It's one thing to have some software work somewhat sub-optimally (as is the case with KiCAD), but it's a bigger issue that users who upgrade to newer free operating systems may face a system that is not usable for them because of limited accessibility tools. Possibly a compliance problem for companies that wish to ship systems based on free software desktops.
Two things: First, yes, a lot of Wayland's missing features absolutely were intentional omissions in the name of security. This is even almost understandable; the only difference between a vital a11y tool and horrible malware is whether the software acts on behalf of the user or against them, there is no technical distinction. Second... Wayland is almost 17 years old. If it was 2010, I would readily accept that it was early WIP software, but we're past the point where 'they just haven't gotten there yet' is convincing.
> However, at the same time, maintaining both X.org and Wayland paths everywhere forever is also not sustainable: with limited resources, there simply has to be a point at which the line is drawn. X.org outside of XWayland has been unmaintained for a fairly long time.
I'm actually cautiously optimistic that https://gitlab.freedesktop.org/wayback/wayback or the like will help significantly; sharing as much of the stack as possible should reduce the maintenance burden.
Major distros and DEs only recently started actually migrating to Wayland by default and only now you can see a decent variety of new nicknames in various development channels.
Firstly, the problem is when you put it this way, people think that Wayland can't do accessibility, or screen capture, or automation. It is true that it is intentional that a Wayland program can't simply expect there to just be the ability to go and read screen contents (or inject inputs, or intercept input, or ...) without permission, but that's not just security, I think that's also somewhat a result of the fact that the Wayland core protocol is really not applicable to any specific use cases, and is really just the bare bones necessary for programs to talk to a compositing system. For example, you can't really do proper desktop applications as we know them without something like xdg-shell, which isn't part of the core Wayland protocols, and yet it's totally possible to have Wayland protocols that do things like screen capture, and they can be as "standard" as the ecosystem wants. (Unfortunately that stuff usually gets relegated to DBus presumably because nobody actually wants to support authorization on the Wayland side, but oh well.) To put it more clearly, there is absolutely no reason that Wayland desktop systems can't just expose every bit of functionality X.org allowed to all apps if they want to, security be damned, and the protocols can be standardized; wlroots compositors usually do basically this after all, and I think these days the protocols are all ext protocols upstreamed to wayland-protocols. (And in practice, secure alternatives that allow for proper automation/accessiblity/etc. are very likely to exist and be supported by all major desktops in the long run.) I think people get the wrong idea that Wayland is telling them they can't ever do this, but it's really just telling application developers they can't absolutely count on being able to do it like they can in X.org.
Secondly, the "Wayland is x years old" thing just doesn't make sense, this has to stop. This isn't a project with full time employees like at your job, it's a distributed open source effort. The investments are incredibly uneven both over time and for specific areas of interest. Until about 10 years ago, Wayland was basically not usable at all for almost anybody, and until the last few years the vast majority of Linux users were using NVIDIA GPUs and couldn't really use Wayland without pretty terrible bugs (XWayland was especially broken. AFAIK to this day NVIDIA is working through XWayland issues that never existed on AMD/Intel.) The momentum Wayland had back when nobody could really use it was pretty damn bad. This isn't really terribly unusual for open source projects of this nature though; I mean look at how catastrophically long it took for GIMP 3.0 to come out, and that is a lot less complex and multifaceted than entire desktop systems.
I'm not saying that the initial work done on Wayland was bad or not important, but the majority of work done on making Wayland usable in real life happened in the past few years. 17 years ago or so, all that existed of Wayland in practice were some ideas about how to design a graphical interface system to succeed X.org. (and at that time, Wayland's design was probably too radical anyways: I don't think it's clear that all Linux users would've accepted things about Wayland that hardly anyone complains about today, like the pervasive use of compositing without a traditional fallback. Today X.org is basically the only commonly used windowing system that can properly operate without some form of compositing.)
This isn't the first case like this. The Linux desktop ecosystem has been getting worse for years, as a few major players force systemic changes that make the system more complex, more brittle, and less compatible [with anything that came before it, or that doesn't use the same core components]. I've been using a Linux desktop for 25 years and it's never been more complicated or broken.
It's part of a larger trend of tech enshittification, but seems especially sad in the Open Source world. I always figured a decentralized, leaderless ecosystem could fight incumbent stagnation and selfishness, through the creation of alternatives. But some things there's just no alternative to. And apparently the list of things without alternatives grows.
For instance, Scribus uses QT which supports wayland, but they hardcoded a check to explicitly detect wayland and exit if it's found. You get the generic QT "supported backends" message that lists wayland, but if you actually try to use it the logic resets your choice, gaslighting you into thinking you typed the backend detection or override env var isn't working.
You can get around it using a wayland-flavor that they forgot to reject, and there are bugs (not sure how many are from wayland itself and not Scribus though) so I get not wanting to handle wayland related bug reports, but having buggy software is often than having no software at all so I wish they didn't choose the nuclear option (and now they get "please support wayland" bug reports instead, so...).
I think Krita is the same? There were a couple programs I had to dig into the code to work around blocker mechanisms to get to run.
Maybe it's better now with Wayland and that check can be removed. I don't know.
See: https://bugs.scribus.net/view.php?id=16998 and https://github.com/scribusproject/scribus/commit/74d8d7ef7
Sure, a lot of code changes need to happen, but they only need to happen once. There's no real reason to discourage people from stepping closer to the end goal.
<expletive> ANY Linux project that strongly breaks backwards compatibility.
Not surprised that it's still messing with people even this late in the game.
I don’t really care about your opinion here.
Also no one is preventing this app from working, for whatever reasons the devs just haven't got it working.
Open source software is about freedom. Freedom to say fuck backwards compatibility or freedom to use X11 for the next 100 years.
Also the freedom for the X11 devs to say they don't want to maintain it anymore...
Personally I think a full forever commitment to the past is a form of folly which I can only laugh at the premise of.
AT-SPI is a protocol for talking between the compositor and an accessibility reader.
It's not in Wayland's jurisdiction to define how AT-SPI should be used.
