I love that a multi-billion-dollar corporation like RedHat/IBM can ship an operating system with a broken screen reader in 2024 (it’s not just them, it’s true for basically every major Linux distribution today) and, when you point it out, the response is “it’s no one’s fault… it’s all free labour… it’s FOSS, man”. And then: oh, and this charity is paying for one person to work on accessibility support to be implemented now… Anyone else see how fucked up that is?
Why should it take @sovtechfund to fund accessibility work on the Linux distribution of a multi-billion-dollar corporation like IBM. Why the fuck isn’t IBM paying for it?
@aral > And then: oh, and this charity is > paying for one person to work >on accessibility support to be >implemented now
Assuming it doesn’t fall through…
“We’re currently facing a major issue from the GNOME Foundation side. We hope it will be resolved before it impacts the coordination of the STF project, but if not, the future of parts of the project is uncertain.” https://thisweek.gnome.org/posts/2024/05/twig-149/
@aral@sovtechfund because corporations don't deliver Linux as a desktop OS as a product / don't provide it to consumers.
Corporations use Linux mostly for servers, or for their internal tools loaded with specific software to do a specific task.
Often, the tasks, for which they use Linux loaded gadgets, require people to not be visually impaired due to nature of work itself and tools just enhance it, and therefore accessibility is irrelevant in their context of use.
@aral I sympathize but don't understand what's the issue you're facing. Just tried using GNOME's screen reader on Fedora (on Wayland) and it's working pretty much perfectly, with the only exception being Firefox, which doesn't seem to have anything to do with Red Hat, weirdly enough.
@joojmachine I mean you can’t control the screen reader. In other words, the major Linux distributions do not have a functional screen reader at the moment and haven’t had one since they started shipping Wayland by default.
@aral Do you mean keyboard control as in managing to navigate the UI with a keyboard or do you mean controlling the TTS through it? At least with the GTK apps I tested the keyboard navigation worked really well, but since it's something I don't NEED I'm not aware of what exactly is broken with it, but I'll be glad to at least look into what can be done about it :frogCozy: