> being "free" just means being under the power and whim of other people
The relevant freedom here is the ability to tweak the software to meet your needs or recruit someone to do it for you. If everyone with accessiblity gripes who isn't a programmer gave detailed, *encouraging* critical feedback to the relevant developers, I suspect the accessibility of free code software would be much better.
More so if there was a bounty fund for accessiblity work on free code projects.
@strypey Yeah, just more "be the change you want to see" stuff. You don’t think we try? We need energy for all that. And some of us don’t have time to be rejected again, and again, and again by big FOSS like Gnome, where all our accessibility issues go into a black hole, just like Google. And GTK4 doesn’t matter *that* much if gnome-shell is so crappy that you can't really use it as a desktop environment in the first place. Even long-time blind Linux users are considering just putting Android on their computers. That shows systemic failure that not even die-hard FOSS bros can't handle.
@devinprater Too many users seem to expect perfect performance from software they don't have to pay for. If users aren't willing to put in either money or effort, how do you think the situation can be improved? Do you really think calling people names ("FOSS bros") on social media helps? Do you think proprietary OS would care about accessibility if they didn't have to compete with OS that are free (libre *and* gratis)?
@easrng @strypey Well Termux, accessibility is very rudimentary. Whenever one presses Enter after typing a command, TalkBack reads the entire screen again, and after the next command, it reads the entire screen again, and so on. So I just SSH into that lol. Or I use clear after each command. But I'd never use Emacs on that.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!