WCAG 2.2 AA in UK law: how it fits Equality Act 2010

The WCAG UK legal baseline is the accessibility standard that courts, the EHRC and expert witnesses use to judge whether a UK website meets the Equality Act 2010's reasonable adjustments duty. That standard is currently WCAG 2.2 Level AA. It is not itself a legal instrument for private sector websites. The Equality Act does not reference it. But its adoption by the UK 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.

<div className="my-6 rounded-lg border border-slate-200 bg-slate-50 p-5"> <div className="mb-2 flex items-center gap-2 text-slate-700 font-semibold"> <svg width="20" height="20" viewBox="0 0 20 20" fill="none" xmlns="http://www.w3.org/2000/svg" aria-hidden="true"> <circle cx="10" cy="10" r="9" stroke="currentColor" strokeWidth="2" /> <path d="M10 6v5M10 13.5v.5" stroke="currentColor" strokeWidth="2" strokeLinecap="round" /> </svg> <span>Quick summary</span> </div> <ul className="list-disc space-y-1 pl-5 text-sm text-slate-800"> <li><strong>What it is:</strong> WCAG 2.2 Level AA, published by the W3C in October 2023.</li> <li><strong>Private sector:</strong> Not direct law. It is the reasonableness benchmark under Equality Act 2010 sections 20 and 29.</li> <li><strong>Public sector:</strong> Directly mandated by PSBAR 2018 (SI 2018/952).</li> <li><strong>Enforcement:</strong> EHRC (private and public sector). Cabinet Office GDS monitors public sector compliance.</li> </ul> </div>

Why this UK legal baseline matters

WCAG enters UK 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. This is the UK legal baseline that informs what counts as a reasonable adjustment.

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. Relevant factors include the size and resources of the organisation, the cost and practicality of the adjustment and the nature of the disadvantage caused.

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. They must 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 is unreasonably burdensome for a commercial operation. 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 direct legal requirement. The Cabinet Office 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. It requires 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 no less real.

<div className="my-6 overflow-x-auto"> <table className="w-full border-collapse text-sm"> <thead> <tr className="bg-slate-100"> <th className="border border-slate-300 p-2 text-left">Aspect</th> <th className="border border-slate-300 p-2 text-left">Public sector (PSBAR 2018)</th> <th className="border border-slate-300 p-2 text-left">Private sector (Equality Act 2010)</th> </tr> </thead> <tbody> <tr> <td className="border border-slate-300 p-2">Statute</td> <td className="border border-slate-300 p-2"><a href="https://www.legislation.gov.uk/uksi/2018/952">SI 2018/952</a></td> <td className="border border-slate-300 p-2"><a href="https://www.legislation.gov.uk/ukpga/2010/15">Equality Act 2010</a> ss.20, 29</td> </tr> <tr> <td className="border border-slate-300 p-2">WCAG status</td> <td className="border border-slate-300 p-2">Mandated by name</td> <td className="border border-slate-300 p-2">Reasonableness benchmark</td> </tr> <tr> <td className="border border-slate-300 p-2">Enforcement initiator</td> <td className="border border-slate-300 p-2">Cabinet Office GDS or EHRC</td> <td className="border border-slate-300 p-2">Disabled claimant or EHRC investigation</td> </tr> <tr> <td className="border border-slate-300 p-2">Accessibility statement</td> <td className="border border-slate-300 p-2">Required</td> <td className="border border-slate-300 p-2">Recommended, not required</td> </tr> <tr> <td className="border border-slate-300 p-2">Remedy</td> <td className="border border-slate-300 p-2">Regulatory action by Cabinet Office</td> <td className="border border-slate-300 p-2">Damages and injunctive orders in county court</td> </tr> </tbody> </table> </div>

WCAG 2.2 vs 2.1: which version applies

The Cabinet Office 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 table below shows the differences most likely to affect a typical business website.

