Most teams treat accessibility as a checklist. Run the audit, fix the contrast ratios, add the aria labels, close the ticket. The site is now "accessible." Except it isn't — not really.
The Compliance Trap
WCAG 2.1 AA is the legal minimum in most jurisdictions. It covers perceivability, operability, understandability, and robustness. These are good principles. But they were written to be testable by automated tools, which means they describe the floor, not the ceiling.
A button with an aria-label passes WCAG. A button labeled "Click here" with an aria-label of "submit form" also passes. One of these is usable by a screen reader user; the other requires them to hold context in working memory that sighted users get visually for free.
Cognitive Load is Accessibility
The most underserved population in accessibility work is people with cognitive disabilities. WCAG has a section on it — Understanding Success Criterion 3.3 — but it's vague and hard to audit automatically.
Concretely: write shorter sentences. Use plain language. Break long forms into steps. Don't rely on color alone to convey state. Provide undo. These are not nice-to-haves for users with cognitive disabilities — they are blockers.
Motion and Vestibular Disorders
The prefers-reduced-motion media query has been supported in every major browser since 2019. Yet the majority of production sites ignore it.
@media (prefers-reduced-motion: reduce) {
* {
animation-duration: 0.01ms !important;
transition-duration: 0.01ms !important;
}
}
For users with vestibular disorders, parallax effects and entry animations are not aesthetic choices — they are barriers that cause physical symptoms.
The Right Mental Model
Accessibility is not a feature you add. It is a quality of the work itself. The same way you wouldn't ship a button that doesn't respond to keyboard input, you shouldn't ship motion that ignores user preferences or forms that fail under a screen reader.
Build it in from the start. It is always cheaper than retrofitting.