Accessibility

WCAG compliance does not mean usable

Meeting accessibility standards is essential, but passing criteria alone does not guarantee that people can move through an experience clearly, efficiently, or with confidence.

Why WCAG should be treated as a foundation rather than a finish line, and why accessibility only works properly when compliance and usability are designed together.

19 February 20246 min read

Why compliance gets mistaken for completion

From that point on, is considered done. The assumption is that because the product meets standards, it is now usable for everyone it was designed for.

That assumption is where things start to break down.

Because compliance is not the same as experience.

is essential. It provides a , a shared language, and a set of standards that help teams more inclusive products. Without it, accessibility would be far more inconsistent and far easier to ignore. But WCAG defines what should be possible, not what is actually easy, clear, or usable in practice.

It sets the floor, not the ceiling.

WCAG tells you whether access is possible. It does not tell you whether the experience is actually easy to use.

Why technically compliant products still feel difficult

In my experience, some of the most frustrating products to use are technically compliant.

They pass audits. They meet contrast ratios. They support keyboard . can access the content. On paper, everything checks out.

But when you actually try to use them, the experience tells a different story.

are still confusing.

Key takeaway

Passing checks can remove technical barriers while still leaving users with journeys that are harder than they should be.

Where the gap between access and use appears

Forms technically work, but require unnecessary effort to complete. is accessible, but difficult to understand when read out of . Content is available, but structured in a way that makes it hard to scan, , or act on. Interactions behave correctly, but not intuitively.

Nothing is technically broken.

But everything feels harder than it should.

This is the gap between compliance and .

focuses on whether something can be accessed.

UX focuses on whether something can be used.

Why that distinction matters in practice

When those two things are not aligned, the result is an experience that technically includes users, but still creates for them. The product does not block access, but it does not support , , or clarity either.

And that distinction matters more than most teams realise.

Because users do not measure compliance.

They experience difficulty.

If a takes too long, feels confusing, or requires too much effort, users will struggle regardless of whether the underlying implementation meets guidelines. In some cases, they will abandon entirely. In others, they will persist, but with frustration, reduced , and a higher likelihood of error.

None of that shows up in a compliance report.

Why WCAG works best as a foundation

What I have found over time is that works best when it is treated as a foundation, not a finish line.

It should inform how things are built, not define when the work is done. The real measure of is not whether something passes, but whether people can complete what they came to do, without unnecessary effort or confusion.

That requires a different mindset.

It means testing with real users, not just tools.

Why accessibility and UX need to work together

It means understanding how assistive technologies are actually used in practice, not just whether they are supported. It means looking beyond individual components and considering how entire behave from start to finish. It means recognising that is as much about and structure as it is about technical implementation.

This is where and UX need to work together.

Because one without the other is not enough.

A well-designed experience that is not accessible excludes users entirely. A compliant experience that is poorly designed includes users, but still makes things harder than they need to be. The goal is not to choose between the two, but to align them so that access and exist together.

That is where real inclusion happens.

Why minimum standards are only the start

In practice, this often requires going beyond what is strictly required.

Not because the guidelines are insufficient, but because real-world usage is more complex than any set of criteria can fully capture. Users bring different , different levels of familiarity, and different ways of interacting with technology. Designing for that variability means thinking beyond minimum standards and focusing on how the experience actually performs.

Compliance tells you if something is allowed.

tells you if it works.

And if the goal is to products that people can genuinely use, one without the other will never be enough.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services. The work usually starts where things have become harder than they need to be: unclear journeys, inconsistent products, competing priorities, or teams trying to move forward without a clear direction. I help simplify the problem, shape the right next step, and turn complexity into something people can actually use.

Previous feedback

Will Parkhouse

Senior Content Designer

01/20