<div className="my-6 overflow-x-auto"> <table className="w-full border-collapse text-sm"> <thead> <tr className="bg-slate-100"> <th className="border border-slate-300 p-2 text-left">Criterion</th> <th className="border border-slate-300 p-2 text-left">2.1 Status</th> <th className="border border-slate-300 p-2 text-left">2.2 Status</th> <th className="border border-slate-300 p-2 text-left">Practical impact</th> </tr> </thead> <tbody> <tr> <td className="border border-slate-300 p-2">2.4.11 Focus Not Obscured (Minimum)</td> <td className="border border-slate-300 p-2">Not present</td> <td className="border border-slate-300 p-2 text-emerald-700 font-semibold">New AA</td> <td className="border border-slate-300 p-2">Sticky headers must not fully hide the focused element</td> </tr> <tr> <td className="border border-slate-300 p-2">2.4.12 Focus Not Obscured (Enhanced)</td> <td className="border border-slate-300 p-2">Not present</td> <td className="border border-slate-300 p-2 text-emerald-700 font-semibold">New AAA</td> <td className="border border-slate-300 p-2">Stronger version of 2.4.11 (no obscuration at all)</td> </tr> <tr> <td className="border border-slate-300 p-2">2.5.7 Dragging Movements</td> <td className="border border-slate-300 p-2">Not present</td> <td className="border border-slate-300 p-2 text-emerald-700 font-semibold">New AA</td> <td className="border border-slate-300 p-2">Drag-and-drop must offer a single-pointer alternative</td> </tr> <tr> <td className="border border-slate-300 p-2">2.5.8 Target Size (Minimum)</td> <td className="border border-slate-300 p-2">Not present</td> <td className="border border-slate-300 p-2 text-emerald-700 font-semibold">New AA</td> <td className="border border-slate-300 p-2">Buttons and links must be at least 24x24 CSS pixels</td> </tr> <tr> <td className="border border-slate-300 p-2">3.2.6 Consistent Help</td> <td className="border border-slate-300 p-2">Not present</td> <td className="border border-slate-300 p-2 text-emerald-700 font-semibold">New A</td> <td className="border border-slate-300 p-2">Help mechanisms must appear in the same location across pages</td> </tr> <tr> <td className="border border-slate-300 p-2">4.1.1 Parsing</td> <td className="border border-slate-300 p-2">Required</td> <td className="border border-slate-300 p-2 text-rose-700 font-semibold">Removed</td> <td className="border border-slate-300 p-2">Modern parsers tolerate the issues this criterion covered</td> </tr> </tbody> </table> </div>

Sites that were audited against WCAG 2.1 AA need a supplementary assessment against the new WCAG 2.2 criteria. The most common new failures appear under 2.5.8 and 2.4.11. These frequently reveal issues in otherwise compliant implementations.

Common WCAG failures and their Equality Act implications

Some WCAG 2.2 AA failures are almost always treated as failures to make a reasonable adjustment under the Equality Act 2010. The table below maps each common failure to its likely Equality Act exposure.

