Animation from interactions

Silktide prompts you to verify that motion animation triggered by user interaction - scrolling parallax, hover transforms, click transitions - can be turned off, unless the motion is essential. This is success criterion 2.3.3 (level AAA).

This is a : deciding whether motion is essential, whether a toggle exists, and whether prefers-reduced-motion is wired correctly all need a person interacting with the page. Silktide raises the prompt on each page and a person confirms it.

Why this matters

Motion triggered by scrolling, hovering, or clicking can trigger vestibular disorders - dizziness, nausea, migraines - in people who are sensitive to it. Operating systems expose a "reduce motion" preference for exactly this reason. Sites that ignore it force those users to either endure the motion or abandon the page.

This is different from Pause, stop, hide (2.2.2), which covers animation the page starts on its own. 2.3.3 covers animation the user triggers.

What to check

Interact with the page: scroll, hover, focus, click. Note any motion that moves content in space (parallax, slide-ins, bouncing, page-flip transitions). Simple opacity fades do not count.
Enable the operating system's reduce-motion setting (or emulate prefers-reduced-motion: reduce in browser DevTools) and repeat. Non-essential motion should stop.
If the site does not respect the OS preference, look for an in-page control that disables non-essential animation. Confirm it works and does not hide content.
Motion that is essential to the function (a loading spinner, a progress bar, an animation authoring preview) is exempt - record that judgment when you approve.

How to fix it

Prefer respecting prefers-reduced-motion in CSS and JavaScript (WCAG techniques C39 and SCR40).
Or provide a site-wide control that turns off non-essential interaction-triggered motion.
Avoid parallax and large spatial transitions when a simpler effect would do.

If the page has no interaction-triggered motion, or every such motion can be disabled (or is essential), the finding.

How Silktide tests this

Silktide cannot observe motion over time from a static crawl, so this check raises one review prompt per page describing what to verify. No mainstream tool automates 2.3.3 - there is no W3C ACT rule for it, and neither axe nor Siteimprove ships a check for it.