![]() ![]() The first of the WCAG recommendations that applies specifically to animation is Pause, Stop, Hide. ![]() Let’s dig into each of those recommendations in more detail to see how we can apply them to our work on the web: Pause, Stop, Hide If you haven’t looked at it in a while, the specification has been updated to version 2.1, and now has even more useful guidance on how we can design web animations that are accessible. These include guidelines for when to provide pause and play controls, limits for blinking or flashing the screen, and advice on when to provide reduced motion options for users with motion sensitivities. While different contexts can affect the details of what you need to do, the WCAG provides a number of recommendations for animated content and interactions. There are also more tactical considerations for making sure the animations on our site are accessible, and that’s where the Web Content Accessibility Guidelines (WCAG) comes in. There are strategic things we can do to make sure our animations have a positive impact on accessibility, like planning how they contribute to the overall UX and ease of use of our site. It’s true, web animation can be accessible! Sometimes it just takes a little extra effort to make sure that it is. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |