Rule
Motion honours reduced-motion
Motion set off by scrolling, hovering or focusing should be switchable off.
- Rule
reduced-motion- WCAG 2.2
- 2.3.3 Animation from Interactions (opens in a new tab) (Level AAA)
- Severity
- Moderate
What it checks
One question per page, asked on the <html> element. It looks for motion that a reader's own action sets off: scroll-driven animations that move content, scroll-behavior: smooth on the root or the body, and rules for :hover, :focus, :focus-visible, :focus-within or :active that animate a transform, translate, rotation, scale, offset path or position.
Small movements are left out: a shift under 8 pixels, a scale within 15 percent, or a change that snaps into place with no transition. A page passes as soon as any stylesheet it can read mentions prefers-reduced-motion.
When a person decides
Such motion is sent for review, never failed, because the criterion excuses motion that is essential to the function or the information, and that is a judgement about the page. A stylesheet from another origin cannot be read, and the review says so when one might hold the media query.
Example
Sent to review
<style>
.card { transition: transform 0.4s; }
.card:hover { transform: translateY(-16px); }
</style>
<a class="card" href="/tours/">Garden tours</a>
Passes
<style>
@media (prefers-reduced-motion: no-preference) {
.card { transition: transform 0.4s; }
.card:hover { transform: translateY(-16px); }
}
</style>
<a class="card" href="/tours/">Garden tours</a>
The engine is tested against both examples.
How to fix it
Put the motion inside @media (prefers-reduced-motion: no-preference), or switch it off under @media (prefers-reduced-motion: reduce). Keep only motion that is essential to the function or the information.
Check your own pages
This rule runs in every pour audit: the browser extension, the bookmarklet, the command line and the editor. Get pour, free.