* Dell latitude with old Intel 8gen CPU, it works fine (Linux kernel causes problems with PSR, but this has nothing to do with Wayland and disabling it fixes the problem, same thing with cstates)
* Dell latitude with 10gen CPU, works fine.
* Huawei d15 with Ryzen 3000 Apu, works fine.
ok. for accessibility it's fair enough as a critique.
I don't use it so can't say. As far as I can tell this hasn't been in focus at all. but most of this is on the toolkit side, not Wayland (even though here one thing is mentioned as Wayland specific, just briefly went through the post)
Does it matter? Your claim is that everything works, and I am here to tell you that I am a real person running real machines that do not work. Unless you're planning to fix the particular bugs and missing features that I'm hitting I don't see where the specifics actually matter. (Anyways, the first machine is a https://wiki.archlinux.org/title/Lenovo_ThinkPad_T490 with Intel graphics; this appears to work but is less stable than Xorg. The second machine is a https://wiki.postmarketos.org/wiki/Lenovo_IdeaPad_Flex_3_Chr... that doesn't run Wayland at all, which I grant is bizarre since the stock ChromeOS uses Wayland. You are welcome to point out that this is more than a little off the beaten path, at which point I will of course point out that Xorg somehow handles it just fine.)
> but most of this is on the toolkit side, not Wayland (even though here one thing is mentioned as Wayland specific, just briefly went through the post)
It varies; a11y isn't a single thing. Deep application integration to allow eg. screen readers to work well probably needs toolkit integration. But there are also things like dwell click, which is really helpful when my RSI is flaring up. In X, I just run `mousetweaks --dwell` and it works, and it works in any window manager or desktop environment, with absolutely no help needed from toolkits or applications. In Wayland, it's sometimes available on a per-compositor basis, which I would describe as purely inferior. On which note, observe that you've linked a blog post about a prototype for GNOME. They note that they're open to working with other desktop environments, but 1. that means it doesn't exist as of that blog post, and 2. I've seen how GNOME operates over the years; I fully expect portability to be a very distant second priority, and whatever they export will be an attempt to force everyone else to do everything the way GNOME does, which will go poorly. I have no interest in ever going back to GNOME, so the actual takeaway, AFAICT, is that the a11y situation on Wayland is bad and will remain bad for the foreseeable future.
if this is so, I can admit I'm wrong. so not everything works for everyone.
For myself and members of my family, I can say that absolutely everything works on gnome. And I have several machines, spread over several cpu and gpu generations, and different form factors that confirm this. not only those 3 laptops I mentioned.
Could it be that since you are not using gnome that you are hitting those problems? My experience is exclusively gnome, so maybe this is it?
a11y aside of course... given that this was not really finished. or seriously worked on.
It certainly could be GNOME vs not-GNOME. That doesn't really help me, either way, but it's not hard to imagine that different compositors have entirely different quality levels.
if you ever come into a position that you could try or would like to try gnome, I would encourage you to do it. maybe you could eliminate that bad opinion of Wayland (or confirm it)...
yes gnome has a vision of how the desktop should look like and strong behavior of "my way or the highway", but maybe you get surprised how well it works. especially on fedora.
I assumed wrongly other people (you mostly) use gnome by default, which obviously is not the case. in that case I could see it as a problem since not everyone has red hat resources for desktop development.
* straight up doesn't work on at least one of my laptops (driver problems AFAICT)
* does run on the other one, but crashes at an alarming rate compared to Xorg
* breaks all of my accessibility tools (some have (worse) replacements, some don't)