Bridging the Gap: Making Accessibility a Design Habit

Accessibility isn't just a checkbox on a design list—it's the foundation of inclusive web experiences. Yet even well-meaning designers sometimes create sites that exclude people. This Q&A explores why that happens, the real-world stakes, and a practical approach to weaving accessibility into your daily workflow. Drawing from industry insights and classic usability principles, we'll uncover a simple shift that can turn good intentions into great, accessible designs.

1. Why is web accessibility considered a life-or-death issue?

Accessibility might sound like a nicety, but it can have profound real-world consequences. In his influential essay This Is All There Is, Aral Balkan argues that nearly every design decision can affect life events and even death events. For example, a poorly designed bus timetable app might cause someone to miss their daughter's fifth birthday party—a missed life event. More tragically, it could prevent someone from saying a final goodbye to a dying grandmother—a missed death event. These aren't hypotheticals; they're the direct results of inaccessible design. When we overlook accessibility, we're not just inconveniencing users—we're potentially barring them from moments that matter most. Recognizing this stakes the urgency of making accessibility a core part of design, not an afterthought.

2. If designers are good people, why do they still create inaccessible designs?

No designer consciously decides to exclude people. You won't hear a designer say, "I don't care if someone can't read this text" or "Who cares if this is confusing?" Yet inaccessible designs persist. The root cause isn't malice—it's cognitive overload. Designers are expected to juggle an enormous amount of guidance: UX principles, visual trends, coding standards, business goals, and a growing list of accessibility guidelines. With so much information to recall, it's no surprise that accessibility often gets overlooked. As one expert put it, "There’s too much to recall." The problem isn't a lack of goodwill, but a system that makes it hard for designers to remember and apply accessibility principles consistently during their work.

3. What is the main obstacle preventing designers from making websites accessible?

The primary obstacle is the overwhelming cognitive load placed on designers. They must remember not only design fundamentals but also specific accessibility rules for vision, hearing, cognition, and motor skills. For instance, they need to account for users who don't see perfectly, don't hear perfectly, don't think the same way, or don't move the same way. That's a lot of variation to keep top-of-mind. Additionally, the wealth of articles, guidelines, and best practices—like those from A List Apart—adds to the mental burden. While the information is valuable, trying to recall it all during the design process is impractical. This overload leads to unintentional exclusion. The solution isn't more information, but better ways to surface that information when it's needed most.

4. How can Jakob Nielsen's usability heuristics help solve accessibility issues?

Jakob Nielsen's 10 Usability Heuristics, dating from the mid-1990s, remain a powerful tool. Heuristic №6, Recognition rather than Recall, originally meant that users shouldn't have to remember information—it should be visible or easily retrievable. But we can flip this principle to help designers themselves. Instead of expecting designers to recall all accessibility guidelines from memory, we can make that guidance visible and easily accessible during the design process. For example, a design tool might show cues about color contrast when picking colors, or remind about alt text when adding images. By turning recall into recognition, designers can spot and fix issues in real time, making accessibility a natural part of the creative workflow rather than a post-hoc check.

5. What specific proposal does the original article suggest for designers?

The article proposes adapting Nielsen's heuristic to the designer's perspective: make the information required to produce an accessible design visible or easily retrievable when needed. In other words, design tools and checklists should surface accessibility information at the moment of decision. For instance, a wireframing tool could highlight insufficient color contrast as you choose colors, or a content management system could prompt for descriptive alt text when an image is added. The goal is to reduce the mental effort of remembering every guideline and instead rely on environmental cues. This shift from recall to recognition not only makes design more efficient but also ensures that accessibility is integrated from the start. The idea is backed by resources like the book A Web for Everyone by Sarah Horton and Whitney Quesenbery.

6. What resources can help designers make accessibility a habit?

A highly recommended resource is the book A Web for Everyone by Sarah Horton and Whitney Quesenbery. It provides practical guidance on designing accessible user experiences, covering everything from perception to comprehension. Beyond books, designers can benefit from automated tools that check accessibility in real time (like Stark or Axe), pattern libraries with built-in accessible components, and community guidelines such as the WCAG. The key is to integrate these resources into the design environment so that they become part of the habit, not an extra step. By making accessibility information as easy to access as a style guide, we can transform good intentions into consistently inclusive designs.

7. How can designers apply the "recognition rather than recall" principle to their own work?

To apply this principle, designers should embed accessibility cues directly into their tools and workflows. For example, use browser extensions that visually flag low-contrast text, or design systems that include accessible color palettes and typography scales. During user testing, include people with disabilities to get real-time feedback. Checklists can be integrated into project management tools so they appear at each stage. The idea is to reduce the need to remember separate rules and instead make the right choices obvious. When a designer is choosing a font size, the tool might show the minimum size for readability. This proactive approach not only improves accessibility but also saves time and frustration. Ultimately, it shifts the burden from memory to environment, making inclusion automatic.