Menu

Accessibility

WCAG Review

A practical UX method for assessing products against defined WCAG criteria and identifying measurable accessibility compliance gaps.

How to run a WCAG review to evaluate compliance, document gaps, and prioritise accessibility remediation.

4 min read

What it is

A review is a UX method used to assess how well a product meets the Web Content Guidelines (WCAG).

It involves evaluating , content, and against specific criteria defined in the framework.

These guidelines cover areas such as perceivability, operability, understandability, and robustness.

The review identifies where the product meets or fails to meet compliance levels such as 2.1 AA.

It combines manual testing and tooling to assess both technical compliance and real .

The focus is on measurable standards and clear pass or fail criteria.

The goal is to ensure requirements are met and to highlight what needs fixing.

A strong WCAG review balances strict criteria checks with practical usability impact for real users.

When to use it

Use this method when compliance is required or expected.

It is most useful when:

you need to meet WCAG standards
you are working in regulated sectors
you are preparing for launch or audit
you need clear compliance reporting
you want to reduce legal risk

It is less useful when:

you are exploring early concepts
compliance is not a requirement
there is no plan to act on findings
WCAG reviews are often used alongside accessibility audits.

Key takeaway

Run a WCAG review when you need explicit evidence of compliance status against recognised criteria.

How to run it

Set up properly

Fix the scope before you start: which and level you are reviewing against, and which pages, flows and components are included. A review without a stated level produces findings nobody can act on.

Cover whole journeys rather than representative pages. Conformance is claimed for a path through the product, not for a screenshot of it.

Run the method

reviews are structured and criteria-based. Unlike a broader audit, the output is a pass or fail against a published standard, so the discipline is in resisting interpretation.

  1. Assess each element against the specific success criterion, and cite it. A finding without a criterion is an opinion wearing a standard's clothes.
  2. Test keyboard and focus states, including focus visibility and whether focus is ever trapped somewhere a keyboard cannot leave.
  3. Check compatibility on real assistive technology rather than inferring it from the markup.
  4. Review colour contrast and against the thresholds for the level you are claiming, in every interactive state.
  5. Record pass, fail or not applicable against each criterion, with evidence. Silence on a criterion reads as untested, which is what it is.

Focus on the standard, not your interpretation of it. Where a criterion is genuinely ambiguous, say so and record the reading you applied.

Capture and make sense of it

The value comes from clear compliance . After the review, document:

  • Issues grouped by criterion, so gaps are visible at a glance
  • Severity and user impact alongside the technical failure
  • Which criteria are met, failed, and untested
  • A remediation order that starts with blockers, not with easy wins

Use this to guide remediation. A review earns its keep when it becomes a work plan, not when it becomes a certificate.

What to look for

Focus on:

Perceivable: can users access content in different ways
Operable: can users navigate and interact
Understandable: is content clear and predictable
Robust: does it work across technologies
Compliance: whether standards are met

Where it goes wrong

Most issues come from:

If it’s only about passing, suffers.

Treating conformance as the goal rather than the floor
Relying on automated checks, which cannot judge whether a label is meaningful
Interpreting criteria loosely, so the same review would fail under scrutiny
Recording a pass while the real user impact goes unmentioned
Producing a compliance document that never becomes a work plan

What you get from it

Done properly, this method gives you:

A criterion-by-criterion picture of where you stand
A structured list of gaps, with evidence attached to each
A remediation order that starts with blockers rather than easy wins
A defensible answer when somebody asks whether you conform

Key takeaway

It helps you meet recognised standards properly.

Get in touch

If this sounds like something you need, we can run a WCAG review and help you meet accessibility standards with confidence.

No guesswork. No assumptions. Just clear, compliant, usable design.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What is a WCAG review in UX?

It is a method for assessing compliance with accessibility standards.

When should you run a WCAG review?

Before launch, during audits, or when improving accessibility.

What does WCAG stand for?

Web Content Accessibility Guidelines, the W3C standard for making digital content usable by people with disabilities. It is organised under four principles, perceivable, operable, understandable and robust, with three conformance levels: A, AA and AAA. AA is the usual target.

Is it the same as an accessibility audit?

No. It focuses specifically on compliance criteria.

Does a WCAG review improve UX?

Yes. It ensures accessibility standards are properly met.

Quick take

If you need to know whether you meet accessibility standards, run a WCAG review.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer