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 [1/x] I can say something about web accessibility in this regard - often making things "pretty" and "UX-y" means deviating from the most natural and accessible markup / structure, especially with web forms. If you ask me, I'd just use native checkboxes, radio buttons, select dropdowns all the time. But rhey are not considered "slick" enough sometimes. So you end up breaking things and the trying (or not) to compensate.

software accesibility rant 

@secretlySamantha [2/x] some other basic things on the web don't have a "native" implementation at all - there is no builtin modal dialog with behavior like proper keyboard focus for instance (except alert, but that's no what I'm ralking about) despite the <dialog> element. So you end up patching up a UI toolkit in a markup language context.

software accesibility rant 

@secretlySamantha (sorry about the typos, typing on the phone)


software accesibility rant 

@setthemfree That's okay, I don't mind typos. That's an interesting point. I'm not a web dev so I don't really know about those things. I guess I have seen sometimes people "make" a button out of a div with an onClick or something which seems really strange to me? Why wouldn't you just style an actual button? (sorry if that are stupid question, this is not my field)

software accesibility rant 

@secretlySamantha I don't think there's a need to imitate a button anymore, they are fully styleable with css, so I just use a <button> whenever I need to. But checkboxes and some other elements are more challenging - the work-around is to still use a checkbox, but make a visual replacement for it while hiding the checkbox itself. Overall though, I think it's a deeper problem - html is not really a UI toolkit.

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.