Designing with Heart: Bridging the Gap Between Intent and Accessible Websites

Accessibility isn't just a checkbox; it's the very foundation of good design. Yet, well-meaning designers often create sites that exclude people. Why does this happen, and what can we do about it? This Q&A explores the real stakes of inaccessible design and offers a practical starting point inspired by classic usability principles. Let's dive into the core issues and a solution that makes accessibility easier to remember and apply.

Why Is Accessibility a Matter of Life and Death?

Accessibility might sound like a technical nicety, but it has profound consequences. As Aral Balkan pointed out in his essay This Is All There Is, almost every design decision can affect life events or death events. A badly designed bus timetable app isn't just an inconvenience; it could cause someone to miss their daughter's fifth birthday party or the chance to say goodbye to a dying grandmother. When you exclude people from using a website or service, you're potentially blocking them from critical moments in their lives. That's why accessibility isn't optional—it's a moral and practical necessity. Every designer has the power to shape these outcomes, for better or worse.

Why Do Good Designers Still Create Inaccessible Products?

No designer wakes up wanting to exclude anyone. Yet, we all see websites with tiny text, confusing navigation, or interactions that work only with a mouse. The root cause isn't malice—it's cognitive overload. Designers are flooded with information: from advanced CSS tricks to usability guidelines, from color theory to inclusive language. Adding accessibility guidelines on top often feels like one more thing to remember. As the original text notes, there's just too much to recall. This mental burden can cause even the best-intentioned designer to overlook basic accessibility needs like sufficient color contrast, keyboard navigation, or screen-reader support.

What Is the "Recognition Rather Than Recall" Heuristic?

Jakob Nielsen's 10 Usability Heuristics, introduced in the 1990s, remain surprisingly relevant. Heuristic #6 is "Recognition rather than recall". Originally, this meant that users shouldn't have to remember information from one part of the interface to another; it should be visible or easily retrievable. This principle is powerful not just for users, but also for designers. Instead of forcing designers to memorize dozens of accessibility rules, we can apply the same heuristic to the design process itself. Make accessibility information visible and easy to access while designing, so that recognizing an issue becomes instinctive rather than a memory challenge.

How Can We Apply "Recognition Rather Than Recall" to Design Work?

To make accessibility recognition easier, we can integrate checkpoints directly into our design tools and processes. For example, use color contrast checkers that are built into your design software, keep a checklist of common accessibility patterns pinned to your workspace, or create a visual reference card for keyboard navigation requirements. The goal is to reduce the mental load by placing the necessary information where you're already looking. Tools like Sarah Horton and Whitney Quesenbery's book A Web for Everyone—Designing Accessible User Experiences offer structured guidance that can serve as an external memory. When a designer can glance at a reference instead of recalling from memory, they're more likely to catch issues early.

What Are the First Steps for a Designer to Improve Accessibility?

Start by acknowledging that you don't have to remember everything. Create a simple, personal accessibility checklist that covers the basics: text contrast (minimum 4.5:1 ratio), focus indicators for keyboard navigation, alternative text for images, and proper heading hierarchy. Use tools like browser extensions (e.g., WAVE or Axe) to test your live sites. Make it a habit to run a quick scan before you ship. Also, consider reading A Web for Everyone to build a solid foundation. The most important step is to recognize that accessibility is a continuous learning process, not a one-time fix.

What Resources Can Help Designers Learn More About Accessibility?

Beyond the classic book by Horton and Quesenbery, there are excellent free resources. The Web Content Accessibility Guidelines (WCAG) provide clear success criteria. The A11Y Project offers easy-to-digest checklists and patterns. For hands-on practice, try the Microsoft Inclusive Design Toolkit or the WAI Tutorials. The key is to rely on these references often—don't try to memorize. Bookmark them, print a quick guide, and integrate them into your daily workflow. Over time, the principles will become second nature, and you'll find yourself recognizing issues without needing to look them up.

How Can Accessibility Become a Habit, Not an Afterthought?

The best way to make accessibility habitual is to embed it into every stage of your design process. Start with a persona of a user with disabilities (e.g., someone using a screen reader, someone with low vision). During wireframing, ask: "Can a keyboard-only user navigate this?" During visual design, run a contrast check. Before development handoff, create accessibility notes. Review your own work against a short checklist regularly. Over time, these micro-habits remove the need for recall. You'll automatically check contrast, add labels, and structure content logically. It's not about perfection—it's about consistent, small actions that make your designs inclusive from the start.