TL;DR I ran a static motion-accessibility scan on 196 AI-generated production apps. 66.3% ship at...
TL;DR
I ran a static motion-accessibility scan on 196 AI-generated production apps.
66.3% ship at least one infinite animation with no way to pause it → fails WCAG 2.2.2 (Pause, Stop, Hide), Level A.
96.9% ship motion with no prefers-reduced-motion guard (a best-practice gap, not a strict A/AA fail). Only 3.1% were clean.
The fix for most of it is a media query and a pause control. Data + method + open dataset at the bottom.
We added reveals to our accessibility SaaS landing. They used opacity. Under prefers-reduced-motion, the opacity stayed at zero —…
This button passes every automated accessibility scan we've thrown at it: <button...
Animations are a common accessibility problem. For users with vestibular disorders, epilepsy, or...
The setup: I thought I was "pretty good" at a11y I shipped a client site earlier this year that I...
There's a particular kind of false confidence that comes from a green accessibility report. The CI...
The accessibility fundamentals that cover most real-world needs — semantic HTML, keyboard nav, contrast, and ARIA — without the…
