WCAG 2.2 AA in UK Law: How the Standard Plays Into Equality Act Cases

WCAG 2.2 AA is the web accessibility standard that courts, the EHRC and expert witnesses refer to when assessing whether a UK website meets the Equality Act 2010's reasonable adjustments duty. It is not itself a legal instrument for private sector websites. The Equality Act does not reference it. But its adoption by the government for the public sector and its widespread use as expert evidence make it the practical benchmark.

For an automated WCAG 2.2 AA audit of your site, run a free scan at /uk/en/scan.

WCAG is not directly law for UK private sector websites

The Web Content Accessibility Guidelines (WCAG) are produced by the World Wide Web Consortium (W3C). They are a technical specification, not a statute. In the UK's private sector, no legislation requires private businesses to meet WCAG at any specific level.

The Equality Act 2010 requires service providers to make reasonable adjustments for disabled people under sections 20 and 29. What constitutes a reasonable adjustment depends on the facts: the size and resources of the organisation, the cost and practicality of the adjustment, and the nature of the disadvantage caused.

WCAG enters this legal analysis through expert evidence. When a disabled person brings an Equality Act claim about a website, the court will typically hear expert evidence about whether the website met industry standards for accessibility. The standard that experts consistently reference is WCAG, currently at version 2.2, Level AA.

Why courts and the EHRC treat WCAG 2.2 AA as the reasonableness benchmark

Several factors combine to make WCAG 2.2 AA the de facto legal standard.

Government adoption: the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (PSBAR 2018) require public sector bodies to meet WCAG 2.2 AA for websites and publish accessibility statements. When the government adopts a standard for its own digital services, that standard becomes the reference point for what is technically reasonable. A private business cannot easily argue that a requirement the government applies to itself, and funds contractors to implement, is unreasonably burdensome for a commercial operation. This argument has been made in equality law more broadly: where the state has set a standard for its own conduct, the baseline for private respondents is informed by that standard.

International consistency: WCAG 2.2 AA is adopted by the EU Accessibility Act (via EN 301 549), the US Section 508 framework, and equivalent regulations in Australia, Canada and Japan. Its widespread adoption means it reflects international professional consensus on what accessible web development requires.

Measurability: WCAG 2.2 AA provides specific, testable success criteria. This makes it usable in legal proceedings. A court can assess whether a specific criterion was met or not. Vaguer accessibility standards would be harder to apply in litigation.

Expert practice: UK web accessibility auditors routinely frame their reports against WCAG 2.2 AA. A claimant's expert who says "the site fails WCAG 2.2 AA criterion 1.1.1 because product images have no alternative text" is providing specific, refutable evidence. This specificity makes WCAG the natural framework for court proceedings.

Public sector vs private sector: PSBAR 2018 and the Equality Act

The legal situation differs between public and private sector.

For public sector bodies covered by PSBAR 2018 (central and local government, NHS, universities), WCAG 2.2 AA is a legal requirement directly. The Government Digital Service monitors compliance through surveys and spot checks. Non-compliance with PSBAR can lead to formal enforcement action by the Cabinet Office.

For private sector businesses, WCAG 2.2 AA is not a direct legal requirement but is the standard against which reasonable adjustments are assessed. The Equality Act 2010 claim mechanism is the enforcement route, requiring a claimant to bring proceedings.

This distinction matters practically. A public sector body that fails PSBAR can face regulatory action on the regulator's own initiative without a claimant. A private sector business faces enforcement only if a disabled person brings a claim or the EHRC acts strategically. The result is that private sector enforcement is less systematic but the legal obligation under the Equality Act is nonetheless real.

WCAG 2.2 vs 2.1: which version applies

GDS updated the PSBAR technical specification to reference WCAG 2.2 AA following the W3C's publication of WCAG 2.2 in October 2023. Private sector guidance from the EHRC references WCAG 2.2 AA as the current standard.

WCAG 2.2 adds nine new success criteria to WCAG 2.1. The most relevant for typical business websites are:

2.5.8 Target Size (Minimum): interactive targets such as buttons and links must be at least 24x24 CSS pixels. Tightly spaced navigation elements and small call-to-action buttons may fail this criterion.

