The Disabilities You Can’t See: Why Cognitive Accessibility Matters

My IQ is 129, and I can still lose a word in the middle of a conversation. I know what I mean. I can see the idea, understand the connection, and have plenty to say about it, but the word I need refuses to show up. So I reach for “thingy,” or I describe red as “the opposite of blue.” I know that is not a literal definition of red. It is my attempt to get you somewhere near the word I cannot retrieve while the conversation keeps moving without me.

I share that score because people too often mistake difficulty communicating for difficulty understanding. I should not need a number to earn someone’s patience, and neither should anybody else. Nobody should have to prove their intelligence before being treated with respect. Yet a pause, an unusual description, or a request to hear something again can change the way another person looks at you. Suddenly, you are explaining yourself instead of being heard. Exhausting.

Understanding and expressing are different things

Cognition is the work involved in taking in information, paying attention, remembering, understanding language, making decisions, and planning what to do next. Communication involves getting meaning from one person to another. These abilities interact, but they do not move together in one neat line. Knowing something and retrieving the words to say it are different tasks; a fluent answer is not a complete measure of someone’s understanding, and a hesitant answer does not tell you what they are capable of.

My experience is my own, not a template for every cognitive disability. People have different strengths, difficulties, and ways of communicating. Some need more time, some need written instructions, and some need a process broken into manageable steps. We do not get to decide who deserves support by how intelligent they seem to us. Accessibility belongs to people across the full range of intellectual ability.

A website can make the work harder

Cognitive accessibility means designing information and interactions so people can understand what is happening, know what to do, and recover when something goes wrong. A website can load perfectly and still leave someone unable to finish a task. Unfamiliar language, disappearing instructions, a maze of pages, or a form that expects someone to remember everything they entered three screens ago can put the burden of a poor design on the person trying to use it.

Imagine completing a long application, reaching the next screen, and realizing you might have misunderstood an earlier question. There is no clear way back. No summary of your answers. No indication of whether returning will erase what you have done. Now you are trying to remember the question, remember your answer, and predict what the website will do if you touch the wrong button. That is a lot to demand from someone who came there to complete one necessary task.

When the system makes people feel invisible

An anonymized account shared with Common Ground Accessibility recalls frustrations with an older version of Michigan’s MI Bridges website, including crashes or failures without useful explanations. The person remembered uncertainty about whether information had been saved, whether an application had gone through, and what to do next. These are recollections, not independently verified findings about that website, and they should not be read as a description of the current system.

They also recalled hearing other people speculate that website barriers were intentional, designed to discourage applications and save government money. Those allegations are unverified. I doubt that was the designer’s intention. But on the other side of the website, when you’re looking for help and keep running into barriers, that’s how it can come across. Do you want your organization to come across that way?

What the recollection brings into focus is the distrust and humiliation a confusing process can leave behind. When someone cannot tell whether a failure belongs to the website or to something they did, they may begin questioning themselves, the institution, or both. Add difficulty with memory, language, attention, or processing, and an unexplained error can become much more than an inconvenience. We should care about that without demanding that someone disclose private details to make us listen.

Give people a path they can follow

Breaking a form into smaller pages can help, but dividing it is only the beginning. Make the route visible. Show a plain-language step trail such as “Your details → Your household → Review → Submit,” identify the current step in text, and show what is completed and what remains. A person returning after an interruption should be able to work out where they are without starting the whole process over in their head. W3C’s guidance on making each step clear describes this kind of orientation support.

Let people return to earlier answers, review them, and make corrections without losing later work. Before submission, provide a readable summary with clearly named edit links, such as “Edit household details,” and a predictable route back to the review page. Explain if changing an answer affects later questions. A Back button should not feel like a gamble.

Preserve progress when someone moves between steps or encounters an error. For longer tasks, offer a secure way to save and return, explain what is saved and for how long, and consider people using shared devices. Tell people before a session expires and give them a way to continue where possible. Saving should protect both their effort and their privacy; it should not require them to understand the technology behind it.

When something goes wrong, say what happened and what the person can do next. “Something went wrong” leaves all the work with the user. An error such as “Enter a date of birth using month, day, and year” gives a direction, provided that really is the problem. Keep valid answers, connect each message to its field, and provide an error summary with links to the affected questions. Do not rely on red alone. If the service itself is unavailable, say so honestly rather than implying the person entered a wrong answer.

Make room for different ways of thinking

Use familiar words, descriptive headings, visible labels, and examples placed beside the question they explain. Ask only for information you need, distinguish required questions from optional ones, and avoid making people repeatedly enter the same details. Keep help easy to find and offer another way to complete the task when someone needs it. W3C’s step-by-step instruction guidance and multi-page forms tutorial offer useful places to start.

Keep the experience usable with a keyboard, give focus a visible indicator, and make sure instructions and feedback reach people using screen readers. Leave room for larger text and smaller screens. Then invite people with different cognitive and communication needs to try the process, and listen when their experience does not match your assumptions. A technically functioning form is not the same as a form people can confidently use.

Dignity should be built in

I do not want patience to be a special favor granted after I explain my IQ or find a more acceptable way to struggle. I want us to stop treating speed, fluent speech, and effortless navigation as proof that someone belongs. People deserve time to find a word, room to correct an answer, and clear information about what happens next. Without having to plead for it.

Accessibility asks us to notice where our systems make people work unnecessarily hard and take responsibility for changing them. Sometimes that change is a better error message. Sometimes it is a way to go back without losing an hour of work. Sometimes it is believing that the person in front of you understands far more than they can say in that moment. Different needs. Equal dignity. That is the common ground we should be building.