Bridging the Gap Between Intent and Impact: A Practical Accessibility Framework

Introduction

Accessibility is often viewed as a complex, technical add-on to web design, yet it remains the single most critical factor in creating truly inclusive digital experiences. While many resources offer innovative insights, this article focuses on actionable steps—something you can apply directly to your next project. The perspectives shared here are personal but grounded in years of observing where good intentions fall short.

Bridging the Gap Between Intent and Impact: A Practical Accessibility Framework

The Paradox of Good Designers and Exclusionary Outcomes

Let’s start with a premise most will agree on: designers are fundamentally good people. I’ve never encountered a designer who openly admits, “I don’t care if someone can’t read this text,” or “It’s not my fault if the interface confuses users.” Yet we all have witnessed examples of designs that inadvertently exclude people—text too small to read, physical devices uncomfortable to hold, or services so puzzling they leave users frustrated.

This isn’t about malice. It’s about the gap between intention and outcome. Designers care, but some designs still create barriers. Recognizing this paradox is the first step toward solving it.

Accessibility as a Life-or-Death Issue

One might ask: “Is accessibility truly a critical concern?” The answer is an emphatic yes. In the 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 could cause someone to miss their daughter’s fifth birthday party—a life event—or prevent them from saying goodbye to a dying grandmother—a death event.

When even a seemingly mundane application carries such weight, the stakes become clear. Accessibility isn’t a luxury; it’s a fundamental responsibility.

Why Do We Still Get It Wrong?

The frustrating question remains: if designers are good and the stakes are high, why do exclusionary designs persist? We already understand that not everyone sees, hears, thinks, or moves the same way. So what goes wrong?

In my view, the core problem is cognitive overload. Designers are expected to absorb a vast body of knowledge—typography, color theory, interaction design, and accessibility guidelines, plus dozens of other disciplines covered by resources like A List Apart. It’s simply too much to recall at once. As a result, even well-meaning designers overlook accessibility considerations.

A Heuristic for Designers: Recognition Over Recall

Jakob Nielsen’s 10 Usability Heuristics for User Interface Design, introduced in the mid-1990s, remain remarkably relevant. Among them, Heuristic №6 — “Recognition rather than Recall” — offers a powerful clue. Nielsen states: “Information required to use the design should be visible or easily retrievable when needed.”

Let’s repurpose this heuristic for designers themselves. Instead of applying it solely to users, we can say: Information required to produce the design should be visible or easily retrievable when needed. This reframing suggests that designers shouldn’t have to rely on memory to incorporate accessibility. Instead, the necessary guidance should be recognizable at the moment of decision.

Putting It into Practice

How can we operationalize this approach? One excellent resource is A Web for Everyone: Designing Accessible User Experiences by Sarah Horton and Whitney Quesenbery. This book provides practical frameworks that align with the recognition-over-recall principle. For example, it offers checklists and personas that make accessibility issues visible during design rounds.

Additionally, consider embedding accessibility tools directly into your workflow:

Use color contrast checkers as browser extensions.
Create design templates with built-in accessibility annotations.
Conduct quick heuristic evaluations focusing on recognition rather than recall.

By making these practices habitual, you reduce the burden on memory and move toward consistent inclusive design.

Conclusion

Good designers create bad websites not from lack of care, but from an overload of information. The solution isn’t to memorize every guideline—it’s to build systems that surface accessibility knowledge when and where it’s needed. By adopting a “recognition over recall” mindset, we can close the gap between intention and impact. Start with small, visible steps, and let accessibility become a natural part of your design process.

Tags: