How to Embed Accessibility in Your Design Process Using Recognition Over Recall

Introduction

Accessibility is not an afterthought—it’s the foundation of great design. Yet even well-meaning designers unintentionally create barriers for people with disabilities. The problem isn’t malice; it’s that we’re expected to remember an overwhelming amount of guidelines, from visual contrast to keyboard navigation, on top of every other design principle. This guide tackles that problem head-on. Drawing from the concept of recognition rather than recall (Nielsen’s heuristic #6), you’ll learn a practical, step-by-step method to spot and fix accessibility issues while you design, without having to memorize every rule.

What You Need

• Basic experience with user interface design (wireframing, prototyping)
• A willingness to challenge your own assumptions
• Reference material such as Sarah Horton and Whitney Quesenbery’s book A Web for Everyone or the WCAG guidelines
• A design tool (Figma, Sketch, Adobe XD, or even pen and paper)
• Optional: a checklist or accessibility overlay you can keep visible while working

Step-by-Step Guide

1. Step 1: Accept That Exclusion Happens—and That It’s Usually Unintentional

   No designer wakes up wanting to exclude people. But reality shows that many sites fail: text too small, poor contrast, confusing navigation. Start by acknowledging that your own designs may have blind spots. This honesty is the first step toward change. List three examples you’ve seen where a design made something hard to use (e.g., a light grey font on white). Keep this list nearby as motivation.

2. Step 2: Remember the Real Stakes—Life and Death Events

   In his essay “This Is All There Is,” Aral Balkan reminds us that even a bus timetable app can affect life events (missing a daughter’s birthday) or death events (missing a final goodbye). When you design, hold that weight: someone might rely on your interface for critical decisions. Write a sticky note: “This design affects real people.” Place it on your monitor.

3. Step 3: Identify the “Too Much to Recall” Problem

   You already know: not everyone sees, hears, thinks, or moves the same way. But with hundreds of guidelines from WCAG, ARIA, and usability heuristics, it’s impossible to keep everything in your head. Instead of trying to memorize, commit to making accessibility information visible during your design process. This shifts the burden from recall to recognition.

4. Step 4: Adapt Nielsen’s Heuristic #6 for Designers

   Jakob Nielsen’s heuristic “Recognition rather than Recall” originally applies to users. Modify it for yourself: The information required to produce the design should be visible or easily retrievable when needed. Practically, this means creating a visual checklist, a physical poster, or a digital overlay that you can glance at while you work. For example, paste a short list of common accessibility checks (color contrast, alt text, keyboard focus) beside your design canvas.

5. Step 5: Create a “Recognition Kit” for Your Design Tool

   Build a small set of reminders specific to your project. For instance:

   • Color contrast: Use a tool like Stark in Figma to flag low contrast in real time.
   • Focus indicators: Ensure every interactive element has a visible focus ring.
   • Text size: Test with browser zoom at 200% and note any cut‑off content.
   • Alternative text: Write alt text for images as you place them (not later).
   Bookmark the WCAG Quick Reference and keep it open.

6. Step 6: Review Your Work Using a Heuristic Walkthrough

   At the end of each design phase (e.g., wireframe, prototype), run a quick accessibility audit. Use your recognition kit and ask:

   • Can a screen reader user navigate this content in logical order?
   • Are all non‑text elements described?
   • Can someone with low vision increase text size without breaking the layout?
   • Is there any flashing or motion that could trigger seizures?
   Mark issues and fix them before moving to the next stage.

7. Step 7: Iterate and Test with Real Users

   No amount of checklists replaces feedback from people with disabilities. Recruit 2–3 testers who use assistive technology (screen readers, speech input, magnification). Ask them to complete key tasks while you observe. Note where they struggle—that’s your design’s blind spot. Then return to Step 4 and update your recognition kit with what you learned.

Tips for Long‑Term Success

• Start small. Don’t try to implement all WCAG criteria at once. Pick three that matter most for your current project and master them.
• Build a habit. Set a recurring calendar reminder every Monday to review one accessibility principle. Over weeks, recognition becomes automatic.
• Use the right tools. Plugins like axe‑dev (browser extension) or the WAI Evaluation Tools list can automate some checks, freeing your brain for higher‑level thinking.
• Share your kit. Encourage teammates to adopt the same visual reminders. A shared team board or Slack channel for accessibility tips keeps everyone oriented.
• Remember: Recognising an issue is half the battle. When you see a potential problem, fix it immediately—don’t bookmark it for later. “Later” rarely comes.

By shifting from recall to recognition, you turn an overwhelming burden into a manageable, visual workflow. Your designs will still be beautiful, but now they’ll also be inclusive. That’s the kind of good designer the web needs.