meloukhia (
meloukhia) wrote in
dw_accessibility2011-03-20 07:25 pm
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
Blocking animations?
Animations and flashing things (including animated user icons and mood icons) basically break my brain and they keep showing up on my reading list, much to my dismay. I'm wonder if it's possible to add an option to the user settings to block all animations on the site (in my innocence about web development, I have no idea how difficult this would be)? I know this is an accessibility need for other people as well.
no subject
no subject
no subject
I have issues with flashing graphics and Flash animation and horrible site design changes; I take control of all of those through using browsers that allow me to set how that sort of content is displayed. I was pointing out NS because it sounded to me like s/he might not have heard of it, if they're having the issues described above. *shrug*
no subject
Also, do you consider it controlling other people's content that I have my default settings to not display videos? Because that's in the code right now, I checked a button for that. I could also check a button to not view images at all, to not honour cut-tags, and to not view other people's layouts ever. Do you consider all that controlling other people's content?
Honestly, I suspect, as I said, that this isn't something the site can do, but you're coming across as very rude and actively hostile to someone asking if the site can implement the same sort of thing that they do right now for videos and images but for animated gifs. meloukhia isn't asking for people to not do animated gifs anymore than I'm asking them to not put up videos.
no subject
no subject
no subject
no subject
It's easy enough to override all the mood themes to simple smileys with our current configuration, so that's something.
no subject
no subject
no subject
no subject
no subject
no subject
no subject
no subject
no subject
no subject
no subject
In terms of an immediate user-side fix, if you're using Firefox you can tweak some settings to stop animations from playing: http://kb.mozillazine.org/Firefox_:_Tips_:_Animated_Images
There's also css "solution" to hide all gifs:
You could add that to your journal style's stylesheet, and so long as you were viewing the page in your style, all gifs would be removed.
Of course, gifs aren't only used for animation, so it will likely remove lots of already-static graphics as well. Because of this, and the propensity for many site graphics (logos, icons, etc) to be gifs, I doubt it could be used as a site-wide solution :/
no subject
(Yes, I know there are extensions that do that-- but they're very kludgy and don't always work.)
no subject
The fix
no subject
no subject
no subject
no subject
no subject
Opera has put an enormous amount of effort into making site-specific settings readily available to the user: cookies, JavaScript, animated icons, pop-ups, frames, etc. There are a huge number of basic browser features that you can get to with a single keystroke. The browser comes with a bunch of accessibility styles for a variety of needs (e.g. high contrast, high zoom, etc.) and they are user-configurable if you know CSS.
BUT.
Firefox has that excellent user community which has been building extensions for years, so we get things like mouseless browsing and the UIUC accessibility extension. Those add-ons just don't exist for Opera. So I use both.
no subject
no subject
no subject
http://www.dreamwidth.org/customize/options
no subject
no subject
This entry explains how. I'm sorry it's a mess from all the edits, I don't understand CSS enough myself to write a new coherent explanation incorporating the various refinements from the comments.
no subject
I hope that helps you at least for the moment?
no subject
no subject
no subject
no subject
It would also only be a solution for one website. If somebody is sensitive to animation, they're probably sensitive to animation everywhere -- so it's better to give people a solution that will work everywhere, not just on one website.
no subject
no subject
Also it wouldn't cover things like people including animations in a post or a comment.
I agree 100% that changing a setting in the user's browser to block animations is the best idea in this case.
no subject
Again, I have no idea if putting in a ticky box would be difficult or helpful to users who can't deal with animations, but I think discounting it as a possibility because some users don't do image descs on their icons and probably won't check a ticky isn't the right reason to discount it.
no subject
I would much, much rather say "we can't guarantee that you will never be exposed to animated icons, so here is the information on how to block animations on the level of your browser" than say "tick this box to block animated icons. Maybe! If you're lucky and if people don't forget to identify their icons as animated!" The risk of causing harm is just too high.
no subject
I'm not under the mistaken impression that you have all the time and energy and spoons to be everywhere all at once, but it just comes across as really dismissive to respond that way several months after the original post, and to not explain why your response was a link to how to change things at the browser-level. You've explained it now, and explained why my suggestion isn't feasible in a way that makes sense, and I appreciate that.
no subject
I am sorry that my attempt to be helpful and to provide someone with the information they need to help make the internet more accessible to them came across as dismissive.
no subject
It wouldn't be too difficult for DW to run a routine when somebody uploads an icon that detects if that icon is animated, and sets a flag in the database. However, while that alleviates the possibility that somebody might forget to tick the box, it shares a number of other problems:
- It would only work on icons. (It's possible that it might be able to get it to work on mood icons too, but I don't know about that.) It wouldn't work for any images that people include in the post itself - even if those images happen to be of somebody's icon. Icon posts would thus still show animated icons, even if you selected not to see animated icons.
- It wouldn't be possible to 'freeze' the image on its first frame without storing what's essentially an entire extra userpic's worth of information. (Meaning that if somebody had 100 icons and they were all animated, the extra work to isolate the first frame would mean DW would have to store 100 extra icons' worth, making a total of 200 icons' worth. And no doubt people would abuse this feature and set the first frame to flick by too quickly for anybody to notice, so they could then link to the 'static' version on purpose.)
Basically, it comes down to the fact that DW simply can't do this feature in a manner that would work for everything, and even if it could, it would have to do so in a manner that wouldn't make for a very good experience on the part of the user who opted not to see animated icons.In other words, there would only be two choices at that point: Load the image (animations and all) or don't load the image at all. Granted, not loading the image is probably better in this case, if a person truly needs it, but it's something to bear in mind, and it would make it difficult for somebody to tell if it was broken or simply not displaying.
Using the browser-based feature means that not only will every image be checked for animations, but you'll also get to see a non-animated version too, rather than the image simply not loading.