European Accessibility Act: what UK businesses need to know

By Toby · Published April 2026 · Last updated April 2026

The European Accessibility Act (EAA) came into force on 28 June 2025. While it is an EU directive, UK businesses selling to EU customers or with EU operations must comply. The UK's own Equality Act 2010 already requires reasonable adjustments for disabled people, meaning web accessibility is a legal obligation for UK businesses regardless of the EAA.

If you run a website or digital service, the practical standard to aim for is WCAG 2.1 Level AA conformance. This guide explains what the EAA requires, how it interacts with UK law, and gives you a concrete checklist to work from.

What the European Accessibility Act is

The EAA (Directive (EU) 2019/882) is a European Union directive that establishes common accessibility requirements for a range of products and services. For digital businesses, the key requirement is that websites, mobile applications, and e-commerce services must be accessible to people with disabilities.

The directive references the EN 301 549 harmonised standard, which maps directly to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. In practical terms, if your website meets WCAG 2.1 AA, you are meeting the technical standard the EAA requires.

EU member states were required to transpose the EAA into national law by 28 June 2022, with compliance obligations for businesses taking effect from 28 June 2025. This means the law is now actively enforceable across the EU.

Does the EAA apply to UK businesses?

Since Brexit, EU directives do not directly apply in the UK. However, the EAA is still relevant to UK businesses in two important scenarios:

• You sell products or services to EU customers. If your e-commerce site serves customers in any EU member state, the EAA applies to that commercial activity. EU market surveillance authorities can enforce compliance requirements.
• You have operations or subsidiaries in the EU. Any EU-based operation must comply with the national transposition of the EAA in that member state.

Even if you operate entirely within the UK, the Equality Act 2010 already imposes a duty on service providers to make reasonable adjustments to avoid placing disabled people at a substantial disadvantage. Courts and tribunals increasingly treat WCAG 2.1 AA as the benchmark for what constitutes a reasonable adjustment for websites and digital services.

Put simply: web accessibility is a legal requirement for UK businesses under existing domestic law. The EAA adds an additional layer for those trading with the EU.

What WCAG 2.1 AA requires

WCAG is built around four core principles, often remembered by the acronym POUR:

Perceivable

Information and user interface components must be presentable in ways users can perceive. This means providing text alternatives for images, captions for videos, and ensuring content can be presented in different ways without losing meaning. Colour cannot be the sole means of conveying information.

Operable

Users must be able to operate the interface. All functionality must be available via keyboard. Users need enough time to read and use content. Content must not cause seizures or physical reactions. Users need ways to navigate, find content, and determine where they are.

Understandable

Information and the operation of the user interface must be understandable. Text must be readable. Pages must appear and operate in predictable ways. Users must get help avoiding and correcting mistakes in forms.

Robust

Content must be robust enough to be interpreted reliably by a wide variety of user agents, including assistive technologies like screen readers. This means using valid, semantic HTML and following established coding practices.

Key technical requirements

While WCAG 2.1 AA contains dozens of specific success criteria, these are the areas where most websites fall short:

• Alternative text for images. Every informative image needs a descriptive alt attribute. Decorative images should have an empty alt attribute (alt="") so screen readers skip them.
• Keyboard navigation. Every interactive element — links, buttons, form fields, menus — must be reachable and operable using only a keyboard. Focus indicators must be visible.
• Colour contrast. Text must have a contrast ratio of at least 4.5:1 against its background (3:1 for large text). User interface components and graphical objects need at least 3:1 contrast.
• Screen reader compatibility. Use semantic HTML elements (nav, main, header, footer, button) rather than generic divs. Add ARIA attributes only when native HTML is insufficient.
• Form labels. Every form input must have a programmatically associated label. Placeholder text alone is not sufficient. Error messages must clearly identify which field has a problem and how to fix it.
• Skip navigation. Provide a skip-to-main-content link as the first focusable element on each page, allowing keyboard users to bypass repetitive navigation.
• Responsive and reflow. Content must reflow at up to 400% zoom without horizontal scrolling and remain usable at different viewport sizes.

Accessibility statements

The EAA requires organisations to publish an accessibility statement. Even if the EAA does not directly apply to your business, publishing a statement is good practice and demonstrates your commitment to accessibility. Your statement should include:

• The level of WCAG conformance you are targeting (typically 2.1 AA)
• Any known accessibility limitations and the reasons for them
• When your site was last tested and by whom
• Contact details for reporting accessibility problems
• A commitment to resolving reported issues within a reasonable timeframe

The UK Government Digital Service publishes a template for public sector accessibility statements that serves as a useful starting point for private sector businesses as well.

Timeline and deadlines

The EAA compliance deadline of 28 June 2025 has already passed. If your business falls within scope and you have not yet addressed accessibility, you are already overdue. There is a limited transition period for certain existing products and services placed on the market before the deadline, but new digital services must comply from day one.