<div className="my-6 overflow-x-auto"> <table className="w-full border-collapse text-sm"> <thead> <tr className="bg-slate-100"> <th className="border border-slate-300 p-2 text-left">WCAG criterion</th> <th className="border border-slate-300 p-2 text-left">User impact</th> <th className="border border-slate-300 p-2 text-left">Equality Act exposure</th> <th className="border border-slate-300 p-2 text-left">Fix difficulty</th> </tr> </thead> <tbody> <tr> <td className="border border-slate-300 p-2">1.1.1 Non-text Content</td> <td className="border border-slate-300 p-2">Screen-reader users cannot perceive images</td> <td className="border border-slate-300 p-2 text-rose-700 font-semibold">High. Zero-cost fix means no reasonableness defence</td> <td className="border border-slate-300 p-2">Low (CMS field)</td> </tr> <tr> <td className="border border-slate-300 p-2">1.3.1 Info and Relationships</td> <td className="border border-slate-300 p-2">Form fields without labels block screen-reader and cognitive-disability users</td> <td className="border border-slate-300 p-2 text-rose-700 font-semibold">High. Basic dev requirement, no plausible burden argument</td> <td className="border border-slate-300 p-2">Low (markup)</td> </tr> <tr> <td className="border border-slate-300 p-2">1.4.3 Contrast (Minimum)</td> <td className="border border-slate-300 p-2">Low-vision and colour-impaired users cannot read text</td> <td className="border border-slate-300 p-2 text-amber-700 font-semibold">Medium-High. Free tools (WebAIM, DevTools) make this trivial to fix</td> <td className="border border-slate-300 p-2">Low (design)</td> </tr> <tr> <td className="border border-slate-300 p-2">2.1.1 Keyboard</td> <td className="border border-slate-300 p-2">Users with motor disabilities cannot operate the site without a mouse</td> <td className="border border-slate-300 p-2 text-rose-700 font-semibold">High. EHRC will not accept cost as justification for an actively developed site</td> <td className="border border-slate-300 p-2">Medium (dev work)</td> </tr> <tr> <td className="border border-slate-300 p-2">2.4.7 Focus Visible</td> <td className="border border-slate-300 p-2">Keyboard users cannot track which element is focused</td> <td className="border border-slate-300 p-2 text-amber-700 font-semibold">Medium-High. Default browser focus styles are free to keep</td> <td className="border border-slate-300 p-2">Low (CSS)</td> </tr> <tr> <td className="border border-slate-300 p-2">2.5.8 Target Size (Minimum)</td> <td className="border border-slate-300 p-2">Motor-impaired users mis-tap closely packed targets</td> <td className="border border-slate-300 p-2 text-amber-700 font-semibold">Medium. Newer criterion. EHRC weight depends on user-base evidence</td> <td className="border border-slate-300 p-2">Low-Medium (CSS)</td> </tr> <tr> <td className="border border-slate-300 p-2">3.3.2 Labels or Instructions</td> <td className="border border-slate-300 p-2">Cognitive-disability users cannot complete forms</td> <td className="border border-slate-300 p-2 text-rose-700 font-semibold">High where forms gate access to a service</td> <td className="border border-slate-300 p-2">Low (copy)</td> </tr> </tbody> </table> </div>

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. They identify 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. It also considers whether the failures were ones that a reasonable organisation of the respondent's size and resources should have addressed. Finally it looks at whether the respondent took any steps to audit or improve accessibility.

A WCAG 2.2 AA audit report from a qualified auditor that shows 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 is in a weaker position. One where the respondent cannot produce any accessibility documentation at all 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). UK courts have accepted WCAG-based expert reports as the appropriate technical standard in EA 2010 service-provision cases.

PSBAR 2018 scope at a glance

PSBAR 2018 binds public sector bodies but exempts certain content categories. The flow below shows how to check whether a particular website or piece of content falls inside scope.

