What is a11y — and what is it actually good for?
A11y is the numeronym for accessibility: the word starts with "a", ends with "y", and has eleven letters in between. It names the practice of building digital products that people with disabilities can perceive, understand, navigate and operate. The reference standard is the W3C's Web Content Accessibility Guidelines (WCAG), which turn that goal into concrete, testable success criteria.
Who a11y actually serves
The World Health Organization estimates that about 1.3 billion people — roughly 16% of the world's population — live with significant disability. But the audience is wider than the statistic, because impairment is not always permanent. It is useful to think in three rings:
- Permanent — a screen-reader user, a Deaf user, someone with a vestibular disorder or limited fine motor control.
- Temporary — a broken wrist, eye surgery, a migraine week, medication that heightens motion sensitivity.
- Situational — bright sunlight, one hand holding a child, a loud train, low battery saving mode.
Design for the first ring and the other two inherit the benefit. That is the well-documented "curb-cut effect": ramps were built for wheelchairs and ended up serving strollers, suitcases and delivery carts.
The advantages — beyond doing the right thing
- Reach. An inaccessible checkout simply loses the customers who cannot complete it — and their households. Accessibility is addressable market, not compliance overhead.
- Usability for everyone. Accessible pages are calmer, better structured, and more forgiving. The same clarity that helps a screen reader helps a hurried human.
- SEO and AI search. Semantic headings, real text, descriptive links and stable structure are exactly what search crawlers and AI answer engines parse. An accessible page and a machine-readable page are, to a large degree, the same page.
- Engineering quality. A11y defects cluster where testing is weakest. Teams that verify accessibility catch broken states, race conditions and dead ends earlier.
- Legal risk. Accessibility legislation exists and continues to tighten in many markets. We deliberately make no conformance claims here — what matters is that "we'll fix it later" gets more expensive every year.
The gap: motion is the least-covered layer of a11y
Most a11y advice covers contrast, alt text, keyboard navigation and forms — and stops there. Animation is where guidance thins out, even though WCAG is explicit about it:
- WCAG 2.2.2 — Pause, Stop, Hide (Level A): moving content that starts automatically and lasts longer than five seconds needs a way to pause, stop, or hide it.
- WCAG 2.3.1 — Three Flashes (Level A): nothing may flash more than three times per second.
- WCAG 2.3.3 — Animation from Interactions (Level AAA): motion triggered by interaction should be disableable, honoured on the web via
prefers-reduced-motion.
For people with vestibular disorders, unguarded animation is not a style preference — parallax, zooms and large sweeping movement can cause dizziness, nausea and migraines. Yet general-purpose checkers like axe or Lighthouse audit whole pages where motion is at most a small part, and visual-regression tools freeze animation to compare screenshots. The motion layer mostly ships unreviewed. That is why we wrote a dedicated, tool-independent verification guide — and why the free motion check scans exactly this layer of any URL.
The advantage no one else brings: a11y by construction
Everything above treats accessibility as something you check after building. That model breaks when AI platforms generate thousands of pages a week — audits cannot keep up with generation. The structural answer is to make the rules non-optional at the moment the UI is produced. That is the layer MotionSpec builds for animation: motion is assembled from a catalog of 40 verified primitives and compiled with the reduced-motion guard and a performance budget already in place. We call the result reduced-motion-safe by construction — deliberately never "guaranteed accessible", because motion is one layer of accessibility, not all of it. You can watch the difference this makes in the before/after demo: the same page with and without the guard, under a real reduce-motion setting.
FAQ
What does a11y stand for?
Accessibility. It is a numeronym — "a", eleven letters, "y" — like i18n for internationalization.
Is a11y only for blind users?
No. It spans visual, auditory, motor, cognitive and vestibular needs, and its benefits extend to temporary and situational limitations almost everyone has.
Does a11y help SEO and AI search?
Largely yes: the structure that assistive technology needs is the structure crawlers and answer engines read.
What is motion accessibility?
The animation layer of a11y: honouring prefers-reduced-motion, giving moving content a pause path, and avoiding flashes — WCAG 2.2.2, 2.3.1 and 2.3.3.
Paste any URL into the free motion check — a static scan against WCAG 2.2.2 and 2.3.3, every finding with its fix. No signup, nothing stored.
Run the free motion check