[opan]

>This is not the kind of gap a community closes by writing better software. It is the kind of gap that takes a decade of full-time employees auditing every label in every default app, a market mechanism that punishes you when you don’t, and a centralized review process to enforce it from above.

We have seen a bigger push to get everything using XDG config dirs in recent years, and also getting everything working on Wayland. These to me seem similar, other than that this accessibility standard would be even more niche, and if it was stated upfront to be made with AI in mind, I think there would be resistance.

Personally I do not want to let an AI tool run loose on my machine, but I do like having ways to script and automate stuff. I like Sway's IPC and that every keybind is also a command you could run. So the explanation of Apple's accessibility stuff sounds cool. I wish I had something like Unity's HUD where I could use a search to select from any depth of graphical menus in a given program instead of having to poke around by hand. If the accessibility standard were like that and allowed more stuff to be done from the CLI more easily, that would be great.