The Most Common Disability Is the One We Design For Least
I'll admit something. For most of my career, when someone said "accessibility," my brain went straight to two things: contrast ratios and alt text. Screen readers. Maybe keyboard navigation if I was being thorough. I built a whole accessibility widget for EqualWeb and still mostly thought in those terms.
Then I looked at the actual numbers, and they embarrassed me a little.
The short version: Cognitive accessibility means designing so people can understand, remember, and finish what they came to do without straining their attention or memory. It serves the single most common disability type, 13.9% of US adults, plus everyone who is tired, stressed, or distracted. It's less about contrast and screen readers, more about clarity, simpler flows, and not making people think harder than they have to.
What is cognitive accessibility?
Cognitive accessibility is designing for how people think, not just how they see, hear, or move. It covers attention, memory, language, and problem-solving, the mental work your interface quietly demands. A product is cognitively accessible when someone can understand what's happening, remember what they were doing, and complete the task without it turning into a puzzle.
That includes people with ADHD, dyslexia, autism, learning disabilities, brain injuries, and age-related decline. It also includes the version of you that is running on four hours of sleep with a toddler yelling in the background. Cognitive load is not a niche condition. It's the water we all swim in.
Why is the most common disability the one we ignore?
Because the other kinds are easier to see, measure, and check off. Contrast has a number. Alt text is either there or it isn't. A screen reader either announces the button or it doesn't. Cognitive accessibility has none of that tidy pass-fail comfort, so it quietly falls off the sprint.
Here's the number that reframed it for me. According to the CDC, more than 1 in 4 US adults live with a disability, and cognition is the most common type at 13.9%, ahead of mobility (12.2%), hearing (6.2%), and vision (5.5%). Read that again. The disability the most people have is the one most design teams spend the least time on. We pour hours into a contrast audit for 5.5% and ship a checkout flow that a stressed, distracted human, which is to say most humans, can't get through.
It's not that contrast and screen readers don't matter. They matter a lot. It's that we mistook a slice of accessibility for the whole thing.
Who does cognitive accessibility actually help?
Everyone, which is exactly why it's worth doing. This is the curb-cut effect: the ramp built for wheelchairs is the thing every parent with a stroller and every traveler with a suitcase uses without thinking. Designing for the person with the least mental bandwidth produces a product that feels easier for the person with the most.
I felt this most sharply designing WeSend, a crypto wallet for migrant families sending money across borders. These were people making high-stakes financial decisions, often on a borrowed phone, often anxious, often not fluent in the app's language. Every extra step, every unexplained term, every screen that asked them to remember something from three screens ago was a real risk of a real family losing real money. Cognitive load wasn't an accessibility checkbox there. It was the whole design problem.
That's the reframe. Cognitive accessibility overlaps almost completely with what we already claim to value: clarity, simplicity, low friction. We just stop practicing it the moment a deadline gets tight.
What does designing for cognitive accessibility look like?
It's mostly a set of habits, not a toolkit. Here's where I start:
Cut the memory tax. Don't make people hold information in their head across steps. Show the shipping address on the payment screen. Let them see what they typed. This is the same instinct behind good behavioral design: reduce the mental work, and behavior follows.
Write for a tired human, not a lawyer. Short sentences. Plain words. One idea per line. If a sentence needs a second read, rewrite it.
Make one obvious next step. Ambiguity is cognitive load. When everything is emphasized, nothing is, so give each screen a clear primary action and let the rest recede.
Be consistent so people don't relearn. Same thing, same place, same name, every time. Novelty is fun in a portfolio and exhausting in a tax form.
Explain errors like a helpful person would. "That didn't work" is cruel. "Your card expired, try another" lets someone act without decoding.
Give feedback for every action. Uncertainty is its own load. A small, well-timed confirmation, the kind I wrote about in the art of microinteractions, tells the brain it can stop worrying and move on.
None of this shows up in a contrast checker. All of it decides whether a real person finishes or bails.
Cognitive-friendly vs cognitive-hostile: the same screen, two ways
Pattern | Cognitive-hostile | Cognitive-friendly |
|---|---|---|
Forms | Re-enter data you already gave | Auto-fill and show past entries |
Language | "Authentication credentials invalid" | "Wrong password, try again" |
Steps | 9 fields, no progress shown | Chunked steps with clear progress |
Login | Remember a complex password | Passkey, email link, or biometrics |
Emphasis | Six buttons, all equal weight | One clear primary action |
Help | Buried somewhere different each page | Same spot, every page |
Does WCAG actually cover cognitive accessibility?
It's starting to, and later than you'd hope. WCAG 2.2, published in October 2023, added several criteria aimed squarely at cognitive load. Accessible Authentication says logins shouldn't force a memory test like recalling a password, unless there's an alternative. Redundant Entry says stop making people re-type what they already entered. Consistent Help says keep support in the same place across pages. None of these are about vision or motor ability. They're about not overtaxing a mind.
The fact that these are new, and that some sit at higher conformance levels, tells you how long the standard treated cognition as an afterthought. The guidelines are catching up to where the users always were.
Key takeaways
Cognition is the most common disability type among US adults (13.9%, per the CDC), and the one design teams spend the least time on.
Cognitive accessibility is about attention, memory, and understanding, not contrast and screen readers.
It helps everyone, because tired, stressed, distracted people use interfaces the same way people with cognitive disabilities do.
The practices are things we already value: plain language, fewer steps, no memory tax, clear feedback, consistency.
WCAG 2.2 finally added cognitive-focused criteria (Accessible Authentication, Redundant Entry, Consistent Help), a sign the standard was behind, not ahead.
We treat accessibility like a compliance layer we bolt on for a small group of other people. But the most common disability is a mind under load, and every one of us is one bad day away from being that user. Design for the tired brain, and you have designed for all of them. So here's my question for your next review: whose attention are you spending, and did you ever ask permission?
Share on
