Why 4.2 Million People Can't Buy What They Want Online: Breaking Down Website Accessibility Barriers

Every day, 4.2 million disabled users abandon their shopping carts because the websites they visit were built without them in mind. That number deserves a moment of stillness before we move on—not because it makes a compelling statistic, but because behind it are real people who wanted to buy something ordinary: a birthday gift, a new pair of shoes, a book. They couldn't. Not because of any limitation they carry, but because of choices made by designers and developers who never paused to ask who else might be in the room.

This is not primarily a compliance problem. It is a comprehension problem—and the distinction matters enormously.

The invisible walls that pass every automated test

Disabled consumers represent $13 trillion in global spending power. Yet research from WebAIM shows that 96.3% of home pages fail basic accessibility tests. The most common failures are not exotic edge cases: missing alt text on images, poor colour contrast, broken keyboard navigation, unlabelled form fields. These are foundational elements. They are also, crucially, invisible to sighted mouse users—which is precisely why they persist.

When developers think about accessibility, they often picture a compliance checklist or a legal requirement. When a blind user thinks about accessibility, they picture independence: the ability to complete a task that everyone else completes without thinking. Screen readers do not "see" a website. They parse semantic HTML to build a mental map of content—headings, landmarks, labels, structure. When that structure is absent or broken, the map cannot be drawn. The user is not slowed down; they are stopped entirely.

Accessibility checkers can catch many of these failures before a site ever reaches a user. Accessibility Insights is one tool that makes this process approachable. But tools only work when the people using them understand why the underlying structure matters—not just that a rule requires it.

The 71% of disabled users who leave inaccessible websites immediately are not being difficult. They are responding rationally to an environment that has told them, through its design, that their presence was not anticipated.

What Hypatia sees in this

There is a philosophical framework that illuminates this situation more clearly than any usability audit: the Stoic concept of oikeiôsis, which roughly translates as "belonging" or "appropriate connection." The Stoics, and Marcus Aurelius in particular throughout the Meditations, returned again and again to a simple premise—that human beings are constitutively social, that we are built for participation in a shared world, and that the health of any community depends on whether its structures genuinely extend that invitation to everyone. Accessibility failures are not neutral oversights. They are, in the Stoic sense, a failure of oikeiôsis—a severing of appropriate connection.

This reveals something that most accessibility advice quietly steps around: the problem is not primarily technical. It is a failure of moral imagination at the design stage. The question "who will use this?" was either never asked, or asked too narrowly. A developer who has never used a screen reader, never navigated a site by keyboard alone, never experienced the disorientation of a page that announces nothing when a form fails—that developer does not lack skill. They lack the imaginative act of placing themselves inside a different experience.

This means the solution is not simply to retrofit alt text onto existing images or run an accessibility scanner before launch. Those actions matter, but they are downstream of something more fundamental: the cultivated habit of asking, at the beginning of every design decision, who is excluded by this choice?

For readers who live with disabilities and encounter these walls daily, this framing is important in a different way. The frustration you feel when a checkout process defeats your screen reader, or when a video has no captions, or when a form cannot be completed by keyboard—that frustration is not an overreaction. It is an accurate perception of something real. You are not failing to adapt to technology. Technology failed to account for you. The examined life, in the tradition Hypatia herself inhabited, requires that we see situations clearly rather than internalise fault that belongs elsewhere.

The harder truth that most accessibility advice misses is this: organisations that treat accessibility as a late-stage add-on are not just creating poor user experiences. They are communicating, through their choices, that certain users were not considered worth designing for from the start. That communication lands. Users feel it. And the $13 trillion in spending that walks away from inaccessible websites is only the measurable surface of something much larger—a loss of participation, dignity, and flourishing that cannot be captured in a cart abandonment rate.

Building with semantic HTML from the first line of code, labelling every form input, structuring headings as genuine navigation—these are not concessions to edge cases. They are the baseline conditions for a digital environment that actually belongs to everyone who needs to use it.

What to do this week

Before you close this tab, choose one concrete thing based on where you are in this:

If you manage or build a website: Run Accessibility Insights on your most-visited page today. Do not aim for a full audit. Look only at heading structure and form labels. Fix what you find. Then read What Semantic HTML Means and Why AI Cares About It to understand the reasoning behind what you're doing—not just the rule.

If you navigate accessibility barriers as a user: The Write Clear Accommodation Requests That Get Results course is a practical place to start building language for what you need and how to ask for it. You can also use the Design Accessible Documents From Templates prompt to make your own materials easier for others to read—because sometimes we need to build the accessibility that hasn't been built for us.

If you're supporting someone else: The Stop Energy-Draining Research Tasks with Smart AI Delegation course addresses something adjacent but real: the cognitive load of constantly navigating systems that weren't built with you in mind. That load is worth taking seriously.

Small, grounded actions taken this week matter more than a comprehensive plan that begins next quarter.

Explore further

• What Alt Text Is and Why AI Helps Create It — A clear explanation of one of the most common accessibility failures and how to address it without it becoming a burden.
• Screen Readers and How AI Makes Them Better — Understand how screen reader users actually experience a website, and where AI is beginning to close real gaps.
• What Accessibility Checkers Do and Why They Save Hours — A practical look at what automated tools can and cannot catch, and how to use them as a starting point rather than a finish line.