10 Critical Insights for Designing Accessible Websites (And Why Good Intentions Aren't Enough)

Every designer I know genuinely cares about their users. They want to create inclusive, usable experiences. Yet, somehow, inaccessible websites still flood the internet. Why? It's not malice—it's information overload. The sheer volume of guidelines, from usability heuristics to accessibility standards, overwhelms even the best-intentioned creative minds. This article distills the core issue and offers a practical path forward: making accessibility issues recognizable during the design process, not after. Here are ten essential things you need to know to bridge that gap.

1. Designers Are Good People – But Their Work Can Still Exclude

I have never met a designer who said, “I don’t care if someone can’t read this text” or “Who cares if this is confusing?” Designers are empathetic by nature. Yet, everywhere we look, there are websites where text is too small, contrast is poor, navigation is a maze, or interactive elements break for assistive technologies. The disconnect isn’t intent; it’s awareness. Many designers simply don’t recognize the accessibility issues in their own work until it’s too late. The first step to fixing this is acknowledging that good intentions alone aren’t enough—we need tools and mindsets that surface problems early.

2. Accessibility Is a Life-or-Death Matter

It’s tempting to think of web accessibility as a “nice-to-have,” but it can literally affect life events. Aral Balkan’s essay “This Is All There Is” illustrates how even a simple bus timetable app can become a barrier. A badly designed interface might cause someone to miss their daughter’s fifth birthday party or, tragically, the chance to say goodbye to a dying grandmother. These are not hypothetical extremes. Every design decision—from font size to button placement—can either include or exclude people from critical moments. Recognizing this stakes can transform how we prioritize accessibility from the start.

3. We Already Know the Diversity of Human Abilities – But Forget It in Practice

We know that not everyone sees perfectly, hears perfectly, thinks the same way, or moves the same way. Yet when we sit down to design, this knowledge often fades into the background. The reason is simple: our brains are wired to design for a “default” user that looks and behaves like ourselves. This cognitive bias, combined with time pressure and feature checklists, leads to exclusion. The solution isn’t to memorize every disability statistic, but to embed reminders and checks into our daily workflow. For instance, using persona cards that include a range of abilities can keep diversity top of mind.

4. The Real Problem Is Information Overload

Consider the vast amount of guidance a modern designer must absorb: usability heuristics, color contrast ratios, ARIA roles, responsive breakpoints, performance budgets, SEO rules, and accessibility laws (WCAG, Section 508, etc.). It’s too much to recall. The problem is not that designers are lazy or uncaring—it’s that human memory is finite. Expecting anyone to remember every single guideline from every A List Apart article is unrealistic. This overload leads to decision fatigue and, ultimately, inaccessible outcomes. We need a different approach: one that reduces the cognitive load on designers.

5. Shift from Recall to Recognition – For Designers, Too

Jakob Nielsen’s 10 Usability Heuristics include “Recognition rather than Recall.” Typically applied to users, this principle states that information needed to use a design should be visible or easily retrievable. I propose we apply the same logic to designers. Instead of forcing designers to remember all accessibility rules, we should make that information visible and retrievable within their design environment. Imagine a tool that flags low contrast while you pick colors, or a plugin that warns about missing alt text as you export. Recognition over recall can be a game-changer for inclusive design.

6. Nielsen’s Heuristics Are a Foundation, Not a Legacy

Some may dismiss Nielsen’s heuristics as outdated (they date to the mid-1990s). But their core ideas remain timeless, especially when adapted for modern challenges. For accessibility, heuristic #2 (“Match between system and the real world”) and #4 (“Consistency and standards”) directly support inclusive design. Don’t throw them away; build on them. By revisiting these heuristics through an accessibility lens, we create a simple mental framework that helps designers spot issues without memorizing endless checklists. Start with heuristics, then layer on accessibility-specific heuristics like those from the “Web for Everyone” book.

7. ‘A Web for Everyone’ Offers Practical, User-Centered Guidance

Sarah Horton and Whitney Quesenbery’s book “A Web for Everyone: Designing Accessible User Experiences” is a treasure trove. It translates complex WCAG guidelines into actionable design principles, organized around how people interact with the web: by seeing, hearing, moving, and thinking. The book emphasizes that accessibility isn’t just about compliance—it’s about creating a seamless experience for everyone. Designers can use it as a quick reference guide, with examples and checklists that make recognition easier. If you read one book on accessible design, make it this one.

8. Make Accessibility Issues Visible in Your Design Process

The key to reducing exclusion is to surface accessibility problems early. This means integrating checks into wireframing, prototyping, and development stages. Use browser extensions (like the WAVE tool) or design software plugins (like Stark for Sketch/Figma) that provide real-time feedback. During design reviews, add a line item for “accessibility scan.” Create a shared checklist that lives in your project management tool, not just in your head. When an issue is recognizable at a glance, you’re far more likely to fix it before launch.

9. A Little Homework Goes a Long Way

Other A List Apart articles offer innovation and insight; this one gives you homework. Commit to one small change this week: learn to check color contrast using a simple tool, or review a page with a screen reader. The return on this small investment is huge. Over time, these habits become automatic, and the things that seemed overwhelming become part of your design vocabulary. Recognition becomes instinct. Your future self—and your users—will thank you.

10. The Goal Is Not Perfection – It’s Progress

Accessibility is a journey, not a final state. No website will ever be 100% accessible to every person in every circumstance. But the gap between good intentions and good outcomes narrows with each conscious effort. Start by choosing one heuristic or one guideline to focus on next week. Use tools that support recognition. Read one chapter from “A Web for Everyone.” Share your learnings with your team. When we accept that we can’t remember everything, we free ourselves to create systems that help us remember what matters most: the people we design for.

In conclusion, the path from good intentions to truly accessible websites lies not in memorizing more rules, but in making accessibility recognizable at every step of the design process. By embracing recognition over recall, leveraging timeless heuristics, and integrating practical tools, we can transform our work from exclusionary to inclusive. The homework is simple: start small, stay consistent, and remember that every design decision can be a life-affirming one. Let's build a web for everyone.