Follow

You know what: it'd be great if people who need accessibility didn't go around calling other people's work "trash". I get it: accessibility is hard, and required for people to use a computer—but you know how proprietary platforms deal with it? They pay developers. You know what Linux users do for it? They fucking whine about it, and then they go out and say that any effort made is trash.

Well, guess what: stuff doesn't fix itself.

Plus, shitting on the work of the few people that care is a surefire way to ensure that they'll burn out and stop contributing to it.

I'd also appreciate it if people didn't send this whining on my timeline, because guess who is not working on this stuff any more, given that the Foundation couldn't find *anybody* to fund improvements in the accessibility stack.

"Wah wah we could move people from Windows to Linux because it's cheap and disabled people aren't made of money"

Well: you get what you pay for. If you figure out how to make my family eat and put a roof over our head every month, we can definitely talk about improving the accessibility stack on Linux for people who cannot afford to upgrade to Windows 11.

As if people using the Linux accessibility stack today aren't also using installations from 2010 because it's all a pile of jenga. As if the stack isn't made of hacks upon hacks because, unlike macOS and Windows, "Linux is about choice". As if the entire thing wasn't designed in 2001 by Sun to make Java applications accessible for government contracts. As if the only people getting paid in the past 15 years weren't the ones working on web browser.

So sorry I couldn't fix the entirety of the accessibility stack in 9 months. Clearly all I did was trash. Also: sorry that you opened a bug about Shell components not being labelled: I guess writing long threads on Mastodon is more effective than actually writing a patch.

I guess I'm more appreciative of the people who filed bugs, who went through the guts of the screen reader to understand the undocumented behaviours it encodes, who submitted code, and helped out with the design. A lot of those who helped out are also users of the accessibility stack, by the way.

If you cannot use Linux and you have to keep using Windows because of the accessibility stack, then it's sad, but you gotta do what you gotta do.

What you don't get to do is whine, and shit on somebody else's work just because people haven't figured out how to make things appear out of thin air without having to worry about food.

You don't get to be a child, throwing a temper tantrum because you didn't get what you want for free.

@ebassi Acting like a child with a weak temper is… kind of a big issue related to some of the trouble people need that aid for? It definitely creates a toxic link between those who need help and those who try to give it. You need to be like “OK, whatever” — and if it’s not a relative and you’re doing it for free, that gets a lot harder.

Honestly, it’s clear that there’s an interest misalignment here, and the people who are more capable of taking care of such functionality before the complaints happen don’t have the need to implement it (they don’t find themselves affected nor they have to deal closely with people who do), perhaps it should be taken as a priority to deal with even if it’s not relevant to the devs in question… and we should, somewhat resignedly, accept the people we’re trying to help aren’t always properly receptive or appreciative.

It really sucks, but I understand some of the weakest and in most dire need of help are, because of it, also really hard to work with

@ebassi Funding, the eternal problem in FOSS. We have at least 3 talks about funding at each conference, but still no solution. It's just harder with accessibility + FOSS.

@ebassi I'm sorry I boosted that post about a11y lacking. (I just unboosted it.)

I didn't take it to mean that things are trash. My understanding was it was wishing people wouldn't hit roadblocks with FOSS.

But I didn't catch that angle within the entire thread, and I'm sorry about that. 😟

(I do know of a few people who have to use Windows or Mac due to various a11y issues & wish they could use FOSS instead.)

You're doing great work.

Apologies about spreading Stop-Energy.

@ebassi in free software it is often the case where "i need this feature, so i developed it." but with accessibility it's a chicken-egg problem as people who need accessibility features will need it in place before they can better develop those features. sighs. i do agree that there should be a cooperative relationship between users and devs instead of a hostile one, though.

On the other hand, @ebassi, developers of proprietary platforms also don’t passive-aggressively dissing and insulting their users on public platforms, so I guess it goes both ways. We are all human and we have bad days, and not all the time communication is polite or effective. Escalating the situation usually doesn’t help.

Sign in to participate in the conversation
Mastodon

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!