Defensible motion evidence — not a compliance promise.
Get defensible, WCAG‑2.2.2‑cited evidence that your product’s motion was checked and fixed — from a vendor that refuses to sell you a “compliance guarantee.”
MotionSpec gives you dated, WCAG‑2.2.2‑cited evidence that your UI motion was checked — it does not certify that your product is “EAA‑compliant.” The European Accessibility Act raised the baseline expectation for digital products in the EU; for motion, the machine‑checkable success criterion is WCAG 2.2.2 (Pause, Stop, Hide — Level A). Across 196 AI‑built apps we measured on 16 Jul 2026, 66.3% ran a loop you can’t pause and 96.9% shipped no reduced‑motion guard.
To be precise: MotionSpec verifies and compiles UI animation in AI‑generated web apps — it does not generate AI video.
What does the EAA actually change for your product’s motion?
The European Accessibility Act (EAA) has been in force since June 2025 and raises the expected accessibility baseline for digital products sold in the EU; for UI motion specifically, the machine‑checkable success criterion is WCAG 2.2.2 (Pause, Stop, Hide — Level A). It does not hand out a “motion certificate” you can buy — which is exactly where two exposures open up.
Unpausable motion is now a documented, common failure mode.
The stakes are rising: the EAA is in force, enforcement has begun, and the 2026 WebAIM Million reported rising detected errors across the web’s most‑visited pages. An infinite loop a user can’t pause is a WCAG 2.2.2 Level A failure — the kind an audit or a complaint can point straight at.
The vendor who sells you “compliant” is a second liability.
No tool can make your product EAA‑ or WCAG‑compliant, so a supplier who claims it is one more thing you’d have to walk back under scrutiny. For a due‑diligence file you need evidence you can defend — dated, scoped and cited — not a promise that inflates past what anyone actually measured.
What evidence do you actually get?
You get a dated, WCAG‑2.2.2 / 2.3.3‑cited record that your product’s motion was checked — and, where you act on the findings, fixed. It is an engineering evidence artifact for your due‑diligence file, not a legal compliance verdict. Three ways to obtain it, smallest first:
Motion Report — €29, one URL
A human‑verified audit of one URL: every finding cited to WCAG 2.2.2 (Pause, Stop, Hide — Level A) or 2.3.3 with a copy‑paste fix, your percentile versus the 196‑site benchmark, delivered as a dated PDF in ≤1 business day. Refundable within 14 days, no questions.
Dated evidence artifactProof Sprint — product or portfolio
We benchmark 50–100 pages across your product: motion validity rate, WCAG 2.2.2 / 2.3.3 and reduced‑motion findings, and the Core Web Vitals delta with vs. without MotionSpec. You keep the report either way. Fixed scope, priced up front.
Fixed scope · paidMonitor & signed certificates — ongoing
Motion Monitor re‑scans your domain weekly with a diff alert when a deploy regresses motion accessibility, and a Dev Key issues signed /certify conformance certificates for the motion we compile — verification by reproduction, not a stored claim.
Continuous evidenceStart with the free check — see every motion issue we can spot in your CSS, free — then commission the report when you need it human‑verified, dated and cited. Run the free motion check →
A detection check — we find and show the issues; we never promise to make your site compliant. How the check works →
How do we know this is a real, measurable problem?
For a due‑diligence file the base rate matters. Across 196 AI‑generated production apps we scanned on 16 Jul 2026, 66.3% ran a loop with no way to pause (WCAG 2.2.2 Pause, Stop, Hide — Level A) and 96.9% shipped motion with no reduced‑motion guard (WCAG 2.3.3 — a best‑practice gap, not an A/AA failure).
ran a loop with no way to pause (WCAG 2.2.2 Pause, Stop, Hide · Level A)
shipped motion with no reduced‑motion guard (WCAG 2.3.3 — a best‑practice gap, not an A/AA fail)
median distinct motion root causes per app
came back clean
We build the tool that fixes this, so we published the method and the raw data — check our work. Read the study & open dataset →
A static scan is a lower bound: it reads linked CSS and <style> blocks, not runtime JS/GSAP motion. We state the date, sample size and scope on every report, so the evidence is exactly as strong as what we measured — no more.
What do you actually get — measurably?
It’s three numbers your audit and your risk file can actually use.
problems on the typical site — see yours free, in ~10s
Paste any URL: a count of motion problems, each with a copy‑paste fix, and where you rank against the 196 real sites we measured. No signup — provable on your own site right now.
sites with no ‘reduce‑motion’ fallback → yours covered
96.9% of the sites we measured ship animation with no fallback for people who’ve set their device to ‘reduce motion.’ MotionSpec gives every animation that calm fallback — so you stop turning those visitors away.
lighter, faster pages (one measured pilot)
The heavy, always‑on motion we flag is the same stuff that makes pages stutter and drain battery — so clearing it is two‑for‑one: more accessible AND lighter. In our first real deployment, the main content appeared in ~1.0s instead of 1.8s and the performance score rose 71→90.
You don’t have to take our word for it — the method and raw data behind the first two numbers are published in full, so you can check them yourself. The speed figures are from one measured deployment, shown as an example — not a promise.
Why is a vendor that won’t say “compliant” the safer one?
MotionSpec verifies and compiles UI animation in AI‑generated web apps — it does not generate AI video. And no MotionSpec plan makes your site “EAA‑compliant”, “WCAG‑compliant”, or “guaranteed accessible” — no tool can promise that, and we won’t.
What we do: enforce a reduced‑motion fallback and a performance budget on the motion we compile, and verify two specific WCAG criteria (2.2.2 and 2.3.3) — stated with date and scope on every report. Runtime JS/GSAP motion is flagged as not audited. For a risk‑averse team that restraint is the point: we’d rather hand you evidence you can defend in an audit than a claim you’d have to retract in one.
Turn one URL into dated, citable evidence.
The smallest reversible first step is the €29 Motion Report — a dated, WCAG‑cited artifact for one URL, refundable within 14 days, no questions. Standardizing across a product or a portfolio? Talk to us about a Proof Sprint and ongoing evidence.
A detection check, not a compliance one — we find and show specific issues; we never promise to make you compliant.
Enterprise & EAA questions.
Does MotionSpec make us EAA-compliant?
No — and no tool can. MotionSpec gives you dated, WCAG‑2.2.2 / 2.3.3‑cited evidence that your product’s motion was checked and, where you act on it, fixed. That is an engineering evidence artifact for your due‑diligence file, not a legal compliance verdict. Overall EAA conformance depends on your whole product and your legal situation.
What evidence do we actually get?
A dated Motion Report: every motion finding on one URL cited to WCAG 2.2.2 (Pause, Stop, Hide — Level A) or WCAG 2.3.3, each with a copy‑paste fix, plus your percentile against 196 AI‑built sites, delivered as a PDF within one business day. Every report states its date, sample and scope, so the evidence is exactly as strong as what we measured — no more.
See the report: motionspec.dev/pricing
How does the EAA treat motion?
The European Accessibility Act raises the expected accessibility baseline for digital products in the EU, but it does not name individual techniques. For UI motion, the machine‑checkable success criterion is WCAG 2.2.2 (Pause, Stop, Hide — Level A); WCAG 2.3.3 (Animation from Interactions) is a best‑practice gap, not an A/AA failure. We verify those two criteria — we do not certify overall EAA compliance.
Can you monitor motion on an ongoing basis?
Yes. Motion Monitor re‑scans your domain weekly and sends diff alerts when a deploy regresses motion accessibility, and a Dev Key issues signed /certify conformance certificates for the motion we compile. It is verification by reproduction — a check anyone can re‑run — rather than a stored claim.
Plans: motionspec.dev/pricing
Get defensible motion evidence.
Paste your URL for the free check, or commission the €29 Motion Report for a dated, WCAG‑cited artifact — then decide from there. No signup for the free scan, nothing stored.
MotionSpec verifies and compiles UI animation in AI‑generated web apps — it does not generate AI video.
Fixing it in code? For developers → · Shipping client sites? For agencies → · Building a platform? For platforms →