Our Audit Methodology
What Separates a Real Audit from a Quick Scan
Every audit follows WCAG-EM 2.0, the W3C’s published evaluation methodology. Structured, repeatable, and defensible, so you get findings you can act on with confidence.
What Is WCAG-EM?
WCAG-EM (WCAG Evaluation Methodology) 2.0 is the W3C’s published methodology for evaluating how well a website or digital product meets WCAG 2.
It was developed because running an automated scanner on a single page, or even doing ad hoc manual checks, doesn’t give you a reliable or defensible picture of your site’s accessibility. You need a structured, documented process.
Every AMTAA audit follows this methodology precisely. That means your findings reflect how your real site performs across real user journeys, not just what a scanner picks up on a single page.
WCAG-EM is intended for experienced evaluators. It does not change existing WCAG requirements; it provides the best-practice methodology for verifying them rigorously.
An audit conducted to WCAG-EM standards carries weight with regulators, grant funders, public sector procurement teams, and legal advisors. It demonstrates you didn’t just run a free checker; you followed a documented, professional process.
What’s New in WCAG-EM 2.0
The W3C published WCAG-EM 2.0 as a Group Note in July 2026, updating the original 2014 version. The five-step process is largely the same. The main changes are what it can be used for, how the sample is described and some updated guidance.
- Wider scope: it now covers apps and other digital products, not just websites.
- Sample sets: evaluators now select a “sample set” of views, which can be web pages, app screens or documents, rather than a sample of web pages only.
- Updated guidance: design systems and native platforms are now named among the things to identify in the exploration step.
For you, it means every finding in your report rests on the current, published W3C version of the methodology.
The 5 Steps of WCAG-EM
A documented, repeatable process applied to every audit we deliver.
1
Define Scope
We agree the boundaries of the evaluation, including which parts of your site, which user journeys, target WCAG level, and whether mobile or desktop is in scope. No surprises at the report stage.
2
Explore the Website
We map your site’s functionality, technology stack, design patterns, and interactive components before testing begins, so nothing gets missed and our sample accurately represents the whole.
3
Select a Representative Sample
We choose a structured set of pages covering all key templates, journeys, and functionality. Auditing every page isn’t efficient or necessary. Auditing the right pages is. This step is where inexperienced auditors cut corners.
4
Audit the Sample
We manually test each selected page against WCAG 2.2 AA success criteria using screen readers, keyboard navigation, colour contrast tools, and automated scanners. Combined, not siloed. This is where the real expertise lies.
5
Report Findings
You receive a clear, prioritised report documenting methodology, sample pages, every issue found, its severity, and exactly how to fix it, in plain English your team can act on immediately.
Tools We Use and Why
Most accessibility checks can’t be fully automated, so we use two kinds of tool. Scanners give fast, consistent coverage. Assistive technology shows how your site really behaves for disabled users. Neither replaces expert judgement; both support it.
Source: W3C, WCAG-EM 2.0, 2026
NVDA
Shows how your site works for blind and low-vision users on Windows
WAVE
Marks issues directly on the page, so findings are easy to see and explain
axe DevTools
Fast, repeatable rule checks, using the same engine as our automated testing
Accessibility Insights
Guided manual checks for keyboard access and focus order
Stark
Checks colour contrast and colour-blindness views, including at design stage
BrowserStack
Tests on real phones, tablets and browsers we don’t have on the desk
Why Methodology Matters Commercially
A WCAG-EM audit isn’t just more thorough. It opens doors a free tool scan never could.
Legal & Regulatory Defensibility
If your accessibility is ever questioned by a regulator or in a legal claim, a documented WCAG-EM audit gives you a clear record of what was tested, what was found and what you did about it. An automated scan alone does not.
Public Sector Procurement
Public sector buyers may ask for evidence of WCAG 2.2 AA conformance in tender requirements. A structured, documented audit gives you something concrete to show.
Grant Funding & Investment
Some funders and public investment bodies ask for accessibility evidence. A WCAG-EM audit gives you documented evidence to share.
Ready to Commission a WCAG-EM Audit?
Get in touch and we’ll talk through your site, your timelines, and the right next step for you.