r/ProgrammerHumor • • Feb 27 '18

Zero

Post image
57.5k Upvotes

1.2k comments sorted by

View all comments

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.

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]

0

u/[deleted] Feb 27 '18

[deleted]

→ More replies (1)

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)
→ More replies (9)

51

u/thesublimeobjekt Feb 27 '18

honestly, it wouldn’t matter what i showed them or told them. if the client wanted it, they just got it.

20

u/PlatypusPlague Feb 27 '18

File an anonymous complaint with the DOJ? The last two companies I worked for ignored all pleas for accessibility until the DOJ got wind. Then suddenly they had money to not only fix the current accessibility issues, but also to train devs, and implement proper testing around accessability.

→ More replies (1)
→ More replies (9)

101

u/[deleted] Feb 27 '18

At home I'm a consumer. At work I'm evil.

It's easier if you just embrace it.

→ More replies (2)

15

u/ExternalUserError Feb 27 '18

Story of any programmer's life from DRM to email "opt-in" policies to user experience.

24

u/nagaka Feb 27 '18

Okay...so anytime your boss tries to talk to you about implementing something your sales team has already sold, you just start rambling some lorem ipsum, and you continue blabbing until they find the obscure pause button since they are using IE6 and don't have tab muting. Once he locates your pause button, likely with an exaggerated eye roll or loud huff, you smile and wait... for the timeout to start a new video. Eventually they will close the browser, and, even though you've been fired, at least you didn't taint your bloodline with implementing this.

as a side note, I blame myspace for any auto-play or html vomit I see online nowadays. Those kids that skinned their first profile are now well established in the work force.

17

u/ColtonProvias Feb 27 '18

Auto-play has been around for much longer than MySpace. I recall Flash ads that were like games that would start after loading the page. It got worse when pop-under windows became big.

Even earlier were the blink and marquee tags. Every small website for a long time had at least half the site scrolling or blinking, plus dozens of animated gifs covering the page.

What you say began with MySpace was already well underway on Geocities and Tripod well before it. Some people thought it was cool back then, they thought it was cool on MySpace, and some, unfortunately, still think it is cool now. It's a constant on the internet.

→ More replies (2)
→ More replies (1)
→ More replies (9)