Accessibility Audit

An accessibility audit is a structured assessment of whether a digital product can be used by people with disabilities, typically evaluated against the Web Content Accessibility Guidelines. It produces an inventory of barriers, each mapped to the specific success criterion it fails, with severity and remediation guidance attached.

The most important practical fact about auditing is that automated tools detect only a minority of accessibility issues. They reliably find missing alternative text, insufficient colour contrast, absent form labels, and structural markup errors, which is genuinely useful. They cannot assess whether alternative text is meaningful, whether the reading order makes sense, whether a custom component behaves correctly with assistive technology, whether focus management works during dynamic changes, or whether content is comprehensible. Organizations that run a scanner, fix the reported items, and declare compliance have addressed a fraction of the real barriers.

Manual testing is therefore the substantive part of an audit. Navigating the entire product by keyboard alone, testing with screen readers on the platforms the audience actually uses, checking behaviour at high zoom and increased text size, verifying that dynamic content changes are announced, and confirming that error handling works for someone who cannot see the visual indicator all require a person. These tests find the barriers that actually prevent task completion.

Testing with disabled users adds a further category that neither automation nor expert review reaches. Technical conformance does not guarantee usability, and a product can satisfy every success criterion while remaining exhausting to use with assistive technology. Sessions with people who use screen readers, magnification, voice control, or switch access as a matter of course reveal friction that a sighted expert simulating those conditions will not experience.

Scope should be defined by journey rather than by page count. Auditing every page of a large site is impractical and unnecessary; auditing the complete critical journeys, including registration, purchase, account management, and support, plus a representative sample of each template, covers the barriers that matter with proportionate effort. Barriers on a checkout affect a business far more than barriers on an archived article.

The legal dimension has become material rather than theoretical in many jurisdictions. Public sector bodies in the European Union and the United Kingdom operate under explicit accessibility requirements with published statement obligations, the European Accessibility Act extends requirements to a range of private sector services, and litigation over inaccessible websites has been substantial in the United States. Audits increasingly serve a compliance evidence function alongside their improvement function.

Findings need translating into scheduled work to produce anything. An audit report listing several hundred issues by success criterion is an inventory rather than a plan, and it typically stalls. Grouping issues by root cause, since most repeat across templates, prioritizing by journey impact and by number of users affected, and assigning them into the delivery backlog with owners is what converts the document into remediation.

Because most issues originate in components and templates rather than in individual pages, durable improvement comes from fixing them at source. In practice the audit is delivered through UX audit work, the systemic remediation is applied to the component library within product design, and for organizations with statutory obligations, particularly in the public sector, the audit also produces the evidence base for the accessibility statement they are required to publish.