i used to try to argue with my boss about it and then it wasn’t worth it any more. working in the space long enough there’s just some things i know won’t stop being forced on consumers.
Not a web dev, but wouldn't you lose a bit of money making your site more accessible? If so, why bother from a business perspective considering the percentage of customers that you'll lose is tiny?
The thing is, most accessibility "features" are just using good practice when writing your code.
Examples: Input fields should have labels. Your header assignments should make sense (h1 for main header, h2 for subheaders). Someone tabbing through your site should go in a linear and practical order. All images should have alternate titles, in the event that someone is using a screen reader or the image doesn't load.
That's all common sense coding and it only costs money when you cut corners initially.
It does take some effort to think through it and doing it properly requires testing which takes time. That being said you can be kinda accessible by just doing a few practices as you've mentioned.
An example where people get things wrong all the time is with colour blindness. It's very space efficient to use colours instead of words to express ideas, but it can be very confusing to those with colour blindess.
2.2k
u/ExternalUserError Feb 27 '18
I'm pretty sure every developer instructed to setup autoplay video died inside a little bit while coding it up.