For UK businesses relying solely on the Equality Act 2010, there is no specific deadline — the duty to make reasonable adjustments is ongoing and has been in force since the Act was passed. The longer you operate an inaccessible website, the greater your legal exposure.

Accessibility compliance checklist

• Run an automated accessibility scan (tools like axe, WAVE, or Lighthouse) to identify obvious issues.
• Test keyboard navigation across your entire site — can you reach every link, button, and form field without a mouse?
• Check colour contrast ratios for all text and interactive elements against WCAG 2.1 AA thresholds.
• Add meaningful alt text to all informative images and empty alt attributes to decorative images.
• Ensure all form inputs have programmatically associated labels (not just placeholder text).
• Add a skip-to-main-content link as the first focusable element on every page.
• Test with a screen reader (VoiceOver on Mac, NVDA on Windows) to verify the reading order and interactive elements work correctly.
• Verify your site reflows properly at 400% browser zoom without horizontal scrolling.
• Check that all videos have captions and all audio content has transcripts.
• Publish an accessibility statement on your website with contact details for reporting issues.

Common mistakes

Relying on an accessibility overlay

Accessibility overlays are third-party widgets that add a toolbar to your site, promising instant compliance. They do not deliver. Overlays cannot fix structural issues in your HTML, they often conflict with real assistive technologies, and they have been the subject of hundreds of legal complaints. The Web Accessibility Initiative, disability advocacy organisations, and accessibility professionals overwhelmingly advise against them. Fix your source code instead. For a detailed analysis, see our accessiBe review.

Ignoring PDFs and documents

Accessibility requirements apply to all content you publish, including downloadable PDFs, Word documents, and spreadsheets. An accessible website that links to inaccessible PDFs still fails to meet the standard. Ensure documents have proper heading structure, alt text, reading order, and tagged content.

Missing skip navigation

Without a skip navigation link, keyboard users must tab through your entire menu on every single page. This is one of the most common and most frustrating accessibility failures. It takes minutes to implement and makes a significant difference.

Poor form labelling

Using placeholder text as the only label for form fields is a persistent problem. Placeholders disappear when a user starts typing, leaving them unable to verify what information goes where. Always use visible, associated label elements.

Assuming automated tools catch everything

Automated accessibility testing tools typically catch only 30-40% of WCAG issues. They are excellent for finding missing alt text, contrast failures, and missing form labels, but they cannot assess whether alt text is actually descriptive, whether the tab order makes sense, or whether custom widgets are usable. Manual testing with a keyboard and screen reader is essential.

Frequently asked questions

Does the EAA apply to UK-only businesses?

The EAA itself is an EU directive and does not directly apply to businesses that only operate within the UK. However, the UK's Equality Act 2010 already requires service providers to make reasonable adjustments for disabled people, and this includes websites and digital services. In practice, meeting WCAG 2.1 AA is the recognised standard for demonstrating compliance with the Equality Act's reasonable adjustment duty. So while the EAA may not apply to your UK-only business, similar obligations already exist under domestic law.

What is the penalty for non-compliance with the EAA?

Penalties vary by EU member state, as each country transposes the EAA into national law with its own enforcement mechanisms. Penalties can include fines, orders to make products or services accessible, and withdrawal of non-compliant products from the market. In the UK context, failing to meet the Equality Act's reasonable adjustment duty can result in legal claims, compensation awards, and reputational damage. There is no fixed maximum fine — damages are assessed case by case.

Do I need to be AAA compliant?

No. The EAA references the EN 301 549 standard, which aligns with WCAG 2.1 Level AA. AAA conformance is not required by the EAA or by the UK Equality Act. WCAG AAA criteria are considered aspirational goals — they include requirements that are very difficult to achieve for all types of content. Focus your efforts on achieving full AA conformance, which covers the most impactful accessibility requirements.

Is an accessibility overlay enough to comply?

No. Accessibility overlays — third-party widgets that add a toolbar to your website — do not fix underlying accessibility issues in your code. They may address a few surface-level problems, but they cannot make an inaccessible website fully compliant with WCAG 2.1 AA. Many overlays introduce new accessibility barriers, conflict with assistive technologies, and have been the subject of legal action. The recommended approach is to fix accessibility issues in your source code, design, and content.

How do I write an accessibility statement?

An accessibility statement should include: the level of WCAG conformance your site aims for (typically 2.1 AA), any known accessibility limitations and the reasons for them, the date of your last accessibility audit, contact information for reporting accessibility issues, and details of your organisation's commitment to accessibility. The UK Government Digital Service provides a template for public sector organisations, which is also a useful reference for private sector businesses. Your statement should be honest about known issues and provide a clear process for users to report problems.