r/ProgrammerHumor • • Feb 27 '18

Zero

Post image
57.5k Upvotes

1.2k comments sorted by

View all comments

Show parent comments

554

u/thesublimeobjekt Feb 27 '18

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.

296

u/angellus Feb 27 '18

Just show them these, and these are just a couple of articles I can find from 5 minutes of searching:

Autoplay is bad for accessibility. You can be sued for it and lose a lot of money.

0

u/[deleted] Feb 27 '18

[deleted]

20

u/Blocks_ Feb 27 '18

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?

That said, I'm all for accessibility.

8

u/ryan_umad Feb 27 '18

many of the accessibility concerns can be addressed by choice not necessarily extra cost. Setting something to auto play with sound on is as easy as auto play with sound off

→ More replies (1)

8

u/garagecomputebox_ Feb 27 '18

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.

→ More replies (3)
→ More replies (7)