From Good Intentions to Inclusive Design: A Practical Heuristic for Accessibility

Every designer wants to create experiences that everyone can use—yet many websites still leave people behind. How can well-meaning professionals consistently miss the mark? This Q&A explores the gap between good intentions and accessible outcomes, and introduces a novel approach based on recognition rather than recall to help designers spot accessibility issues during the creative process. Let’s dive into the problem and a workable solution.

Why do user-friendly designers sometimes create inaccessible websites?

Designers are inherently good people. I’ve never met a colleague who deliberately says, “I don’t care if someone can’t read this text” or “Who cares if this interface confuses users?” Yet, we’ve all seen designs—physical or digital—that exclude people. The root cause isn’t malice; it’s an overload of information. A designer must juggle aesthetics, usability, brand guidelines, technical constraints, and accessibility rules. With so many guidelines (from color contrast to screen-reader compatibility), it’s impossible to remember every detail in the heat of creation. Consequently, even the most empathetic designer can unintentionally produce a site that fails a user with low vision, hearing impairment, or cognitive differences. The solution lies not in demanding perfect memory, but in making accessibility cues visible during the design process itself.

From Good Intentions to Inclusive Design: A Practical Heuristic for Accessibility

Is web accessibility really a life-or-death issue?

Absolutely. In his influential essay “This Is All There Is,” Aral Balkan argues that nearly everything we design can influence life and death events. For example, a poorly designed bus timetable app might 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). While not every accessibility flaw has such dramatic consequences, the cumulative effect of exclusion can be devastating. Missed medical appointments, lost job opportunities, or social isolation are just a few real-world outcomes. Recognizing that small design failures can have outsized impact helps prioritize accessibility from the start. It’s not hyperbole—it’s a call to treat design as a matter of human dignity and safety.

What is the core problem that prevents designers from making accessible designs?

The central challenge is too much to recall. Designers are expected to absorb and apply a vast body of knowledge: UX heuristics, responsive layout techniques, performance optimization, branding, and—on top of everything—full accessibility guidelines (WCAG, ARIA, color contrast ratios, etc.). The human brain can only hold so much active information. When a designer is focused on visual appeal or meeting a tight deadline, accessibility concerns often slip through the cracks. This isn’t a character flaw; it’s a cognitive limitation. The proposal is to shift from demanding perfect recall to enabling recognition—making accessibility requirements visible and easily retrievable right when design decisions are made. By externalizing the checklist, we free mental space for creative problem-solving while ensuring no one is left out.

How can Jakob Nielsen’s usability heuristics help solve the accessibility overload?

Jakob Nielsen’s 10 Usability Heuristics, first published in the 1990s, offer a timeless framework. Heuristic #6, “Recognition rather than Recall,” originally applied to users: interface information should be visible or easily retrievable when needed. I propose we apply the same principle to designers. Instead of forcing designers to memorize every accessibility rule, we should make those rules visible and retrievable during the design process. For instance, a design tool could flag low-contrast text in real time, or a checklist could appear when a component is inserted. By turning recall into recognition, we reduce cognitive load and increase the likelihood that accessibility becomes an integrated part of the workflow—not an afterthought.

What does “recognition rather than recall” mean for the design process?

In practice, it means designing tools and environments that prompt designers at the moment of creation. For example:

Color contrast warnings in design software (like Figma plugins) that highlight insufficient ratios.
Component libraries that automatically include ARIA labels or focus indicators.
Checklists triggered by specific actions (e.g., “Did you add alt text to this image?”).
User personas with disabilities visible on the workspace, reminding the team of real needs.

The goal is to transform abstract guidelines into tangible, immediate feedback. This approach doesn’t replace learning—it supports it. Designers still need to understand why certain patterns matter, but the memory burden is lifted. Over time, these prompts become internalized, yet the safety net remains for complex scenarios.

How can designers practically implement this heuristic in their daily work?

Start by auditing your current tools and workflows. Ask: How many accessibility checks require manual memory? Each one is a failure point. Then:

Integrate automated checks into your design system (e.g., Stark plugin for contrast, axe for code).
Create a visible accessibility checklist on your design board (e.g., a sticky note with key items like “keyboard navigation” and “alt text”).
Use personas with disabilities as part of your design files—add notes like “Screen reader user” next to components.
Schedule regular “recognition breaks” where the team reviews designs against the heuristics without trying to recall everything.

The key is to externalize the knowledge. Sarah Horton and Whitney Quesenbery’s book A Web for Everyone offers a practical framework for building accessible user experiences. By making their principles visible at every stage, you turn accessibility from a burden into a natural design habit.

What resources can support this recognition-based approach to accessibility?

Several resources align with the “recognition rather than recall” philosophy. The WCAG Quick Reference is a searchable list of success criteria—but it’s still recall-heavy. Better options include:

A Web for Everyone (Horton & Quesenbery) – provides personas and integrated checklists.
Accessibility design kits from Microsoft or Figma community – include ready-made components with built-in accessible properties.
Automated testing tools like WAVE, axe DevTools, or Lighthouse – provide real-time feedback.
Heuristic review templates that combine Nielsen’s heuristics with accessibility criteria (e.g., “Is there a text equivalent for every image?”).

The goal is to create a library of prompts that sit next to your design tools, so you don’t have to recall them. Over time, this reduces errors and builds confidence that your final product works for everyone.

Tags: