Designing with Recognition: A Practical Guide to Embedding Accessibility in Your Design Workflow

Introduction

Every designer I know is a good person. They care about inclusivity and usability. Yet, we all have encountered websites or apps where text is impossible to read, buttons are too small, or navigation is baffling. The gap between intention and outcome often stems from cognitive overload—designers have so much to remember (typography, layout, branding, interactions, and accessibility) that critical details slip through. This guide builds on a powerful idea from Jakob Nielsen's usability heuristics: Recognition rather than Recall. Instead of forcing designers to memorize every accessibility guideline, we will make accessibility issues visible during the design process. By following these steps, you will reduce exclusion and create experiences that work for everyone—without needing a PhD in accessibility.

What You Need

• Design tools (e.g., Sketch, Figma, Adobe XD, or pen and paper)
• Basic understanding of WCAG (Web Content Accessibility Guidelines)
• A heuristic evaluation checklist (we will build one)
• User personas representing diverse abilities (or access to real users)
• Color contrast analyzer tool (e.g., Stark plugin or online checker)
• Screen reader (optional but recommended)

Step-by-Step Guide

Step 1: Acknowledge the High Stakes

Begin by recognizing that design decisions have real consequences. As Aral Balkan argued in This Is All There Is, even a simple bus timetable app can affect life events—like missing a daughter's birthday—or death events, like failing to say goodbye to a dying grandmother. This is not hyperbole. When you start a project, take five minutes to write down one possible life-altering scenario that could fail if your design is inaccessible. Keep that note visible on your desk. This mindset shift will anchor every future decision.

Step 2: Recognize Human Diversity

We know that people vary in vision, hearing, cognition, and motor abilities. Yet we often design for an idealized, narrow user. To counter this, create a quick checklist of four human variations to always consider:

• Vision: low vision, color blindness, blindness
• Hearing: deaf or hard of hearing
• Cognition: memory, dyslexia, attention disorders
• Motor: limited dexterity, tremors, reliance on keyboard

Print this list and place it next to your workstation. Whenever you design an interface, scan the list and ask, “Would this work for each group?” This simple act turns abstract knowledge into a usable reminder.

Step 3: Adopt the Heuristic of Recognition over Recall for Designers

Jakob Nielsen's sixth usability heuristic says users should not have to remember information. We flip this: designers should not have to remember accessibility guidelines. Instead, make the needed information visible or easily retrievable at the moment of design. This means leveraging checklists, pattern libraries, and automated tools that surface issues immediately. For example, instead of memorizing WCAG color contrast ratios, use a plugin that gives real-time feedback as you pick colors. By reducing reliance on memory, you free mental energy for creative problem solving.

Step 4: Create an Accessibility Heuristic Checklist

Based on Nielsen's 10 heuristics and WCAG principles, create a short, actionable checklist tailored to your project. Keep it to 10 items or fewer. Example:

1. Perceivable: All information is available in more than one sensory modality (e.g., text + icon).
2. Operable: All functionality is available via keyboard alone.
3. Understandable: Language is plain, instructions are clear.
4. Robust: Content works with assistive technologies.
5. Color independence: Don't rely solely on color to convey meaning.
6. Sufficient contrast: Text vs. background meets WCAG AA (4.5:1 for normal text).
7. Scalable text: Users can resize text up to 200% without loss of content.
8. Focus indicators: Visible focus ring for keyboard navigation.
9. Error prevention: Provide confirmations, undo options.
10. Help and documentation: Offer context-sensitive help.

Print this checklist and use it before each design review.

Step 5: Integrate Heuristic Evaluation into Design Reviews

Do not wait until development to check accessibility. Include heuristic evaluation in your regular design critiques. For each screen or flow, go through the checklist with your team. If an issue is found, note it on the design file (use annotations or sticky notes). Make these evaluations mandatory, not optional. Over time, you will begin to spot patterns and proactively avoid common pitfalls.

Step 6: Use Real-World Testing and User Feedback

No checklist can replace feedback from real people with diverse abilities. Recruit 3–5 participants who use assistive technologies (screen readers, voice control, magnification). Run short, task-based tests. Observe where they struggle. Record the sessions (with permission) to share with the team. This step transforms abstract heuristics into lived experiences, making the need for accessibility emotionally tangible.

Step 7: Iterate and Document

Accessibility is not a one-time fix. After each round of testing, update both your design and your checklist. Document what you learned—write a short paragraph about the issue, why it happened, and how you resolved it. Share this inside your organization. Over time, you will build a knowledge base that makes accessibility recognition even easier for new designers.

Tips for Success

• Start small: Pick one heuristic (e.g., color contrast) and master it before adding more.
• Automate where possible: Use plugins for design tools that check contrast, text spacing, and alt text reminders.
• Talk to users early: Even one interview can change your perspective.
• Don't obsess over perfection: Focus on removing the biggest barriers first—it's better to have a slightly imperfect site that works for 90% of people than a perfect one that works for 60%.
• Celebrate small wins: When you make a button keyboard-accessible or write a clear error message, acknowledge it. Positive reinforcement builds habits.

Remember: The goal is not to memorize every rule but to recognize when something isn't inclusive right there in your design tool. By following these steps, you will move from good intentions to consistently accessible outcomes.