Hero video autoplays without a visible pause control. Fails WCAG 2.2.2 for any user who cannot silence background motion.
<video autoplay muted playsinline controls>...</video>
Paste a URL. Motion Panel checks the four motion-specific WCAG criteria that Lighthouse, axe, and WAVE cannot: 2.2.2 Pause, 2.3.1 Flashes, 2.3.3 Animation from Interactions, plus reduced-motion honoring. Every finding cites the criterion.
Every figure below is footnoted with its source. Motion Panel does not ship uncited stats.
| Jurisdiction | Max fine |
|---|---|
| Hungary[1] | €1,260,000 |
| Spain[2] | €1,000,000 |
| Netherlands[3] | €900,000 |
| France[4] | €250,000 |
| Germany[5] | €100,000 |
| Italy[6] | 5% turnover |
Any auto-moving content that runs longer than 5 seconds needs a pause / stop / hide control.
Nothing on the page may flash more than three times per second at general or red-flash thresholds.
Motion triggered by scroll, hover, or click must be able to be disabled by the user.
Every animation should degrade gracefully when the OS motion setting is set to reduce.
Server-side fetch, cheerio parse, and a targeted analysis against the exact cues that cause motion violations in Framer, Webflow, and hand-rolled marketing sites.
Free tier shows the top three violations. Paid tier expands the same panel in place with every finding, a downloadable PDF, and a shareable bento dashboard.
Hero video autoplays without a visible pause control. Fails WCAG 2.2.2 for any user who cannot silence background motion.
<video autoplay muted playsinline controls>...</video>
Logo ticker uses animation-iteration-count: infinite and runs > 5s with no pause. Users cannot stop it.
.marquee-row.is-paused { animation-play-state: paused; }No @media (prefers-reduced-motion: reduce) block was found. Scroll-linked parallax fires even for opted-out users.
@media (prefers-reduced-motion: reduce) { * { animation-duration: 0.01ms !important; } }Yes. The audit fetches the rendered HTML and CSS server-side and looks for the specific motion cues that Framer, Webflow, GSAP, and framer-motion leave behind. If your site is a client-rendered SPA and the initial HTML is empty, paste the DOM snapshot into the fallback textarea and we audit that.
Open DevTools, right-click <html>, choose Copy > Copy outerHTML, and paste it into the 'Or paste HTML directly' field. The audit runs on the pasted markup exactly as if we had fetched it.
No. Motion Panel surfaces WCAG 2.2 findings and cites the success criteria and regulator context. When a finding could plausibly trigger an EAA fine or ADA lawsuit we raise an attorney-escalation flag. Talk to accessibility counsel before shipping in regulated markets.
axe and Lighthouse do not evaluate WCAG 2.3.3 because they cannot detect motion triggered by scroll or interaction, and they cannot simulate the prefers-reduced-motion state. Motion Panel focuses only on the four motion-specific criteria those tools skip.
Yes. Webflow interactions compile to inline transforms and animation properties that our parser picks up. We flag any interaction that fires without a reduce-motion guard.
The European Accessibility Act has been enforceable since June 28, 2025. Administrative fines range from €5,000 to over €1.26M depending on the member state. Every violation shows which EAA-aligned WCAG criterion it maps to, and the attorney flag fires on the high-risk ones.
Paste a public URL. We fetch the rendered HTML, extract every motion cue, and return WCAG-cited findings. If the target is a client-rendered SPA, use the paste-HTML fallback.