Verified motion for AI‑generated web apps.

We scanned 196 AI‑generated production apps for motion accessibility. Most shipped motion you can’t turn off.

We build a tool that fixes this, so we published the method and the raw data — check our work. Read the study & open dataset →

New companion study — the same scan on 50 real WordPress sites: The State of Motion Accessibility on WordPress →

The stakes are rising: the EAA is in force, the first enforcement order landed in June 2026, and the 2026 WebAIM Million reported the first year‑over‑year rise in detected errors in seven years.

Which of these is you?

MotionSpec serves four kinds of teams — developers, agencies, AI platforms, and EAA‑exposed enterprises — with the same verified‑motion engine.

What exactly would we catch on your site?

The free motion check is a static scan of any URL’s linked CSS and <style> blocks against WCAG 2.2.2 (Pause, Stop, Hide) and WCAG 2.3.3 (Animation from Interactions), with a fix for every CSS‑motion issue it flags. It’s the same MIT engine MotionSpec runs — not a mock. Looking for a WCAG motion compliance checker? This static scan checks two motion criteria — WCAG 2.2.2 and 2.3.3 — and shows the fix, not a full‑compliance verdict.

Static scan of linked CSS + <style> only. Not a full accessibility audit, not a compliance verdict; runtime JS/GSAP motion isn’t covered. Nothing is stored. Findings are grouped by root cause; the score (v2) weighs distinct causes — log‑dampened by occurrences — not the raw finding count.

Prefer a direct link to share? motionspec.dev/motion-check

Need evidence? €29 motion report — your percentile vs 196 audited AI‑built sites.

Want to watch the fix land — and try the engine yourself?

Two live demos: what a reduced‑motion fix actually does for a real visitor, and the open validator that keeps generated motion inside the rules.

Animation your users won’t fight — and you won’t maintain.

Every animation comes from a reviewed, device‑verified catalog and ships accessible‑by‑default and on‑budget — consistently, every time.

How does MotionSpec verify motion?

Three steps, each one checkable today — the same flow the demos and the docs walk through.

Try it yourself: validate a spec in the playground · run the free motion check · connect the MCP.

Why catch motion before it ships instead of flagging it in a report later?

Most tools check motion after it exists — scanners and audits, sampled and advisory. MotionSpec won’t emit motion that skips its reduced‑motion fallback or blows its performance budget in the first place. The core is MIT and public on npm, so there’s no lock‑in and full diligence access from day one — you pay us to operate it, verify it, and keep it current with the standards, and that operated, continuously‑verified layer is the part that compounds.

Where do the usual suspects fit?

What’s proven so far — and what can you inspect today?

One live pilot so far — commercial terms in progress — plus a core anyone can verify in five minutes. We’re precise about what’s measured versus asserted.

First pilot deployment — CHS Computer, Germany. Lighthouse, median of 5 runs, desktop, one client site — not a guarantee; raw reports available on request. CLS improved but is not yet in the green band — we don’t advertise “all Core Web Vitals green.”

What do you actually get — measurably?

MotionSpec turns “is our motion OK?” into three numbers you can check.

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.

What does it cost to go further?

MotionSpec has one free tool and a short ladder of paid options — you never pay for the MIT core.

See full pricing →

How does the design‑partner program work?

A three‑step path, deliberately small so each partner gets real engineering attention. Terms are set per partner on a call; platform pricing isn’t public — see how the three tiers work.

You could build this in‑house — so why license it?

The pattern is MIT and public — cloning the basics is a few weeks. What you’d actually sign up for is the forever part: every new motion class hand‑built, tested, and accessibility‑verified, in a layer that never differentiates your product. Our estimate: roughly 0.5–1 senior engineer for 3–6 months to reach parity, plus permanent maintenance. A license is a fraction of that, stays neutral across your stack, and grows with the MCP ecosystem instead of your release train.

MotionSpec is built by Kevin Fröba (Fröba Sales Solutions UG, Germany), with dedicated security engineering. We’re deliberately small and honest about it: the MIT core means you’re never locked in, and a maintainer runbook plus a source‑escrow option cover continuity.

Frequently asked questions.

What we will and won’t claim.

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. Need a full accessibility audit? Hire a specialist — we’ll happily coexist with their findings.