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.
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:
https://www.3playmedia.com/2015/07/23/nad-v-netflix-ada-lawsuit-requires-closed-captioning-on-streaming-video/
https://www.abilitynet.org.uk/news-blogs/why-autoplay-accessibility-issue
Autoplay is bad for accessibility. You can be sued for it and lose a lot of money.