Bridging the Gap: How Design Heuristics Can Improve Accessibility

The Paradox of Good Designers and Exclusionary Websites

We often assume that skilled designers naturally create inclusive experiences. After all, no professional designer wakes up thinking, "I don't care if someone can't read this text" or "It's fine if navigation confuses people." Yet, across the web, we see websites and apps that inadvertently exclude users—those with visual impairments, cognitive differences, or motor challenges. This isn't due to malice; it's a deeper issue rooted in the complexity of modern design.

Acknowledging the Problem

Designers are, by and large, empathetic individuals. They strive to create products that serve everyone. However, good intentions don't always translate into accessible outcomes. We've all encountered sites where text is too small, contrast is poor, or interactions rely on precise mouse movements. The problem isn't a lack of caring—it's that designers are overwhelmed by the sheer volume of guidelines they must juggle.

The Consequences of Exclusion

Some might ask, "Is this really life-or-death?" The answer, as Aral Balkan argues in his essay This Is All There Is, is a resounding yes. Even a simple bus timetable app can have profound consequences. A poorly designed interface might cause someone to miss their daughter's fifth birthday party—or worse, prevent them from saying goodbye to a dying grandmother. Accessibility failures don't just frustrate; they alter life events.

Why Do Well-Meaning Designers Still Exclude Users?

It's frustrating because we already know the realities of human diversity: not everyone sees, hears, thinks, or moves in the same way. Yet, exclusion persists. The root cause isn't ignorance—it's cognitive overload. Designers are expected to keep track of UX best practices, visual design trends, coding standards, and a dozen other domains, all while remembering every accessibility guideline. That's too much to recall on the fly.

The Overwhelming Amount of Guidelines

Consider the breadth of topics covered by publications like A List Apart. Designers are told to remember guidance on typography, color theory, responsive layouts, interaction patterns, performance optimization, and so forth. On top of that, they need to memorize WCAG criteria, ARIA roles, and inclusive design principles. The human brain can only hold so much information without support. No wonder some guidelines slip through the cracks.

A Heuristic Approach to Accessibility

Jakob Nielsen's 10 Usability Heuristics for User Interface Design, from the mid-1990s, offer a timeless framework. While you might be younger than those heuristics, they remain relevant. One heuristic in particular stands out: #6 – Recognition rather than Recall. Nielsen stated that users should have relevant information visible or easily retrievable. But what if we apply that same principle to designers? Instead of forcing designers to recall every accessibility rule from memory, let's make the necessary information visible and retrievable while they work.

Adapting Nielsen's Recognition Principle for Designers

The idea is simple: embed accessibility cues directly into the design process. For example, a design tool could automatically flag low-contrast text or missing alt text. Checklists and pattern libraries can be integrated into daily workflows. By shifting from recall to recognition, we reduce cognitive burden and help designers catch issues early. As Sarah Horton and Whitney Quesenbery suggest in their book A Web for Everyone—Designing Accessible User Experiences, accessibility should be woven into the fabric of design practice, not treated as an afterthought.

Putting Theory into Practice

How can teams implement this? Start by creating a shared repository of common accessibility patterns that designers can reference. Use overlays or plugins that provide real-time feedback. Conduct regular heuristic evaluations focused on inclusive design. The goal is to make the right choice the easy choice—so that designers naturally build accessible experiences without having to consult a mental checklist every time.

For instance, when choosing a color palette, a recognition-based tool might display contrast ratios and warn if they fall below WCAG standards. When adding a clickable element, it could suggest a minimum target size for touch accessibility. These small nudges add up to significant improvements.

Conclusion

The problem of good designers creating bad websites is not a character flaw—it's a system flaw. We give designers too many rules to remember and too few aids to apply them. By adapting the heuristic of "recognition rather than recall" to the design process itself, we can empower professionals to create more inclusive web experiences without overwhelming their memory. It's time to stop treating accessibility as a separate discipline and start embedding it into the tools and workflows designers already use. After all, the best design is one that works for everyone.