The European Accessibility Act & What It Means for UK Websites
Since the European Accessibility Act took effect, UK businesses have been told variously that it applies to all of them and to none of them. Neither is true. What follows sets out who the act actually catches, where microenterprises stand, which standards are involved, and what UK law requires whether or not the act touches you.
This is general information, not legal advice. Obligations turn on what you sell, where you sell it and how your business is structured. Take your own legal advice before relying on anything here.
What the act is & when it applied
The European Accessibility Act is Directive (EU) 2019/882 of the European Parliament and of the Council of 17 April 2019, on the accessibility requirements for products and services. It was published in the Official Journal on 07 June 2019 and entered into force on 27 June 2019.
The European Commission describes it as a directive that "aims to improve the functioning of the internal market for accessible products and services", and notes that member states were required to bring it into national law by June 2022. The obligations themselves applied from 28 June 2025 under Article 31.
Two points on timing get lost. It is a directive, so what binds a business is the national implementing law of the member state concerned, not the directive text. And Article 31 allows transitional arrangements: service providers may continue using existing products for five further years, and self-service terminals until the end of their economic life, up to twenty years.
Who the act catches
Article 2 sets the scope, and it is a closed list rather than a general duty. On the product side it covers consumer general purpose computer hardware and operating systems, self-service terminals including payment terminals, ATMs, ticketing machines, check-in machines and interactive information screens, consumer terminal equipment used for electronic communications and for accessing audiovisual media services, and e-readers.
On the services side it covers electronic communications services, services providing access to audiovisual media services, elements of air, bus, rail and waterborne passenger transport such as websites, mobile applications, ticketing and real-time travel information, consumer banking services, e-books and dedicated software, e-commerce services, and emergency communications to the 112 number.
Note what is not on that list. A consultancy's brochure site, a manufacturer's product information site, a restaurant's booking page and a charity's donation appeal are not caught simply by existing. E-commerce is caught. A website that only describes a service and does not sell it online is a different question.
Does it apply to a UK business?
The UK is outside the EU, so the directive does not apply to UK businesses through UK law. It can still reach you through the national law of a member state where you offer products or services. Work through these in order.
- Do you offer any of the listed products or services to consumers in an EU member state? If the answer is no, the act is not your concern. Move to the UK duties below.
- Is it a consumer offering rather than business to business? The listed services are framed around consumer use.
- Are you actively targeting an EU market, or merely reachable from one? Currency, language, shipping options and EU-specific terms point to targeting. This is a legal judgement to put to your solicitor.
- Which member state's implementing law applies? The directive sets the floor. National transpositions differ in detail and in enforcement.
- Do you meet the microenterprise definition, and is what you offer a service rather than a product? See the next section.
- Would compliance impose a disproportionate burden or require a fundamental alteration? Article 14 allows this, but on strict terms.
If steps one to three give a clear no, your obligations are the UK ones below.
The microenterprise position
Article 3 defines a microenterprise as "an enterprise which employs fewer than 10 persons and which has an annual turnover not exceeding EUR 2 million" or an annual balance sheet total not exceeding the same figure. Both the headcount and the financial test matter.
Article 4 exempts microenterprises that provide services from complying with the accessibility requirements, on the reasoning that requiring such an assessment of a business that size would itself constitute a disproportionate burden. Read that carefully: the exemption as written concerns services. The position for a microenterprise placing covered products on the market is not the same, and if you manufacture or import any of the listed products you need advice rather than an assumption.
Article 14 is the other relief, and it is narrower than businesses hope. Operators must comply only to the extent that requirements do not impose a disproportionate burden, but they must assess and document that against the criteria in Annex VI and renew it every five years. The directive is explicit that lack of time or knowledge is not a legitimate justification. A disproportionate burden claim is written work, not a shrug.
EN 301 549, WCAG & what compliance means
Article 15 provides that products and services conforming to voluntary harmonised standards receive a presumption of conformity with the accessibility requirements. That is the practical route: meet the standard and you are presumed to meet the law.
The relevant standard is EN 301 549. The European Commission's Accessible EU Centre describes EN 301 549:2021, published on 29 June 2021, as the European standard setting out requirements that ICT products and services "should meet to enable their use by persons with disabilities", and notes it is being updated to support Directive 2019/882.
For web content, EN 301 549 sits on top of the Web Content Accessibility Guidelines. The W3C Web Accessibility Initiative states that EN 301 549 currently references WCAG 2.1, and that "we expect the next version of EN 301 549 to use the latest version of WCAG 2.2".
WCAG is the technical measure everyone ends up working to. W3C published WCAG 2.2 as a Recommendation, current version dated 12 December 2024, adding nine new success criteria including Focus Not Obscured, Dragging Movements, Target Size (Minimum) and Accessible Authentication. It defines three conformance levels: A, AA and AAA. For anyone worried about chasing a moving target, W3C states that "content that conforms to WCAG 2.2 also conforms to WCAG 2.0 and WCAG 2.1". It is also an approved ISO standard, ISO/IEC 40500:2025.
Level AA is what policy tends to require. Build to WCAG 2.2 AA and you satisfy the earlier versions too.
What UK law requires regardless
This is the part most articles skip, and it is the part that applies to nearly every reader.
Section 29 of the Equality Act 2010 provides that a service provider "concerned with the provision of a service to the public or a section of the public (for payment or not) must not discriminate against a person requiring the service by not providing the person with the service", and must not discriminate as to the terms on which the service is provided or subject the person to any other detriment. Subsection 7 applies the duty to make reasonable adjustments to service providers.
Section 20 sets out that duty in three requirements. Where a provision, criterion or practice puts a disabled person at a substantial disadvantage compared with people who are not disabled, the provider must "take such steps as it is reasonable to have to take to avoid the disadvantage". The second requirement concerns physical features, the third auxiliary aids.
The W3C's own summary of UK web accessibility policy lists the Equality Act 2010 as the governing law, covering both public and private sector, with the Equality and Human Rights Commission as the responsible body.
The Equality Act prescribes no technical standard and no certification scheme. It sets a duty framed around reasonableness, which means an inaccessible checkout or an unusable booking form is a risk whether or not any EU directive reaches you. WCAG 2.2 AA is the sensible yardstick, because it is the one everyone else uses.
Public sector duties are separate
If you are a public sector body, or you build for one, a further regime applies. The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018, SI 2018/952, transpose EU Directive 2016/2102. They require public sector bodies to make websites and apps accessible, presume conformity where specified technical standards are met, and require an accessibility statement under Regulation 8.
GOV.UK guidance states that public sector bodies must meet the WCAG 2.2 AA standard and must publish an accessibility statement that "explains how accessible your website or mobile app is", reviewed regularly. It lists exemptions covering pre-2020 audio and video, heritage collections, older PDFs not needed for a service, maps with an accessible alternative, third-party content and archived sites. Enforcement sits with the Equality and Human Rights Commission in England, Scotland and Wales, and the Equality Commission for Northern Ireland, with the Government Digital Service monitoring annually.
GOV.UK's own process is four steps: check for problems, plan the fixes within reason, publish the statement, and keep new features accessible. That sequence works for private sector organisations too.
A remediation priority order
Audits routinely return two hundred issues. Very few businesses can fix two hundred things. Order them by how many users are blocked, not by how many instances the scanner counted.
| Priority | What to fix | Why it comes first | Typical effort |
|---|---|---|---|
| 1 | Keyboard operability and a visible focus indicator | A user who cannot reach a control cannot use the site at all | Medium, often a CSS and component fix |
| 2 | Form labels, error identification and error suggestion | Broken forms block enquiries, checkout and account access | Medium |
| 3 | Text alternatives for meaningful images | Screen reader users lose content and context entirely | Low, but ongoing editorial work |
| 4 | Heading structure and semantic markup | Determines whether a page can be navigated at all assistively | Medium, template level |
| 5 | Colour contrast for text and interface components | Affects a large group, low vision and older users included | Low, design system level |
| 6 | Captions for pre-recorded video | Required at Level A and AA depending on the criterion | Low cost, needs process |
| 7 | Target size and alternatives to dragging | New in WCAG 2.2, common on mobile interfaces | Medium |
| 8 | PDFs and downloadable documents | High volume, often the largest remaining gap | High, consider replacing with HTML |
Fix at template level wherever possible. One correction in a component fixes every page that uses it, which is the difference between a two week job and a two month one.
What to do next
- Answer the scope questions above in writing, then send them to your solicitor for a view. Do not resolve the EU question with a search result.
- Run an automated scan and a manual keyboard test on your five highest traffic pages this week. Automated tools find a minority of issues, so the keyboard test matters.
- Fix the top three priorities in the table at component level rather than page by page.
- Write an accessibility statement, even if you are not legally required to. It records what you have done, what is outstanding and how someone reports a problem.
- Add an accessibility check to your release process so that new work does not reintroduce old failures.
Accessibility work is cheapest when it happens inside the design system and most expensive when it is bolted on after launch. If you are planning a build or a redesign and want WCAG 2.2 AA built in from the first template, our web design team works that way.
Sources
- EUR-Lex, Directive (EU) 2019/882 on the accessibility requirements for products and services
- European Commission, European accessibility act
- European Commission Accessible EU Centre, EN 301 549:2021 Accessibility requirements for ICT products and services
- W3C, Web Content Accessibility Guidelines (WCAG) 2.2
- W3C Web Accessibility Initiative, WCAG 2 Overview
- W3C Web Accessibility Initiative, Web Accessibility Laws and Policies: United Kingdom
- legislation.gov.uk, Equality Act 2010, section 29: Provision of services, etc.
- legislation.gov.uk, Equality Act 2010, section 20: Duty to make adjustments
- legislation.gov.uk, The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018
- GOV.UK, Understanding accessibility requirements for public sector bodies
- GOV.UK, Make your website or app accessible and publish an accessibility statement
