European Accessibility Act: a website checklist for 2026

The European Accessibility Act is now being enforced. What it means for websites on any platform, the WCAG 2.2 update, and a practical checklist.

Crest Design
Accessible website checklist with EU accessibility symbols

The European Accessibility Act (EAA) has applied since 28 June 2025, and in 2026 it has moved from deadline to enforcement. If your website or app sells to consumers in the EU, including from outside the EU, it is likely to be in scope, whichever platform it runs on. National regulators are processing complaints, French courts have issued their first rulings, and the technical standard behind the law was updated in September 2026 to reference WCAG 2.2.

This guide explains what the EAA expects from websites at the time of writing (November 2026), what has changed this year, and a practical checklist for Shopify, WordPress, HubSpot, Webflow, Magento and custom sites. It is general information, not legal advice: speak to a qualified adviser about your own obligations.

Who the EAA applies to

The EAA is an EU directive, so each member state has written it into national law. The European Commission lists e-commerce among the covered services, alongside banking, e-books, passenger transport, telephony and audio-visual media. Legal commentators note that businesses outside the EU are covered when they provide services to EU consumers through e-commerce websites or mobile apps.

There is one important exemption. Ireland's regulator, the CCPC, explains that the requirements do not apply to microenterprises providing services, defined as businesses with fewer than 10 employees and annual turnover or balance sheet not exceeding EUR 2 million. Microenterprises that deal in products are not exempt in the same way. National laws can add their own details, so check the rules in the countries you sell into.

What has changed in 2026

Enforcement has started

Enforcement is handled by national authorities and courts, and much of it so far is driven by complaints from consumers and disability organisations. In June 2026, a court in Caen, France ordered a large grocery retailer to make its online shop and app fully accessible within six months, with daily penalties for delay. Accessibility specialists Deque have also reported regulators in several countries, including the Netherlands, Sweden, Poland and Ireland, planning larger-scale monitoring during 2026.

Penalties are set nationally. The directive requires them to be effective, proportionate and dissuasive, and commentators note they can include fines and, in some countries, removal of non-compliant services.

The technical standard was updated

The standard most closely tied to the EAA is EN 301 549. Version 3.2.1 incorporates WCAG 2.1 Level AA for web content. On 2 September 2026, the European standards organisations published EN 301 549 V4.1.1, which moves to WCAG 2.2 Level A and AA. According to law firm Davis Wright Tremaine, its biggest legal effect comes once it is cited in the Official Journal of the EU, at which point following it gives a presumption of conformity with the EAA.

Building to WCAG 2.2 AA now means you are not chasing a moving target next year.

What the EAA expects from a website

In practice, a covered website should let people with disabilities complete the same journeys as everyone else: finding products, reading information, creating an account, adding to basket and paying. In WCAG terms, that usually means:

  • Keyboard access to every menu, filter, form, modal and checkout step, with a visible focus indicator.
  • Text alternatives for meaningful images, icons and product photos.
  • Sufficient colour contrast for text, buttons and form borders.
  • Labelled forms with clear error messages that explain how to fix the problem.
  • Proper structure: headings in order, landmarks, and meaningful link text.
  • Captions and transcripts for video and audio content.
  • Content that reflows at 400% zoom and on small screens without losing information.
  • WCAG 2.2 additions such as minimum target sizes, focus not being hidden by sticky headers, and accessible authentication that does not depend on memory puzzles.

Service providers also need to publish information explaining how their service meets the accessibility requirements. Article 13 of the directive requires this information to be available in written and oral form and in accessible formats, and it is commonly provided in the terms and conditions or an accessibility statement.

What this means on each platform

No platform makes a site compliant on its own. The platform provides the foundations, while the theme, apps, content and customisations you add decide the result.

Platform Where issues usually come from
Shopify Theme sections, third-party apps (reviews, pop-ups, upsells), image alt text and custom checkout extensions
WordPress and WooCommerce Themes, page builders, plugins and sliders, plus content added by editors
HubSpot CMS Custom modules, embedded forms styling, colour choices in themes and pop-up forms
Webflow Custom interactions and animations, div-based layouts without semantic elements, and missing labels
Magento (Adobe Commerce) Theme templates, layered navigation filters and extension markup
React or Next.js builds Custom components such as dropdowns, carousels and modals that need ARIA and focus management

A practical checklist

  1. 1 Confirm whether you are in scope. Check whether you sell to EU consumers, whether you qualify as a microenterprise, and which countries' laws apply.
  2. 2 Map your key journeys. Homepage, search, category, product, basket, checkout, account and contact.
  3. 3 Run automated checks. Tools such as axe or Lighthouse catch a useful share of issues, including contrast and missing labels.
  4. 4 Test manually. Complete each journey using only a keyboard, then with a screen reader such as NVDA or VoiceOver. Automated tools cannot judge everything.
  5. 5 Audit third-party apps and plugins. Ask vendors for accessibility information and replace components that block key journeys.
  6. 6 Fix in priority order. Start with anything that stops someone completing a purchase or contacting you.
  7. 7 Publish accessibility information. Explain how the service meets the requirements, known limitations and how to report a problem.
  8. 8 Set up a feedback route. Make it easy for users to tell you about barriers, and respond.
  9. 9 Build it into your process. Check accessibility in design reviews, before each release and when adding apps.

Overlay widgets that promise instant compliance are not a substitute for fixing the underlying code and content. Fixes in your theme and templates are what change the experience for users.

Frequently asked questions

Does the EAA apply to businesses outside the EU?

It can. Legal commentary notes that non-EU businesses providing e-commerce services to EU consumers are covered. Take advice on your own situation.

Which WCAG version should we target?

WCAG 2.2 Level AA is the sensible target, as it is referenced in EN 301 549 V4.1.1 and is backwards compatible with WCAG 2.1.

Is a B2B-only website covered?

The EAA focuses on products and services for consumers. If you sell only to businesses, your exposure may be lower, but check with an adviser, especially if consumers can also buy.

Need help making your website accessible?

We audit and fix accessibility issues across Shopify, WordPress, HubSpot, Webflow and custom builds as part of our website design and development services. If your store is on Shopify, our Shopify store launch checklist is a useful companion. To start with an audit of your key journeys, get in touch.

Sources: European Commission: European Accessibility Act, Directive (EU) 2019/882, CCPC: EAA guidelines for microenterprises, Davis Wright Tremaine: EAA ICT standards update, NDA: EN 301 549 published, Deque: One year of the EAA, Deque: French court decision, Seyfarth ADA Title III: EAA and non-EU companies

(over to you)

Planning a build like this?

Tell us what you're building and we'll come back with ideas and next steps.