Website accessibility and the Equality Act 2010
Steven | TrustYourWebsite · 20 April 2026 · Last updated: April 2026
The European Accessibility Act does not apply in the United Kingdom. If you run a UK business selling only to UK consumers, the EAA is not your concern. Website accessibility in the UK is governed by the Equality Act 2010, specifically the anticipatory duty to make reasonable adjustments under sections 20 and 29.
There is an important exception. If your business sells to consumers in the EU, the EAA may still reach you through its provisions on "placing on the market" and "providing services to consumers in the Union". That cross-border exposure is covered at the end of this article.
How does your website score on accessibility?
Our scanner runs an axe-core analysis and reports the most common barriers.
The micro-enterprise position
The EAA exempts micro-enterprises (fewer than 10 employees and annual turnover or balance sheet total below 2 million euro) from its service obligations. The Equality Act 2010 has no equivalent exemption. The duty to make reasonable adjustments applies to all service providers regardless of size. "Reasonable" is assessed in context -- what is reasonable for a sole trader differs from what is reasonable for a large retailer -- but there is no automatic carve-out.
The Equality Act 2010 duty
The Equality Act 2010 imposes a duty on service providers to make reasonable adjustments where a provision, criterion or practice puts a disabled person at a substantial disadvantage compared with persons who are not disabled (s.20). This duty is anticipatory: you must think about the needs of disabled people in advance, not wait for a complaint.
Section 29 makes it unlawful for a service provider to discriminate against a person by not providing the service or by providing it on worse terms. Failing to make a reasonable adjustment is a form of discrimination.
There is no named technical standard in the Act. However, WCAG 2.1 AA (and increasingly WCAG 2.2 AA) is the de facto benchmark used by courts, regulators and industry bodies when assessing whether a website meets the duty. Meeting WCAG 2.1 AA is strong evidence of compliance; failing it is strong evidence of a problem.
Public sector: PSBAR 2018
Public sector bodies in the UK are subject to the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (PSBAR). These regulations require compliance with WCAG 2.2 Level AA (updated from 2.1 in 2024) and are monitored by the GDS (Government Digital Service) / CDDO (Central Digital and Data Office).
PSBAR applies to central and local government, NHS bodies, state-funded schools and universities and other public sector organisations. It does not apply to private sector businesses, but it sets the standard that courts and regulators reference.
Enforcement in the UK
Enforcement of website accessibility under the Equality Act 2010 happens through several channels.
Civil claims in county courts. Any person who believes they have been discriminated against can bring a claim. There is no cap on damages. Cases are typically settled before trial, but the threat of litigation is real. Notable cases include the Royal National Institute of Blind People's campaigns against major retailers.
EHRC strategic enforcement. The Equality and Human Rights Commission can take strategic enforcement action in England, Scotland and Wales. The EHRC has published guidance making clear that websites are covered by the reasonable adjustment duty.
ECNI in Northern Ireland. In Northern Ireland, the Equality Commission for Northern Ireland enforces the Disability Discrimination Act 1995, which still applies alongside the Equality Act 2010 for reserved matters. The anticipatory duty under the DDA 1995 is substantively similar.
There is no dedicated website accessibility regulator in the UK, no mandatory accessibility statement for private sector websites and no administrative fine regime comparable to the EAA. Enforcement relies on individual claims and strategic action by the EHRC.
The technical benchmark: WCAG 2.1 AA and WCAG 2.2
The Equality Act 2010 does not reference a specific standard. In practice, WCAG 2.1 Level AA is the established benchmark. Courts and regulators treat it as the measure of reasonable adjustments for web content.
WCAG 2.2 became ISO/IEC 40500:2025 in October 2025. PSBAR 2018 was updated to require WCAG 2.2 Level AA for public sector bodies. For private sector businesses, WCAG 2.2 AA is the forward-looking standard. Building for WCAG 2.2 AA is sensible, but WCAG 2.1 AA remains the established floor for the reasonable adjustment duty.
What axe-core actually detects
Deque's own coverage study shows that axe-core detects 57.38% of WCAG issues based on a corpus of 13,000 pages with roughly 300,000 issues found. There are no false positives by design. Other estimates (Playwright, WebAIM) suggest 30-40% when you look at success criteria rather than issue volume. The difference is because contrast, alt text and labels are the most common errors, and those are precisely the ones that are automatically detectable.
Reliably detectable: missing or empty alt text, contrast errors, form fields without labels, missing html lang attribute, landmarks, heading structure, ARIA misuse, duplicate IDs, nested interactive elements, link and button names, autocomplete issues.
Requires manual testing: whether alt text is meaningful, logical reading order, keyboard operability of custom widgets, screen reader output, caption quality, cognitive accessibility, contrast against gradients or images, focus management, redundant entry (WCAG 2.2), accessible authentication.
A clean axe-core report is the baseline, not proof that reasonable adjustments have been made. Scanner output is a technical signal, not a compliance verdict.
The 5 most common online shop failures
WebAIM Million 2026 data: 95.9% of the top 1 million homepages have detectable WCAG errors. Average of 56.1 errors per page. Retail and e-commerce sites average roughly 71 errors per page (27% worse than average). Platform averages: Shopify roughly 70, WooCommerce roughly 76, Magento roughly 85.
1. Low-contrast text. 84% of pages, average of 34 instances. Price labels, sale overlays, placeholder text. WCAG 1.4.3.
2. Missing alt text on images. Roughly 53% of pages. Product photos, category tiles. 45% of missing alt text is on linked images. WCAG 1.1.1.
3. Form fields without labels. Roughly 48-51% of pages. Checkout, search bar, newsletter, payment forms. WCAG 1.3.1 / 3.3.2 / 4.1.2.
4. Empty or ambiguous links and buttons. Roughly 45%. "Read more", icon-only basket button. WCAG 2.4.4 / 4.1.2.
5. Skipped headings and broken document structure. Roughly 39%. WCAG 1.3.1 / 2.4.6.
Honourable mention: ARIA misuse. Pages that use ARIA average 57 errors compared with 27 on pages without ARIA.
If you sell to EU consumers: the EAA still reaches you
The EAA applies to services "provided to consumers in the Union". If your UK-based online shop actively targets EU consumers (for example through EU-language versions, EU delivery options or EU-specific pricing), the EAA's service obligations may apply to those transactions. The relevant Member State's supervisory authority can enforce against you for services directed at consumers in their jurisdiction.
This means a UK retailer selling to Irish consumers could face CCPC action, or one selling to French consumers could face DGCCRF action. The micro-enterprise exemption applies in the same way: fewer than 10 FTEs and below 2 million euro turnover or balance sheet total.
If you have any EU-facing trade, treat the EAA as a parallel obligation alongside the Equality Act 2010.
What to do
Start with a WCAG 2.1 AA baseline audit. If you are a public sector body, the requirement is WCAG 2.2 AA under PSBAR. Publish an accessibility statement -- not legally required for private sector, but recommended by the EHRC and increasingly expected by customers. Address the top 5 errors. If you sell to EU consumers, ensure you also meet the EAA's requirements including the CEFR B2 plain-language standard for consumer information.
Accessibility is a commercial reality
Roughly a quarter of consumers have a disability. SEO rewards semantic HTML. B2B procurement increasingly requires accessibility conformity as a supply-chain criterion. Whether the legal driver is the Equality Act 2010 or the EAA, the commercial case is the same.
This article is technical analysis, not legal advice. Consult a solicitor for advice on your specific situation.
Check your website now
Scan your website for Accessibility issues and 30+ other checks.
Scan your site freeWebsite Guides
UK website privacy notice requirements after DUAA (2026)
The 14 mandatory elements of a UK GDPR privacy notice. DUAA 2025 changes, new complaint mechanism, recognised legitimate interests and ICO checklist for SMEs.
Company website trading disclosures in the UK (2026)
Mandatory website disclosures for UK companies. Companies Act 2006 s.82, E-Commerce Regulations 2002 and the s.83 contract enforcement stick.
Cookie banner dark patterns in the UK: ICO enforcement in 2026
The 12 cookie banner dark patterns per EDPB taxonomy. ICO top-100 letter campaign, PECR enforcement and what the scanner detects after clicking reject all.