Test properly
Automated tools help, but manual checks are needed for many barriers.
WCAG audit guide
WCAG audit service UK
A WCAG audit should help teams understand what is blocking access, what matters most and what to fix first. The goal is practical improvement, not just a long list of failures.
AXS Audit connects WCAG checks with real user journeys, cognitive access and clear remediation priorities.
Prioritise impact
A useful audit explains severity, affected users and practical next steps.
Improve access
WCAG matters most when it leads to better experiences for real people.
What a WCAG audit should include
Automated scan
Useful for quickly identifying common issues.
Manual testing
Human checks for keyboard access, focus order, labels and interaction problems.
Content review
Headings, links, instructions, plain language and cognitive load.
Key journeys
Forms, checkout, enquiries, booking, login or application paths.
Evidence
Clear findings and examples.
Prioritised fixes
Actionable recommendations by impact and urgency.
WCAG is necessary, not sufficient
WCAG criteria are essential, but users experience pages as journeys, not checklists.
A useful audit should connect WCAG issues to real user impact:
what task is blocked?
who is affected?
how serious is it?
what should be fixed first?
what can wait?
what evidence supports the recommendation?
How Calling All Minds approaches audit work
Technical
Code, structure, labels, focus, keyboard and compatibility.
Content
Headings, link text, instructions, readability and plain language.
Journey
Forms, decisions, tasks, errors, recovery and completion.
Cognitive
Memory load, ambiguity, layout, density and friction.
When to pair audit with toolbar
A toolbar can help users adjust the experience. It should not be used to avoid fixing WCAG issues.
AXS Audit finds barriers and prioritises fixes. AXS Toolbar helps users read, listen, simplify, summarise and navigate.
Turn WCAG findings into better access
AXS Audit helps organisations understand issues, prioritise fixes and support users more effectively.
Frequently asked questions
What is a WCAG audit?
A WCAG audit reviews a website against Web Content Accessibility Guidelines and identifies issues that may affect disabled users.
Is automated testing enough for WCAG?
No. Automated tests find some issues, but manual testing is needed for many accessibility barriers.
What should a WCAG audit report include?
It should include findings, examples, impact, affected pages or components and prioritised recommendations.
Does WCAG cover cognitive accessibility?
Some criteria relate to understanding and navigation, but cognitive accessibility often needs deeper content and journey review.
How does AXS Audit help?
AXS Audit helps organisations identify accessibility barriers and prioritise practical fixes.
Can a toolbar make us WCAG compliant?
No. A toolbar can support users, but compliance depends on the underlying site and content.