From Good Intentions to Inclusive Design: Solving the Accessibility Puzzle

Accessibility is often hailed as the most critical aspect of web design, yet many websites remain difficult or impossible for some users to navigate. This isn't due to malice—designers genuinely care about inclusivity. So why do exclusionary designs persist? The answer lies not in lack of empathy but in information overload. Designers are expected to remember countless guidelines across usability, accessibility, aesthetics, and more. This article proposes a practical shift: instead of relying on designers' memory, make accessibility issues recognizable during the design process. Inspired by Jakob Nielsen's heuristic Recognition rather than Recall, we explore how to surface accessibility knowledge at the moment it's needed. Below, we answer key questions about this approach.

Why is accessibility more than just a nice-to-have for websites?

Accessibility is often treated as an optional extra, but in reality it is a fundamental requirement that can have direct consequences on people's lives. As Aral Balkan argues in his essay This Is All There Is, almost every designed artifact can influence life events and death events. A simple bus timetable app, for instance, might seem trivial, but if it's poorly designed, someone could miss a daughter's fifth birthday party or be unable to say a final goodbye to a dying grandmother. These are not hypotheticals; they are real stakes. When we design websites, we are not just creating digital interfaces—we are shaping access to services, information, and connections that matter deeply. Ignoring accessibility means actively excluding people from these critical moments. Therefore, making websites accessible is not a checkbox; it is a moral and practical necessity that directly affects human experiences.

How can a poorly designed bus timetable affect life and death?

The connection between a bus schedule and life-or-death events may seem far-fetched until you consider real-world scenarios. A complicated or unclear timetable can cause a person to miss the bus, which might mean arriving too late to visit a sick relative in the hospital or missing a once-in-a-lifetime family gathering. Aral Balkan's essay highlights this exact point: even seemingly mundane designs can create barriers that have profound emotional and practical consequences. When designers fail to account for users with visual impairments, cognitive disabilities, or language barriers, they inadvertently block access to life's important moments. For example, if the text is too small or the layout confusing, someone might misread the departure time and miss the last visit with a loved one. This is why accessibility must be considered from the start—not as an afterthought but as an integral part of design that safeguards human connection and well-being.

If designers care, why do inaccessible designs still exist?

The disconnect between designers' intentions and the exclusionary outcomes of their work stems from a simple but frustrating reality: there is simply too much to remember. Designers are bombarded with advice from countless articles, guidelines, and best practices covering everything from typography to cognitive load. On top of that, they must recall specific accessibility standards like WCAG, color contrast ratios, screen reader compatibility, and more. As one insightful piece from A List Apart points out, designers are good people who never say, "I don't care if someone can't read this." Yet they still produce inaccessible designs because the sheer volume of knowledge required exceeds human memory capacity. The problem is not unwillingness but overload. When faced with a mountain of information, even the most empathetic designer can overlook critical accessibility details. The solution is not to shame designers but to change the process so that accessibility knowledge is easily accessible at the moment of decision-making.

What is Jakob Nielsen's Recognition rather than Recall heuristic?

Jakob Nielsen's 10 Usability Heuristics, developed in the mid-1990s, remain a cornerstone of user interface design. Heuristic number 6, Recognition rather than Recall, originally applies to users: it states that the information needed to use a design should be visible or easily retrievable when needed, rather than relying on the user's memory. For example, a well-designed website shows navigation options clearly instead of forcing users to remember where they are or what they can do next. This principle reduces cognitive load and makes interfaces easier to use. But we can extend this idea beyond the end user. What if we applied the same logic to the design process itself? Instead of requiring designers to recall every accessibility guideline from memory, we could make that information visible and available right at the moment they need it—during the design phase. That shift transforms the problem from one of recall to one of recognition, making it far easier for designers to catch and fix issues before they ever reach users.

How can we apply Recognition rather than Recall to help designers?

To apply this heuristic to designers, we need to change the environment in which they work. Rather than expecting designers to memorize a long list of accessibility dos and don'ts, we can embed accessibility cues directly into their tools and workflows. For instance, design software like Sketch or Figma could have built-in warnings when a color contrast ratio falls below WCAG standards. Checklists could be integrated into prototyping stages, and personas representing diverse abilities could be part of the template library. The goal is to make accessibility issues recognizable at the moment of creation, not something to check later. This mirrors what Nielsen proposed for users: show the information when it's needed. For designers, that means having visual indicators, automated scans, or even simple reminders within the interface they're building. By reducing the cognitive burden of recall, we empower designers to naturally create more inclusive experiences without an extra cram session before each project.

What practical steps can make accessibility issues more visible during design?

Implementing Recognition rather than Recall for designers involves concrete changes in tools, culture, and process. First, design tools should include real-time accessibility feedback: for example, color contrast analyzers that flag low contrast immediately, or text size warnings when fonts fall below recommended thresholds. Second, design systems can embed accessibility patterns—like requiring alternative text fields on every image component or offering pre-validated color palettes. Third, team workflows can incorporate quick accessibility reviews during design critiques, using simple heuristics such as "Can this be perceived by someone who cannot see?" or "Is this navigable by keyboard?" Reference materials like Sarah Horton and Whitney Quesenbery's A Web for Everyone provide excellent guidance, but the key is to surface that guidance at the right moment. By integrating these practices, we transform accessibility from a distant checklist into an immediate, visible part of the design conversation.