Accessible motion by default — at generation time.

Who owns it when a generated site ships inaccessible motion?

When your platform generates a site, the motion it emits is motion you shipped — and under the European Accessibility Act the accessibility exposure travels with the output, not with the prompt that asked for it. That makes motion accessibility a platform property, not a per‑user afterthought.

The scale is the uncomfortable part. We scanned 196 AI‑generated production apps for motion accessibility on 16 Jul 2026: 66.3% ran an infinite loop with no way to pause it — the real WCAG 2.2.2 Pause, Stop, Hide Level A failure — and 96.9% shipped animation with no prefers‑reduced‑motion guard (WCAG 2.3.3, a best‑practice gap we never call an A/AA failure). Only 3.1% came back clean, with a median of 17 distinct motion root causes per app. A prompt telling the model to “be accessible” does not move those numbers; enforcement does.

Two fears follow from that, and they’re the ones we hear from platform teams: becoming the named cause of a wave of inaccessible sites, and watching a rival ship “accessible motion by default” first. Both are answered the same way — make it a property of the generator, verifiable on demand.

What does “accessible motion by default” actually enforce?

MotionSpec compiles every animation from a reviewed catalog of 40 device‑verified primitives with a prefers‑reduced‑motion fallback and a performance budget enforced by default — a prompt alone can’t switch them off. The result is reduced‑motion‑safe by construction: the liability moves off your users and off your roadmap, and becomes a feature you can pass on.

Three ways to embed it, smallest commitment first:

Want to see it on a site your platform generated? The free motion check shows every CSS‑motion issue we can spot — free, no signup, nothing stored. motionspec.dev/motion-check

How bad is generated motion today — and who says so?

At platform scale the exposure compounds across every site you emit: we scanned 196 AI‑generated production apps for motion accessibility on 16 Jul 2026, and only 3.1% came back clean. We build the compiler that fixes this at generation time, so we published the method and the raw dataset — check our work.

Read the study & open dataset →

Honest scope: the compiler enforces a reduced‑motion fallback and a performance budget, and the checker verifies two specific WCAG criteria (2.2.2 and 2.3.3) — stated with date and scope. No MotionSpec plan makes a site “EAA‑compliant” or “WCAG‑compliant”; no tool can promise that, and we won’t. Runtime JS/GSAP motion is flagged as not audited.

What do you actually get — measurably?

For a platform it’s three numbers you can hold your output to.

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.

How does a platform partnership work?

MotionSpec runs a small design‑partner program for platforms that generate web UI at scale: motion that’s reduced‑motion‑safe and on‑budget by default, without your team owning a motion‑QA layer. It’s deliberately small so each partner gets real engineering attention; terms are set per partner on a call, and platform pricing isn’t public.

You could add prefers‑reduced‑motion yourselves — 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 across devices, 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 as the standards move. A license is a fraction of that, stays neutral across your stack, and grows with the MCP ecosystem instead of your release train — and because the core is MIT and public on npm, you’re never locked in, with a maintainer runbook and a source‑escrow option covering continuity.

Platform questions, answered.