![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Autoplay is an Accessibilty Issue
Dec. 14th, 2014 01:59 pmI don't know how common sensory issues are. I can see how common bad design which worsens sensory issues can be.
For example, backup beepers, sirens, and flashing lights are often used as warning signals. But they can inflict incapacitating pain. For another example, grocery stores often use machines that go beep, bright strobing flourescent lights, and scented detergents. And web sites often use autoplay.
Why? Why on earth? Why?
I currently use Firefox. I have used various settings and add-ons to disable autoplay and disable animations. But. they. don't. work. For some reason, Firefox's accessibility settings do not work in Firefox any more. And Mozilla's own site uses autoplay on some pages.
What is going on here?
P.S. It turns out that the latest painsource was a flash video. Between Firefox 34 breaking several add-ons, Firefox 34 breaking the Flash plug-in, and the new Flash plug-in breaking other add-ons, I had to find a new add-on to block Flash again. An ugly solution. Why can't Firefox just block all animation/video by default and include toggles to run any of that if you want to?
P.P.S. Obviously it's not the worst accessibility issue. But it is one of those insulting accessibility issues where people have gone out of their way to make things less accessible for no discernable reason.
For example, backup beepers, sirens, and flashing lights are often used as warning signals. But they can inflict incapacitating pain. For another example, grocery stores often use machines that go beep, bright strobing flourescent lights, and scented detergents. And web sites often use autoplay.
Why? Why on earth? Why?
I currently use Firefox. I have used various settings and add-ons to disable autoplay and disable animations. But. they. don't. work. For some reason, Firefox's accessibility settings do not work in Firefox any more. And Mozilla's own site uses autoplay on some pages.
What is going on here?
P.S. It turns out that the latest painsource was a flash video. Between Firefox 34 breaking several add-ons, Firefox 34 breaking the Flash plug-in, and the new Flash plug-in breaking other add-ons, I had to find a new add-on to block Flash again. An ugly solution. Why can't Firefox just block all animation/video by default and include toggles to run any of that if you want to?
P.P.S. Obviously it's not the worst accessibility issue. But it is one of those insulting accessibility issues where people have gone out of their way to make things less accessible for no discernable reason.
