Skip to content

Moving pictures, animation, and accessibility

When you publish video content, or use animations, the onscreen movement can cause accessibility problems, or even outright harm. This post explains how to avoid that.

It’s part of a series called Accessible Intentions, which is for people who want to do the right thing for accessibility, but aren’t sure how. For more context and definitions of some terms I use here, read my introduction to the Accessibility Intentions series.

Cheat sheet: Just tell me what to do

The easiest way to avoid your videos or animations causing accessibility problems? Don’t have any. This also means you avoid worries over captioning and transcripts and audio description. Ask yourself if it’s really necessary to publish that video, or use that animation effect.

If you definitely want to publish a video or use an animation, make sure that:

  • it doesn’t play automatically.
  • there is a usable way to stop, start and hide the movement
  • there are no more than three flashes a second

Why is it important to think about on-screen movement?

More and more content is in video form these days. Many people love to watch videos, and they can be a helpful way of sharing information.

Animation effects, like parallax scrolling and elements that slide into view, tend to be used for flourish and flair, rather than function.

In either case, movement on a screen can cause problems for lots of different groups.

It can trigger seizures for people with photosensitive epilepsy, or vestibular migraines for people with a range of conditions. These can cause serious harm.

It can also be very difficult for people with slower cognitive or reading skills to concentrate when there is too much movement on the screen.

What does WCAG say about movement?

This blog groups together a few different WCAG criteria.

At the minimum level of basic accessibility (WCAG A), the ‘pause, stop, hide’ criteria means users must have a way to stop a video or animation longer than 5 seconds: WCAG 2.2.2 Pause stop hide.

You must also make sure that the video or animation has less than 3 flashes a second. There is a basic requirement for this in WCAG 2.3.1. and a subtly different gold standard (AAA) level in WCAG 2.3.2. The difference is quite technical, though. The simplest thing is to never have more than 3 flashes a second. This meets the AAA requirement.

For gold standard accessibility (WCAG AAA), you should also make sure that people can disable animations around interactions: WCAG 2.3.3 Animation from interactions

Exceptions

Less than 5 seconds

The requirement to to be able to stop or hide video technically only applies to videos more than 5 seconds long. But as with so many of these exceptions, that’s a fairly arbitrary number. A video of 4 seconds is as likely to cause the same issues as one that’s 6 seconds..

Essential movement

There’s also an exception for anything considered essential. WCAG gives the examples of a ‘page loading’ animation. If someone is waiting for content to load, a moving icon helps to reassure people the page is still loading and hasn’t crashed. You should still make sure this kind of animation is as simple as possible.

Where it gets complicated

Accessible controls

Having a mechanism to pause, stop or hide video is great. But if those controls aren’t accessible to assistive tech, the mechanism doesn’t work.

All brains are different

The requirement for less than three flashes a second is a good baseline, but people can still have problems from fewer flashes. If your video technically has less than three flashes a second, it technically meets WCAG, but if it still flashes very quickly, it could still cause harm.

The aim is for accessible content, not content that just about passes WCAG..

Don’t rely on browser settings

People can change their browser settings to reduce animation effects. If you’re committed to having animation, you should definitely make sure your site will respond to these settings.

But there are lots of people with conditions triggered by animation who haven’t changed their browser settings. Maybe they don’t even know they can. It’s important not to put the burden of your site’s accessibility onto users. When it comes to animation effects, it’s easiest by far to just not have them.

Free tools

I don’t know of any tools that can tell you exactly how many flashes per second a video is producing. If you do, please let me know!

Get in touch

If you have feedback on this post, or want advice about anything to do with accessible and inclusive content, you can get in touch via email.