Your platform generates thousands of sites a week. Motion is the least reliable part.

LLM‑written animation code hallucinates APIs, ignores prefers‑reduced‑motion, and quietly degrades Core Web Vitals. Every page that ships “motion slop” is your brand on the line — and fixing it in‑house means building and maintaining a motion‑QA layer that isn’t your core business.

And the stakes keep rising: independent audits find accessibility failures on roughly 95% of the top million home pages, EU accessibility expectations keep tightening, and AI builders are multiplying how much web UI gets generated — so the weakest, least‑supervised layer is the one scaling fastest.

See exactly what we’d catch — on any URL.

Paste any site. We statically scan its CSS motion against WCAG 2.3.3 (reduced‑motion) and WCAG 2.2.2 (pause/stop) and show every finding with the fix. It’s the same engine we’d run across your platform’s output — not a mock.

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.

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.

Caught before it ships, not flagged 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.

First production deployment, and code you can 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; raw reports available on request. CLS improved but is not yet in the green band — we don’t advertise “all Core Web Vitals green.”

Co‑build the verified layer — then embed it.

A three‑step path, deliberately small so each partner gets real engineering attention. Terms are set per partner on a call; we don’t publish pricing.

You could. The ongoing part is the catch.

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.