A good article that was written recently about how Wayland still lags behind X11 in terms of accessibility: https://nocoffei.com/?p=451
libre
Welcome to libre
A comm dedicated to the fight for free software with an anti-capitalist perspective.
The struggle for libre computing cannot be disentangled from other forms of socialist reform. One must be willing to reject proprietary software as fiercely as they would reject capitalism. Luckily, we are not alone.

Resources
- Free Software, Free Society provides an excellent primer in the origins and theory around free software and the GNU Project, the pioneers of the Free Software Movement.
- Switch to GNU/Linux! If you're still using Windows in
$CURRENT_YEAR, take Linux Mint for a spin. If you're ready to take the plunge, flock to Debian and design your dream system!
- Those on Apple Silicon Macs can consult Asahi Linux for available options.
Rules
- Be on topic: Posts should be about free software and other hacktivst struggles. Topics about general tech news should be in the technology comm or programming comm. That doesn't mean all posts have to be serious though, memes are welcome!
- Avoid using misleading terms/speading misinformation: Here's a great article about what those words are. In short, try to avoid parroting common Techbro lingo and topics.
- Avoid being confrontational: People are in different stages of liberating their computing, focus on informing rather than accusing. Debatebro nonsense is not tolerated.
- All site-wide rules still apply
Artwork
- Xenia was meant to be an alternative to Tux and was created (licensed under CC0) by Alan Mackey in 1996.
- Comm icon (of Xenia the Linux mascot) was originally created by @ioletsgo
- Comm banner is a close up of "Dorlotons Degooglisons" by David Revoy (CC-BY 4.0) for Framasoft
XWayland is good enough for legacy apps at this point so there's no reason whatsoever to hold onto the ridiculous mess that is x11. Wayland still needs some obscure features parity, sure, but at this point there's not a good argument against it unlike some other 'modernize linux' changes.
Plus there's always LXDE for legacy hardware.
Like someone else has commented, the main thing that seems missing that is important is accessibility. Apparently people that need screen readers or other aids are just hosed as I understand it.
It might be a chicken-and-egg situation though, where nobody focuses on Wayland in this area as X11 is familiar and (still) working, so more display managers moving over might also eventually shift the (probably very limited) Dev resources over. At least I hope so.
Screen readers have been solved for a while via OrCA's updates which cover gtk+ and qt applications under wayland, though all of linux really needs better accessibility to compete in that arena. That being said yes as the zeitgeist essentially forces developers off of x11 more will take their knowledge to wayland which will even further speed up the (unfortunately) niche areas of development that might be missed.
There's also government funding for accessibility improvements in linux (like the Newton project from the German government) which should help solve several of the challenges.
The transition away from X11 had me worried, I felt like the ground was moving out from under me. But XWayland has been working well enough for my necessary legacy apps.
I don't really care what's on the backend, if xorg is no longer maintained I don't see a reason why they should keep supporting it
I've been using Bazzite which ripped out x11 a while ago in anticipation of this, so I'm unaffected. If developers want to move to a new protocol that isn't held down by decades of tech debt, then great. There are a few situations I've seen of people having legitimate issues with Wayland missing features, which will be solved in time, and a whole lot more people complaining for the sake of it to the point of using an x11 fork made by a fascist.
The x11 fork guy also isnt an x11 fork he just made x12.
Removing X11 is a net good since it'll force everyone to a new status quo of sorts and leave all the chuds in the dust.
At this point my biggest issues with Wayland are that it doesn't remember and restore window positions and "keep on top" doesn't work for e.g.: Firefox popup video window or mpv. I know KDE said they're going to implement window position saving into KWin eventually but why doesn't "keep on top" work?
There's a workaround in KDE to allow for PiP on top:
It's waiting on the xdg_pip to be merged (https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/132) which should be soon (it's hard to tell).
Session restore has been finalized in plasma 6.7 so it's basically a matter of time till apps update to it.
good news!

