![](https://files.wehavecookies.social/accounts/avatars/111/706/674/124/996/073/original/9ef4db8d133efe87.jpg)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
8·
5 days ago@Chewy7324 @GolfNovemberUniform I’d say as soon as screen readers work properly under Wayland, they could drop X11 builds. But they should definitely not do it before fixing that.
Developing free open-source software and games…
@Chewy7324 @GolfNovemberUniform I’d say as soon as screen readers work properly under Wayland, they could drop X11 builds. But they should definitely not do it before fixing that.
@nick I don’t know. I can understand both sides.
Users searching for solutions of their problems, stumbling upon a new functionality and test it out without doing what it does.
Developers specifying what it does and therefore expect people would know what they are doing.
Anyway a compromise got merged to make it more difficult for users to accidentally mess up. Which is probably good. But I don’t think you need to handhold users all the time…
@possiblylinux127 That would definitely be part of it, I assume. Does Wayland already track text rendering and its contents?
Because somehow text from any UI would need to be detected.