Breaking: Web Accessibility Failures Persist Despite Good Intentions
Leading accessibility advocates warn that even well-meaning designers are unintentionally excluding millions of users—and the root cause is cognitive overload. In a new proposal presented to the web design community, an expert argues that the sheer volume of accessibility guidelines overwhelms designers, leading to recurring usability failures.
“Designers are good people. I have never heard a designer say, ‘I don’t care if somebody can’t read this text,’” the expert noted. “Yet some designs still exclude people because there’s too much to recall.” The solution, they suggest, is to adapt a classic usability principle—recognition rather than recall—for designers themselves.
The Urgent Problem: Life-and-Death Consequences
The issue is far from trivial. Drawing on a well-known essay by Aral Balkan, the expert emphasizes that poor design can directly impact life events and even death events. “A straightforward bus timetable app, if designed badly, might cause someone to miss their daughter’s fifth birthday party—or the chance to say goodbye to a dying grandmother,” the expert explained. These are not hypotheticals; they are everyday realities for users with disabilities.
Yet despite widespread knowledge that not everyone sees, hears, thinks, or moves the same way, exclusionary designs remain common. The expert points to a fundamental disconnect: designers know the right things to do but cannot keep all the guidelines in mind simultaneously.
Background: The Overload of Design Guidance
For decades, organizations like A List Apart have published countless articles on innovation, insight, and accessibility. Designers are expected to absorb all of this—plus emerging standards, tools, and user research. “It is too much,” the expert said. “Recognizing accessibility issues while designing is the missing link.”
Jakob Nielsen’s 10 Usability Heuristics, introduced in the mid-1990s, have long guided user interface design. Heuristic №6, “Recognition rather than Recall,” originally applied to users: information required to use a design should be visible or easily retrievable. The expert now proposes flipping that heuristic for designers. “Let’s say that the information required to produce the design should be visible or easily retrievable when needed,” they said. This shift could make accessibility issues easier to spot during the creative process, not just during testing.
What This Means: A New Approach to Inclusive Design
If adopted, this recognition-based heuristic could fundamentally change how designers approach accessibility. Instead of memorizing long checklists, teams would embed accessibility cues into their tools and workflows—similar to how integrated development environments highlight code errors in real time. The book A Web for Everyone by Sarah Horton and Whitney Quesenbery, which the expert recommends, already points in this direction.
The proposal also challenges the industry to systematize empathy. “We don’t need to be mean or careless to exclude people,” the expert emphasized. “We just need to be overwhelmed.” By reducing cognitive load on designers, the industry can move from good intentions to genuinely inclusive outcomes. Early adopters include design systems that automatically flag low-contrast text or missing alt text.
Immediate Steps for Designers and Teams
- Adopt design tools that surface accessibility rules in context (e.g., color contrast checkers built into wireframing software).
- Create “recognition checklists” for common failure points, such as keyboard navigation and screen reader compatibility.
- Integrate peer reviews focused specifically on cognitive load—both for users and for the design process itself.
The expert’s entire proposal is outlined in the original article, which also provides homework for designers. The takeaway is clear: good designers can build bad websites, but with the right heuristics, they can do better. The clock is ticking—millions of users depend on it.