My gut feeling was that a standard accessibility protocol doesn’t exist yet, but that a Wayland extension is probably the solution.
Looks like I was right: https://blogs.gnome.org/a11y/2024/06/18/update-on-newton-the-wayland-native-accessibility-project/
However that’s a recent proof-of-concept, so nothing generally available at this stage. Details would have to be ironed out, changes upstreamed, the protocol extension accepted, and every graphics toolkit would have to be updated to support the protocol. Seems like a very worthy goal to pursue though and it’s great to see funds allocated for a11y.
I don’t know how that would work with XWayland apps, but given how clunky that gets with stuff like fractional scaling I wouldn’t get my hopes up. The sooner we can native Wayland all the things, the better. X11 must die, regardless of the feeling of the graybeards on the matter.
Oh they definitely exist. At a high level the bullshit is driven by malicious greed, but there are also people who are naive and ignorant and hopeful enough to hear that drivel and truly believe in it.
Like when Microsoft shoves GPT4 into notepad.exe. Obviously a terrible terrible product from a UX/CX perspective. But also, extremely expensive for Microsoft right? They don’t gain anything by stuffing their products with useless annoying features that eat expensive cloud compute like a kid eats candy. That only happens because their management people truly believe, honest to god, that this is a sound business strategy, which would only be the case if they are completely misunderstanding what GPT4 is and could be and actually think that future improvements would be so great that there is a path to mass monetization somehow.