software accesibility rant 

okay so this is totally not the reason why you should care about accessibility but I find it so weird that devs hardcore don't care about accessibility because of a very good reason: in 90% of the cases making something more accessible means "make it easier to parse for technology" and like, why wouldn't you do that? That's gonna make your own life so much easier. Testing, monitoring, benchmarking, debugging, all the things are helped by that!

software accesibility rant 

@secretlySamantha @petrichor in general, the problem isn't "developers don't care". We've been through this with security

Some devs don't know about the topic

Many devs do know and care but don't understand what to do about it, and need clear guidance and tools that help, or it'll always come last after getting things working

Many devs know and care but their managers and product managers won't give them adequate time and resources, approve features/designs that make it harder or impossible to do things securely/accessibly, and otherwise screw the devs over

The "devs don't care" model doesn't help! They mostly DO care, once they're aware of the need. They just have to care about a great many other and often conflicting things. Go after designers and product managers, and the rest will follow

software accesibility rant 

@calcifer @petrichor That's actually a really good point and I'm kind of embarrassed I didn't think about this given that I'm currently experiencing it myself at my job (though on a different topic). I do think that it can be both though.

software accesibility rant 

@calcifer @petrichor I guess that making a case that it helps with things like testing could make a good case to managers as well to bring it higher on the list. It honestly kind of baffles me that UX and accessibility aren't thought of as the same thing because they really should be! (but I guess that's a different topic)

software accesibility rant 

@calcifer @petrichor another (reformist approach) is to try and sneak accessibility things into major frameworks like React. I don't actually have numbers on this, but I imagine that the number of buffer overflow exploits greatly decreased when people moved away from raw C and started using frameworks that didn't have that problem. I think the same can be said for accessibility.

Follow

software accesibility rant 

@calcifer @petrichor and to be fair, a lot has already been done. I've seen the idea about aria labels that "the best thing to do about aria labels is nothing. You're more likely to do something wrong when you try to do it manually instead of just using the built-in stuff." So while we still have a ways to go, there are things out there! This is true for users and devs alike, but the best way to ensure something is done is to make sure nobody has to think about it

Sign in to participate in the conversation
LGBTQIA+ Tech Mastodon

*Due to increased bot signup, manual approval is required. Please write some applicable request text on signup.*

This Mastodon instance is for tech workers, academics, students, and others interested in tech who are LGBTQIA+ or Allies.

We have a code of conduct that we adhere to. We try to be proactive in handling moderation, and respond to reports.

Abridged Code of Conduct

Discrimination & Bigotry Won’t Be Tolerated.

We're not a free speech absolutist. We're not interested in Nazis, TERFS, or hate speech.

Respect Other Users.

This instance is meant to be a friendly, welcoming space to all who are willing to reciprocate in helping to create that environment.

Consent is Important in all contexts.

If you’re ever unsure, ask first. Use CWs where required.

Listen; Don’t Make Excuses.

If you’re accused of causing harm, either take some responsibility or ask moderators for help.

Use the Report Feature.

Our moderators are here to listen and respond to reports.



For more detail, please
Review our Full Code of Conduct


This instance is funded in part by Patreon donations.