DEV Community

Don't be a pr*ck: Frontend Engineers and Accessibility

David Lorenz on December 20, 2021

Basic Accessibility isn't hard and it often isn't even a choice. What's hard is your damn stubbornness. The following code will upset ...
Collapse
 
exceedgroup profile image
Exceed Team

Thank you, this post is very important. Accessibility is something so easy to neglect when you personally don't depend on it.

But the truth is, most of us faced temporary disability at least once: tired eyes, broken arm, noisy place, hands full with packages, and more.

You made a very good point:
Understanding is the crucial point of effortlessly using it and implementing it whilst coding.

Today we shared some thoughts on accessibility too: dev.to/exceedgroup/accessibility-w...

Collapse
 
activenode profile image
David Lorenz

That's the point! Thanks a bunch.

Collapse
 
adam_cyclones profile image
Adam Crockett πŸŒ€

sign

In my country, all children are taught a form of sign language, my son here is autistic, he's learning this for a future without words. As a FrontEnd Dev I appreciate the passion for accessibility, the word comes in to our lives not just as information, but knowing what to avoid, walking through a crowd having no choice because the event is set up that way, that's not accessible. That sort of lack of thought is what causes indeed stress.

You are right to push for a more accessible world

Collapse
 
activenode profile image
David Lorenz

Lovely. Thank you for those wonderful insights! Very much appreciated.

Collapse
 
billypurvis profile image
Billy Purvis

Straight to the point and clear cut with great relatable examples. I really wish A11y was taken seriously a developers took an active interest rather than leaving it to other teams to test and report back.

Collapse
 
oniichan profile image
yoquiale

If accessibility were to have a better documentation and had any reward then I'd take a more active approach.

Collapse
 
billypurvis profile image
Billy Purvis • Edited

There are nuances with accessibility and at times it can be very tricky, but I refute there isn't good documentation.

w3.org/WAI/tutorials/
w3.org/WAI/standards-guidelines/wcag/

The tutorials are great and you can inspect all the code. There's countless packages too that help with accessibility for different frameworks.

I really dislike the notion that there must be a reward for it to be worth it. It is morally the correct thing to do, as well as a legal (not that you care, apparently). Hundreds of thousands of people suffer with some form of disability and websites can be impossible for them to navigate. A competent developer should be able to implement basic accessible practices rather than being lazy. The web is for everyone, not just the able bodied - the more we move to a digital first approach for daily life, the harder it can be for people with disabilities if sites don't implement basic accessibility - don't exclude disabled people more than society already does. Be a good person, not a prick.

Collapse
 
activenode profile image
David Lorenz

Would it be a reward knowing it can be costful to be sued? Just to mention one :)

Thread Thread
 
oniichan profile image
yoquiale

I'm from Spain, so I genuinely don't care about the suing part.

Collapse
 
stretch0 profile image
Andrew McCallum • Edited

Now start cleaning the room - start even finding anything

I couldn't agree more. If something's worth doing, it's worth doing now. I believe this is referred to as the the broken window theory

The idea behind this theory is to never let any window broken, every time you found a broken window in your code, just fix it, don’t let it spread in your code base.

Collapse
 
activenode profile image
David Lorenz

Didn't know about that Theory. I just love learning something new. Endorphines hitting. Thanks for sharing.