We’ve all been there. We want to be inclusive, but somewhere in the effort to make sure no one is left out, we lose sight of what’s truly important. It’s a slippery slope, and it’s easy to lose your footing.
As a designer who doesn’t personally rely on assistive technology, I often feel the urge to over-explain or overcompensate when it comes to accessibility. We add alt text—sometimes turning a simple image into an exhaustive description. We provide data down to the last decimal, even when the bigger story is the upward trend. We explain graphics that don’t need explaining, simply because we feel like we should.
The intentions are good. But the outcome can be anything but accessible. Instead of helping people find what matters, we bury the lead beneath information they never needed in the first place.
MORE ISN’T NECESSARILY MORE ACCESSIBLE
When we consider that more than one in four U.S. adults has a disability, making design accessible is far from a niche consideration. In a recent WebAIM Screen Reader User Survey, 89.9% of respondents said they use a screen reader because of a disability. That’s not a small audience.
For users navigating content with assistive technology, too much information can also create an accessibility problem. We tend to think of accessibility as making sure no one misses anything. But what if the goal isn’t to give users more information, but the information that matters?
That distinction is important. An accessible experience isn’t necessarily the one that contains the most information. It’s the one that makes the right information easier to find, understand, and use.
ALT TEXT ISN’T A DESCRIPTION CONTEST
Alt text is one of the easiest places to fall into the trap of thinking that more is better. Consider a photo of a group of students sitting around a table. Do we need to describe the color of their clothing, the number of chairs in the room, the laptop on the table, or the expression on every person’s face? Probably not.
If the image reinforces the narrative, something like “Students at the summer reading event” may be enough. The goal isn’t to recreate the image in words. It’s to communicate what the image contributes to the story.
Sometimes the most accessible choice is to say nothing at all. If an image is purely decorative or repeats information already provided in the surrounding text, the World Wide Web Consortium recommends a null alt text so assistive technology can skip it. Adding a description simply because there is an image creates more noise for someone navigating the page.
The same principle applies to charts and graphs. Resisting the urge to list every data point can feel counterintuitive, even like you’re sacrificing transparency. But when those numbers are read one after another, the larger story quickly disappears. Somewhere between the fourth and fifth line, the audience may lose the ability to understand why the data matters.
Instead, start with the point you want the reader to understand. If the story is an upward trend, say so. If there’s a significant peak or dip, call attention to it. When more detail is necessary, provide it as additional context rather than making someone work through every number before they can understand the point.
Accessibility isn’t transcription. It’s communication.
WHEN ACCESSIBILITY GETS HIJACKED BY MACHINES
There’s another layer to this problem that I think we need to talk about: What happens when the things we create for accessibility become another place to optimize for machines?
As creators, we’re being asked to make our content increasingly discoverable—not just by search engines, but by artificial intelligence tools that crawl, interpret, summarize, and surface information for users. In that rush to make content machine-readable, accessibility elements can become an easy place to stuff in more information.
Alt text is a good example. Yes, search engines use alt text to understand images. But that doesn’t mean it should become a pile on keywords, or be written for a search algorithm instead of the end user. Google even explicitly warns against keyword stuffing in alt text.
The same thinking can creep into headings, captions, metadata, transcripts, and other supporting content. We start asking, “What else can we include that might help this get found?” instead of asking, “What does this person actually need to understand?”
The person using assistive technology is not a search engine. They are a person trying to understand something.
EDITING IS AN ACCESSIBILITY SKILL
Accessibility should be human focused first. And the best way to know whether something is accessible is to test it—not just against a checklist, but through the experience of using it.
Use a screen reader. Navigate the document by its headings. Listen to the alt text. Pay attention to where the experience starts to feel repetitive, confusing, or disconnected from the main point. And whenever possible, test with people who use assistive technology in real life. They will notice things creators won’t.
But there’s another test we should apply first: Ask, “Is this information necessary?” It asks us to think about accessibility not only as what we add, but also as what we remove.
If something feels repetitive or overwhelming, ask whether it belongs in the experience at all. If not, remove it.
If it’s important, find the clearest way to communicate it. Write descriptions focused on what matters. Don’t describe decorative elements simply because they exist. Don’t turn alt text into a keyword list. Don’t make someone navigate every data point when the story is the trend.
We often think of accessibility as something we add: alt text, captions, transcripts, tags, descriptions, data tables. But accessibility also requires deciding what not to include. Because sometimes the most accessible thing we can give someone isn’t more information. It’s a clearer path to the information that matters.
Rochelle Ratkaj Moser is owner and chief creative officer of Ratkaj Designs.