<div className="my-6 rounded-lg border border-slate-200 bg-slate-50 p-5"> <svg width="100%" viewBox="0 0 720 360" xmlns="http://www.w3.org/2000/svg" role="img" aria-labelledby="psbar-flow-title psbar-flow-desc"> <title id="psbar-flow-title">PSBAR 2018 scope decision flow</title> <desc id="psbar-flow-desc">Decision diagram. Step 1: is the body a public sector body under Regulation 2 of PSBAR 2018? No means out of scope. Yes leads to step 2: is the content one of the listed exemptions (pre-2020 audio or video, live media, third-party content, heritage reproductions)? Yes means out of scope. No leads to step 3: is the disproportionate-burden assessment evidenced? Yes means partial exemption with a documented statement. No means in scope and WCAG 2.2 AA conformance required.</desc> <rect x="20" y="20" width="200" height="56" rx="8" fill="#ffffff" stroke="#475569" strokeWidth="1.5" /> <text x="120" y="44" textAnchor="middle" fontSize="13" fontFamily="sans-serif" fill="#0f172a" fontWeight="600">1. Public sector body?</text> <text x="120" y="62" textAnchor="middle" fontSize="11" fontFamily="sans-serif" fill="#334155">PSBAR 2018 Reg. 2</text> <rect x="260" y="20" width="200" height="56" rx="8" fill="#ffffff" stroke="#475569" strokeWidth="1.5" /> <text x="360" y="44" textAnchor="middle" fontSize="13" fontFamily="sans-serif" fill="#0f172a" fontWeight="600">2. Excluded content?</text> <text x="360" y="62" textAnchor="middle" fontSize="11" fontFamily="sans-serif" fill="#334155">Pre-2020 media, maps, third party</text> <rect x="500" y="20" width="200" height="56" rx="8" fill="#ffffff" stroke="#475569" strokeWidth="1.5" /> <text x="600" y="44" textAnchor="middle" fontSize="13" fontFamily="sans-serif" fill="#0f172a" fontWeight="600">3. Disproportionate</text> <text x="600" y="62" textAnchor="middle" fontSize="11" fontFamily="sans-serif" fill="#334155">burden evidenced?</text> <path d="M220 48 L260 48" stroke="#0f172a" strokeWidth="1.5" markerEnd="url(#arrow)" /> <path d="M460 48 L500 48" stroke="#0f172a" strokeWidth="1.5" markerEnd="url(#arrow)" /> <text x="240" y="42" textAnchor="middle" fontSize="11" fontFamily="sans-serif" fill="#0f172a">Yes</text> <text x="480" y="42" textAnchor="middle" fontSize="11" fontFamily="sans-serif" fill="#0f172a">No</text> <rect x="20" y="160" width="200" height="56" rx="8" fill="#fef2f2" stroke="#b91c1c" strokeWidth="1.5" /> <text x="120" y="184" textAnchor="middle" fontSize="13" fontFamily="sans-serif" fill="#7f1d1d" fontWeight="600">Out of scope</text> <text x="120" y="202" textAnchor="middle" fontSize="11" fontFamily="sans-serif" fill="#7f1d1d">Equality Act still applies</text> <path d="M120 76 L120 160" stroke="#b91c1c" strokeWidth="1.5" markerEnd="url(#arrow-red)" /> <text x="100" y="120" textAnchor="middle" fontSize="11" fontFamily="sans-serif" fill="#7f1d1d">No</text> <rect x="260" y="160" width="200" height="56" rx="8" fill="#fef2f2" stroke="#b91c1c" strokeWidth="1.5" /> <text x="360" y="184" textAnchor="middle" fontSize="13" fontFamily="sans-serif" fill="#7f1d1d" fontWeight="600">Content exempt</text> <text x="360" y="202" textAnchor="middle" fontSize="11" fontFamily="sans-serif" fill="#7f1d1d">Document in statement</text> <path d="M360 76 L360 160" stroke="#b91c1c" strokeWidth="1.5" markerEnd="url(#arrow-red)" /> <text x="340" y="120" textAnchor="middle" fontSize="11" fontFamily="sans-serif" fill="#7f1d1d">Yes</text> <rect x="500" y="160" width="200" height="56" rx="8" fill="#ecfdf5" stroke="#047857" strokeWidth="1.5" /> <text x="600" y="184" textAnchor="middle" fontSize="13" fontFamily="sans-serif" fill="#064e3b" fontWeight="600">In scope</text> <text x="600" y="202" textAnchor="middle" fontSize="11" fontFamily="sans-serif" fill="#064e3b">WCAG 2.2 AA required</text> <path d="M600 76 L600 160" stroke="#047857" strokeWidth="1.5" markerEnd="url(#arrow-green)" /> <text x="580" y="120" textAnchor="middle" fontSize="11" fontFamily="sans-serif" fill="#064e3b">No</text> <rect x="260" y="260" width="200" height="56" rx="8" fill="#fffbeb" stroke="#b45309" strokeWidth="1.5" /> <text x="360" y="284" textAnchor="middle" fontSize="13" fontFamily="sans-serif" fill="#78350f" fontWeight="600">Partial exemption</text> <text x="360" y="302" textAnchor="middle" fontSize="11" fontFamily="sans-serif" fill="#78350f">Document assessment</text> <path d="M600 216 L600 280 L460 280" stroke="#b45309" strokeWidth="1.5" markerEnd="url(#arrow-amber)" /> <text x="540" y="270" textAnchor="middle" fontSize="11" fontFamily="sans-serif" fill="#78350f">Yes (evidenced)</text> <defs> <marker id="arrow" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="6" markerHeight="6" orient="auto-start-reverse"> <path d="M0 0 L10 5 L0 10 z" fill="#0f172a" /> </marker> <marker id="arrow-red" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="6" markerHeight="6" orient="auto-start-reverse"> <path d="M0 0 L10 5 L0 10 z" fill="#b91c1c" /> </marker> <marker id="arrow-green" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="6" markerHeight="6" orient="auto-start-reverse"> <path d="M0 0 L10 5 L0 10 z" fill="#047857" /> </marker> <marker id="arrow-amber" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="6" markerHeight="6" orient="auto-start-reverse"> <path d="M0 0 L10 5 L0 10 z" fill="#b45309" /> </marker> </defs> </svg> </div>

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 plus 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 plus 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 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.