An accessibility audit is a structured evaluation of a website or application
against an accessibility standard — typically WCAG 2.1 or 2.2 Level AA. It
produces a documented record of conformance and non-conformance, providing
an organisation with a clear picture of its current accessibility status and
a prioritised list of issues to address.
[1]
Automated scan only
Fast and scalable. Covers rule-based WCAG failures detectable by automated
tools. Does not cover behavioural, quality, or contextual failures. Appropriate
as a baseline or for continuous monitoring, not as a standalone compliance audit.
Expert manual audit
A trained accessibility specialist manually reviews a representative sample
of pages and templates using keyboard testing, screen reader testing, and
visual inspection. Covers a much broader range of WCAG criteria but is
time-consuming and expensive for large sites.
Combined audit
Automated scanning plus manual expert review. The most credible and thorough
approach. The automated scan identifies obvious failures efficiently; manual
review covers what automation cannot.
User testing with disabled users
Structured usability testing with participants who have disabilities. Identifies
real-world usability issues that may not be captured by technical WCAG
compliance checks. Complements rather than replaces expert audit.
[2]
Define the scope
Identify which parts of the site or application will be audited. For large
sites it is not practical to test every page — instead, identify a
representative sample covering:
Define the standard
Specify which version of WCAG and which level will be tested against, and
any additional standards (Section 508, EN 301 549) that apply.
Define the testing environment
Specify the browsers and assistive technologies to be used. A minimum
testing matrix for a WCAG 2.1 AA audit typically includes:
Step 1 — Automated baseline
Run automated scans across all pages in scope. Tools such as a11ytest.ai
provide comprehensive scanning against WCAG 2.0, 2.1, and 2.2 alongside
Section 508 and EN 301 549, with issues structured and ready to export.
This identifies rule-based failures efficiently and creates a baseline
for manual testing.
[3]
Step 2 — Keyboard testing
Navigate all pages and user journeys using keyboard only. Test skip links,
focus order, focus visibility, modal dialogs, dropdowns, and all interactive
components.
Step 3 — Screen reader testing
Test with NVDA on Windows and VoiceOver on macOS at minimum. Navigate by
headings, landmarks, and links. Test all forms and dynamic interactions.
Step 4 — Visual inspection
Check colour contrast including interactive states and non-text elements.
Check text spacing and reflow at 320px. Check for use of colour alone to
convey information.
Step 5 — Document review
Test any PDFs or downloadable documents in scope against PDF/UA requirements.
For each issue found, record:
A final audit report should include:
Last edited Apr 7, 2026, 7:42 PM · P**** J****