Articles

The Real Accessibility Problem We Refuse to Talk About

Accessibility is one of those words everyone agrees with.

No one argues against it.

No one openly dismisses it.

Most institutions claim they already care about it.

And yet, exclusion remains ordinary.

So ordinary, in fact, that we’ve learned to explain it away.

Accessibility is where responsibility goes to rest

Most systems are not designed to include. They are designed to function — for someone.

Only later does accessibility enter the conversation, usually as a checklist. A correction. A requirement to be met so that work can continue without friction or guilt.

A ramp is added.

A feature is enabled.

A policy is cited.

At that point, accessibility becomes proof of intent, not proof of experience.

The system itself remains unchanged.

The question we rarely ask

Every product, space, or policy answers a silent question before it ever reaches a user:

Who is this for?

That question is almost never debated out loud. It’s decided through habit. Through precedent. Through who has always been in the room.

The result is a narrow definition of “normal” — one that quietly excludes anyone who moves, thinks, processes, or lives differently.

When people don’t fit, the system doesn’t see a flaw in itself.

It sees an inconvenience.

Why access feels exhausting

Being allowed in is not the same as belonging.

Many people technically have access — to buildings, to systems, to opportunities — and still experience them as draining, unreliable, or demeaning.

Because access often comes with conditions:

• extra planning

• extra explanation

• extra dependence

• extra effort just to do what others do without thinking

These costs don’t appear in audits or reports. But they shape behaviour. They determine who stays, who participates fully, and who slowly disengages.

Exclusion rarely announces itself. It works quietly.

Disability just makes the cracks visible

Disability is often treated as a special category.

In reality, it exposes a universal truth: systems designed for a narrow range of bodies and abilities are fragile.

Age exposes it.

Illness exposes it.

Injury exposes it.

Caregiving exposes it.

Disability is not the outlier. It is the stress test.

And most systems fail that test long before they admit it.

Why good intentions don’t fix this

Most accessibility failures are not caused by indifference.

They are caused by timing.

Accessibility is considered after decisions are made, after budgets are allocated, after designs are final.

At that stage, the question is no longer “How do we include?”

It becomes “What can we adjust without changing too much?”

That is how exclusion survives even inside well-meaning systems.

A more uncomfortable way to frame accessibility

Instead of asking:

Is this accessible?

We should ask:

What kind of body, mind, and life does this assume — and who is forced to adapt as a result?

That question does not allow for easy fixes.

It demands accountability at the level of design, power, and decision-making.

Why Accessibility Still Feels Incomplete

Accessibility is widely discussed, increasingly regulated, and often publicly affirmed. Most organizations today can point to policies, standards, or features intended to demonstrate commitment to inclusion.

And yet, for many people, everyday interactions with systems, products, and institutions remain difficult, unreliable, or exhausting.

This persistent gap suggests that accessibility is not failing because it is ignored, but because it is misunderstood.

Accessibility Is Commonly Treated as an Outcome

In most contexts, accessibility is addressed after something already exists.

A building is completed, then assessed.

A product is launched, then adapted.

A policy is written, then reviewed for inclusion.

By the time accessibility enters the conversation, the most consequential decisions have already been made. What remains is adjustment rather than design.

This approach produces compliance, but not coherence. Systems may technically allow access, while still placing disproportionate effort on certain users to participate fully.

The Unexamined Assumption of the “Intended User”

Every system is built with an intended user in mind, whether explicitly stated or not. This user is assumed to move, communicate, process information, and adapt in predictable ways.

These assumptions are rarely interrogated, largely because they reflect those who are most often present in decision-making spaces.

When people fall outside these assumptions, they are treated as exceptions. Accessibility then becomes a matter of accommodating difference rather than reconsidering the original frame.

This distinction is critical. Accommodation preserves the system as it is. Inclusion questions whether the system was designed appropriately to begin with.

Why Access Does Not Guarantee Usability

Access is often measured in binary terms: accessible or inaccessible. Usability, however, is cumulative.

It is shaped by:

• the effort required to engage repeatedly

• the consistency of the experience

• the degree of independence maintained

• the dignity with which participation occurs

These factors are rarely captured in audits or reports, yet they determine whether people remain engaged or quietly disengage over time.

When usability is overlooked, exclusion does not always appear as denial. More often, it appears as attrition.

Disability as a Diagnostic Lens

Disability is frequently treated as a special category, but in practice it reveals the limits of narrow design.

The same systems that fail disabled users often falter for people who are aging, injured, ill, or navigating temporary constraints. Disability does not create these weaknesses; it makes them visible sooner.

In this sense, disability functions less as an edge case and more as a diagnostic lens — exposing where systems lack resilience, flexibility, and foresight.

Good Intentions Are Not a Structural Safeguard

Many accessibility gaps persist despite genuine commitment. This is not a failure of values, but of process.

When accessibility is considered late, it competes with fixed timelines, budgets, and priorities. The question shifts from “How should this work for everyone?” to “What can be changed without altering too much?”

This is how exclusion becomes embedded even within well-intentioned systems.

Reframing the Accessibility Question

The most common question asked is: Is this accessible?

A more foundational question is:

Who was this designed for, and whose needs shaped the original decisions?

This reframing moves accessibility upstream — into strategy, governance, and design — rather than leaving it at the level of correction.

The Real Accessibility Problem

The core problem is not the absence of accommodations. It is the persistence of unexamined assumptions that shape systems long before accessibility is addressed.

As long as accessibility is treated as an addition rather than a starting point, exclusion will continue — quietly, systematically, and often unintentionally.

Accessibility fails not because it lacks support, but because it is introduced too late to influence what matters most: how systems are imagined in the first place.