Menu

Accessibility

Accessibility Audit

A practical UX method for assessing accessibility barriers across interfaces, content, and interactions against recognised standards.

How to run an accessibility audit to identify barriers, prioritise fixes, and improve usability and compliance.

5 min read

What it is

An audit is a UX method used to evaluate how well a product meets standards and supports users with a wide range of needs.

It involves reviewing , , and content against recognised guidelines such as .

The audit looks at areas like keyboard , compatibility, colour contrast, structure, and .

It combines automated tools with manual review to identify issues that affect and compliance.

The focus is on making the product usable for everyone, not just meeting minimum standards.

The goal is to identify barriers and define what needs to be fixed.

Accessibility audits are most valuable when they improve real user outcomes, not just compliance checklists.

When to use it

Use this method when inclusivity and compliance matter.

It is most useful when:

you are launching or updating a product
you need to meet accessibility standards
you want to improve usability for all users
you are working in regulated sectors
you have received accessibility complaints or feedback

It is less useful when:

the product is still in very early concept stages
there is no intention to act on findings
Accessibility audits are often used before release and during optimisation.

Key takeaway

Run accessibility audits when delivery decisions can still be changed and fixed.

How to run it

Set up properly

Decide three things before you open the product: what is in scope, which standard and level you are measuring against, and how findings will be recorded. Scope decided halfway through is what turns a two-week audit into a two-month one.

Cover real user scenarios rather than a list of pages. A page can pass every check in isolation and still leave someone unable to finish a task that crosses three of them.

Run the method

audits are systematic and detailed. The structure is what makes the findings defensible when somebody disputes them.

  1. Review against the guidelines criterion by criterion, not screen by screen. Working screen-first turns an audit into a list of things that caught your eye.
  2. Test keyboard and focus states with the mouse put away entirely. Reaching a control but not being able to see where you are is still a failure.
  3. Check on the journeys that matter, not on a sample page. Announcements break most often around forms, modals, and content that updates without a page load.
  4. Assess colour contrast and in the states people actually meet: hover, focus, disabled, error, and text sitting over images.
  5. Sweep with automated tools, then manually validate every finding. Tools return false positives, and more dangerously they return silence where a person would object.

Focus on real , not just compliance. A product can satisfy every success criterion and still be exhausting to use with assistive technology.

Capture and make sense of it

The value comes from clear, actionable . After the audit, document:

  • Each issue with its severity and the criterion it breaks
  • The impact in plain terms: what a person cannot do, not what the code does
  • A prioritised order of fixes, weighted by how many people hit it and how hard
  • Recommendations specific enough to hand straight to a

Use this to improve and compliance, in that order. Fixing for compliance alone produces products that pass and still exclude people.

What to look for

Focus on:

Navigation: can users move through the product easily
Perception: can content be seen, heard, or understood
Interaction: can users interact without barriers
Structure: is content organised and readable
Compliance: does it meet required standards

Where it goes wrong

Most issues come from:

If it’s only about compliance, you miss the point.

Relying only on automated tools, which catch the mechanical failures and none of the judgement ones
Treating it as a checklist, so the product passes every criterion and is still exhausting to use
Auditing without knowing how disabled users actually use the product
Delivering findings nobody owns, which turns an audit into a document
Fixing the symptom on one screen rather than the pattern across the product

What you get from it

Done properly, this method gives you:

A clear view of what blocks people, in plain terms rather than criterion numbers
Fixes ordered by how many people hit them and how hard
Usability improvements that reach everyone, not only disabled users
A defensible position on legal and reputational risk

Key takeaway

It helps you create a product everyone can use.

Get in touch

If this sounds like something you need, we can run a full accessibility audit and help you fix the issues that are holding users back.

No guesswork. No assumptions. Just inclusive design that works for everyone.

FAQ

Common questions

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

What is an accessibility audit in UX?

It is a method for evaluating how accessible a product is for all users.

When should you run an accessibility audit?

Before launch, so there is still time to fix what it finds, and periodically afterwards as the product changes. Running one late turns findings into a backlog nobody clears; running one early enough makes them design decisions instead.

What standards are used?

WCAG (the Web Content Accessibility Guidelines) is what almost every audit works to, with level AA the usual target and 2.2 the current version.

UK public sector sites are also covered by the 2018 accessibility regulations, which point at EN 301 549, a standard built on WCAG, so meeting AA does most of the work either way.

Are automated tools enough?

No. Automated checks catch the mechanical failures (missing alt text, insufficient contrast, unlabelled fields), but they cannot tell you whether a label is meaningful, whether focus order makes sense, or whether someone can actually complete the task with a screen reader.

Does an accessibility audit improve UX?

Yes. It removes barriers and improves usability for everyone.

Quick take

If some users can’t use your product, it’s broken. An accessibility audit shows you where and why.

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