2.4.11 Focus Not Obscured (Minimum): when a component receives keyboard focus, it must not be completely hidden behind sticky headers, banners or other overlapping content. Sites with persistent navigation bars that cover the focused element fail this criterion.

3.2.6 Consistent Help: if a website provides a help mechanism (phone number, chat, contact page), it must appear in the same location across pages. Inconsistently placed help mechanisms fail this criterion.

Sites that were audited against WCAG 2.1 AA need a supplementary assessment against the new WCAG 2.2 criteria, particularly 2.5.8 and 2.4.11, which frequently reveal failures in otherwise compliant implementations.

Common WCAG failures and their Equality Act implications

Some WCAG 2.2 AA failures are almost always considered failures to make a reasonable adjustment under the Equality Act 2010.

1.1.1 Non-text Content (missing alt text on images): affects screen-reader users with visual impairments. Zero cost to fix with any CMS. Courts would find it unreasonable to have omitted this.

1.3.1 Info and Relationships (form fields without labels): affects screen-reader users and those with cognitive disabilities. Labels are a basic development requirement. No reasonable court would accept that this adjustment was too burdensome.

1.4.3 Contrast (Minimum): affects users with low vision and colour-related visual impairments. Checking and adjusting contrast ratios is a design task with minimal cost, achievable with free tools like the WebAIM Contrast Checker or the browser's built-in DevTools colour picker.

2.1.1 Keyboard (keyboard navigability): affects users who cannot use a mouse, including many with motor disabilities. Making a site keyboard-navigable is a development task, but not a prohibitively expensive one for any commercially operating website, and the EHRC would not accept cost as justification for omitting it from a site that already employs developers.

What a WCAG audit report means in legal proceedings

When an Equality Act claim involving website accessibility reaches court, both parties typically instruct accessibility experts. Each expert produces a report assessing the website against WCAG 2.2 AA and identifying which success criteria are met and which are not.

The court does not simply count failures. It considers whether the failures caused a substantial disadvantage to the claimant, whether the failures were ones that a reasonable organisation of the respondent's size and resources should have addressed, and whether the respondent took any steps to audit or improve accessibility.

A WCAG 2.2 AA audit report from a qualified auditor, showing known failures and a remediation plan, is useful evidence even when the site is not yet fully compliant. It demonstrates awareness and intent. A site with no audit history, or one where the respondent cannot produce any accessibility documentation at all, is in a weaker position because it cannot show that the reasonable adjustments question was ever seriously considered.

Expert witnesses in these cases are typically certified accessibility professionals, often holding qualifications from the International Association of Accessibility Professionals (IAAP). Courts have accepted WCAG-based expert reports as the appropriate technical standard in EA 2010 service-provision cases.

Automated vs manual testing: what each covers

Automated accessibility testing tools, including axe-core (which underlies many commercial scanners), WAVE and Lighthouse, can reliably detect a defined subset of WCAG 2.2 AA issues. Research from Deque suggests automated tools identify around 30 to 57 percent of WCAG issues depending on the tool and the content tested. The issues most reliably detected automatically include missing alt text, insufficient colour contrast, missing form labels, missing document language and certain ARIA misuse patterns.

The issues that require manual testing include keyboard navigation flows, screen-reader behaviour in complex interactive components, the logical reading order of page content, meaningful sequence assessment, and timeout handling. A WCAG 2.2 AA audit that relies solely on automated scanning is not a complete audit.

For legal proceedings, a complete audit conducted by a qualified human auditor is more persuasive than an automated scan report alone. For initial risk assessment and ongoing monitoring, automated scanning covers the most common failures efficiently and cost-effectively. Most organisations use automated scanning continuously and commission manual audits at intervals or before launching significant new content or features.

The accessibility statement template covers how to document known failures and the distinction between automated and manual audit findings.

For the broader legal framework, see website accessibility under the Equality Act 2010. For how EHRC enforcement works, see EHRC investigations of websites.

---

This is technical analysis, not legal advice. Consult a solicitor for specific guidance on WCAG compliance in the context of your Equality Act obligations.