Resources · 66

Animation: verify reduced motion, pause and understanding

Inventory motion, offer reduced behaviour and test that progress, state and navigation remain understandable without animation.

· 4 min

Empty digital forensics bench with storage devices and precision tools AI-generated editorial illustration

What this guide helps achieve

  • Inventory triggers
  • Define reduced behaviour
  • Separate WCAG criteria
  • Test all implementations

Quick check

  • Does reduced motion prohibit all animation?
  • Is criterion 2.3.3 level AA?
  • Is a global CSS rule sufficient?

Step-by-step method

  1. 01

    Inventory triggers

    List automatic, interaction-triggered and scroll-linked motion. Separate state information from decoration. Inspect JavaScript animations, video and embedded elements too.

    Deliverable: effects and purpose register.

  2. 02

    Define reduced behaviour

    prefers-reduced-motion signals a desire to reduce non-essential motion. Offer a static or quieter alternative while retaining information and controls. Avoid replacing large translations with another distracting effect.

    Deliverable: reduced behaviour per component.

  3. 03

    Separate WCAG criteria

    Interaction-animation criterion 2.3.3 is level AAA. Level A criterion 2.2.2 covers, among other cases, certain automatic movements lasting more than five seconds alongside other content, unless essential. Check the applicable criterion’s conditions.

    Deliverable: criteria and controls for each effect.

  4. 04

    Test all implementations

    Emulate preference before loading and during a session. Inspect styles, scripts and programmatic scrolling. If state depends on animation completion, ensure a reliable conclusion when animation is removed too.

    Deliverable: cold-load, live-change and final-state trials.

  5. 05

    Preserve information and controls

    Exercise reading, keyboard and error feedback in both modes. For affected automatic motion, test pause, stop or hide and stability during reading. Document exceptions rather than labelling every animation essential.

    Deliverable: evidence and limitations.

Four situations for testing the method

Fictional teaching cases. Each situation connects a signal, a check and a decision bounded by evidence; none represents a client outcome.

Fictional situationConcrete checkDecision and limit
Check a visual identity in actual use — A new palette looks coherent on a brand board, but links and error messages become difficult to distinguish.Compare component states in real themes: text, focus, error, selection and disabled controls. Test meaning without colour alone.Approve the palette with usage rules and readable states, rather than a logo or presentation page alone.
Preserve information when layout changes — On mobile, an animation shrinks a card and hides a button description while reading order remains unchanged.Disable non-essential effects and check the same information at narrow widths, with zoom and keyboard navigation.Make animation optional presentation; preserve content and controls in a usable order when the effect is absent.
A theme change must preserve component states — Dark mode changes the page background, but the focus indicator still uses a colour intended for the light theme.Test interactive states in each theme and during automatic switching. Include content added after loading.Fix the affected tokens and components; the presence of dark mode establishes neither adequate contrast nor accessibility.
Guide attention without requiring motion — A confirmation is communicated through an animated movement that some people prefer to reduce.Enable reduced-motion preferences and check that text or a static state still communicates the action result.Preserve information and control in the reduced variant. Provide suitable controls for persistent movement where needed.

Reusable worksheet

Complete with your authorised observations. These fields are a working template, not observed results.

FieldInformation to record
EffectTrigger, duration and information
AlternativeReduced version and final state
CriterionLevel, conditions and control
TrialPreference, keyboard, result and limit

Worked example

Illustrative situation

Fictional example: a panel becomes active only after its transition completes.

Decision and expected evidence

Reduced-mode acceptance reveals the wait; the component completes its state change without depending on animation duration.

Distinguish the mechanisms

MechanismPurposeCheck or limitation
Reduced-motion preferenceAdapt to system choicesCheck scripts too
Pause controlControl affected automatic motionMake it keyboard-operable
Static stateRetain information without motionDo not remove progress or error feedback

Management indicators

IndicatorWhat it measuresFirst action
Adapted effectsMotion with verified alternativesInclude embeds and scrolling
Preserved tasksJourneys completed in reduced modeInspect animation-dependent states
Working controlsPause or stop actually effectiveCheck resume and keyboard

Common pitfalls

  • Check scripts too
  • Make it keyboard-operable
  • Do not remove progress or error feedback

Frequently asked questions

Does reduced motion prohibit all animation?

No. It expresses a preference; choose a proportionate adaptation and retain necessary information.

Is criterion 2.3.3 level AA?

No, it is AAA. Other criteria may apply to automatic motion or flashing.

Is a global CSS rule sufficient?

It can reduce many effects but may not control scripts, videos or integrations. Test actual components.

Official references

References consulted: . The method and worksheet propose checks to adapt to your context; they do not constitute certification.