11–20 of 132 posts
Apple has a lot of accessibility stuff, built-in, and API flags exposed, all over. It has some really comprehensive user-facing accessibility controls.
I think I should probably still review the app I'm working on, just to make sure that I'm honoring the users' wishes.
Why does even the thought of 'disabling' animations have to be cast in the context of an accessibility issue? What about those of us that see no need of user interface elements that flollop about doing some kind of 'me Me ME!' dance, when we just want to get things done? I get it, if you're building a webpage maybe that's your artistic vision, and I'm specifically railing on OS animations, but the question still stan…
> “look at my mad skills”
I’m torn about this: there are enough unneeded and horrible animations that I completely understand this point of view of wanted to get rid of all of them.
I also see that as throwing the baby with the bath water. There’s also fundamentally useful and informative animations to tell you something changed, what you’re supposed to do with an element or even what type of content you’re looking at.
As an unintentional experiment, when I got my new phone a few weeks ago I checked “disable animations” first and foremost, and started using the device normally. And everytime I was doing a specific action the screen froze with a round arrow. It took me 5 min to understand that page and app transitions where, well, “animations”, and getting rid of them made for a broken experience.
Same for popups and dialogs. Did it come from the top of the screen or from somewhere else in the app ? If you saw the animation you’d understand it immediately, before even parsing the design of the popup or the content.
I think we’re far away from the time where animations where random animated gifs with no meaning, and platforms are mature enough to use them in more advanced and useful ways most of the time.
Why does even the thought of 'disabling' animations have to be cast in the context of an accessibility issue? What about those of us that see no need of user interface elements that flollop about doing some kind of 'me Me ME!' dance, when we just want to get things done? I get it, if you're building a webpage maybe that's your artistic vision, and I'm specifically railing on OS animations, but the question still stan…
Instead, it explains there is accessibility issue and teaches how to fix that.
It's a bit crap that this needs conscious work by developers to implement - I feel like with just a little more thought put into the CSS spec itself, that animations could have defaulted to following the user's OS settings unless the dev explicitly marked them as necessary. Edit: not meaning to absolve developers of thinking about a11y, or to accuse css spec designers of negligence, just making the point that a syste…
If it matters, it should happen by itself unless someone turns it off.
@namespace url(http://www.w3.org/1999/xhtml);
*, :before, :after {
transition: none !important;
animation-delay: 0ms !important;
animation-duration: 0ms !important;
}
This gives me the best "reduced motion" of all (zero motion), with no effort required from developers, and unlike the official preference, does not leave me vulnerable to the no-Javascript fingerprinting discussed at https://news.ycombinator.com/item?id=30237846 . I haven't noticed it breaking anything important. The same can be put in chrome/userChrome.css (without the namespace header) to remove the annoying animations from Firefox itself, at the cost of occasionally breaking the tab bar (it can be fixed by dragging a tab to blank space and then immediate closing it).
I've never seen a UI animation I thought was necessary.
Why does even the thought of 'disabling' animations have to be cast in the context of an accessibility issue? What about those of us that see no need of user interface elements that flollop about doing some kind of 'me Me ME!' dance, when we just want to get things done? I get it, if you're building a webpage maybe that's your artistic vision, and I'm specifically railing on OS animations, but the question still stan…
I totally get where you're coming from, most employment of CSS animate and transition is excessive and reduces UX. The rule is that you should never have to wait for a UI animation - That said, UI animations done correctly, which are subtle and extremely short, do enhance perception of UI controls state and transitions. But I can't blame people for the broad hate towards animation on the web, so much of it is done po…
Why does even the thought of 'disabling' animations have to be cast in the context of an accessibility issue? What about those of us that see no need of user interface elements that flollop about doing some kind of 'me Me ME!' dance, when we just want to get things done? I get it, if you're building a webpage maybe that's your artistic vision, and I'm specifically railing on OS animations, but the question still stan…
> that's your artistic vision > “look at my mad skills” I’m torn about this: there are enough unneeded and horrible animations that I completely understand this point of view of wanted to get rid of all of them. I also see that as throwing the baby with the bath water. There’s also fundamentally useful and informative animations to tell you something changed, what you’re supposed to do with an element or even what ty…
I don't get it. That sounds like the OS is fundamentally broken that it assumes a hard coded timer is required before it does the next step.
Why does even the thought of 'disabling' animations have to be cast in the context of an accessibility issue? What about those of us that see no need of user interface elements that flollop about doing some kind of 'me Me ME!' dance, when we just want to get things done? I get it, if you're building a webpage maybe that's your artistic vision, and I'm specifically railing on OS animations, but the question still stan…
These in-between states gives us well-needed information and are not artistic at all. Sure, they can be emulated badly, but for example iphone’s app switcher is imo a very natural implementation of how it should be done. Won’t make the action take any more time, but it does instruct on what happens very accurately. Compare it to i3’s instant desktop switching, which gives us barely any info to work with.