Boosts appreciated.
I'm close to moving back to Windows. I can't tell you how frustrating it is to hold oneself back, deny oneself better and easier accessibility in the name of open source, when many open source developers don't give a crap about accessibility, and/or don't educate themselves on it. KDE connect, GSConnect, all were inaccessible for one reason or another, not the least because of Gnome-shell's terrible accessibility issues. That was just the last straw. With the only thing holding me to Linux being Emacs+Emacspeak, I think its time to quit Linux and just use what actually works. It's interesting how being "free" just means being under the power and whim of other people, a mass of developers who have no insentive for accessibility, rather than a cohesive company who does. This is serious, and I want every developer to understand this, understand my deep frustration with FOSS.

> 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 @strypey tbh android-x86 with taskbar and termux probably wouldn't be an awful setup.

@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.

That does sound irritating. I presume you have reported this to the TalkBack and Termux developers and been ignored? If so, I agree that's not good enough. Can you link to the issues you filed?


Sign in to participate in the conversation

A fun, happy little Mastodon/Hometown instance. Join us by the fire and have awesome discussions about things, stuff and everything in between! Please read our rules before doing that, though; applications without the password that confirms you have done so will be rejected. Admins: Talon and Mayana.