Skip to main content

European Accessibility Act checklist for websites and online shops

By the Quick Brains team · Updated

The European Accessibility Act (EAA) has applied since 28 June 2025. It requires many digital services sold to EU consumers, including online shops, to be usable by people with disabilities. For a full review with fixes, see our accessibility audit.

This guide is general information, not legal advice. Check your specific obligations with a lawyer.

Does the European Accessibility Act apply to you?

Work through these questions:

  • Do you sell to consumers in the EU? The EAA covers business-to-consumer products and services. It applies to companies outside the EU too, if they serve EU consumers.
  • Is your service on the list? For digital services, the main categories are e-commerce, consumer banking, e-books, electronic communications, and passenger transport by air, bus, rail and water (websites, apps, ticketing and travel information).
  • Are you a microenterprise? Service providers with fewer than 10 employees and no more than €2 million in annual turnover or balance sheet total are exempt from the service requirements.

If you answered yes, yes and no, the EAA very likely applies to your website and app.

Transition rules apply to some existing products and contracts, and in rare cases a company can claim that a requirement would be a disproportionate burden. Both need careful documentation, and neither is a general exemption.

What “accessible” means under the EAA

The EAA sets out functional requirements, and in practice conformity is shown against the harmonised standard EN 301 549. For web content, EN 301 549 incorporates the success criteria of the Web Content Accessibility Guidelines (WCAG) at level AA.

The current version of WCAG is 2.2. Meeting WCAG 2.2 AA covers everything in 2.1 AA and adds several criteria that matter for real users, so it is the sensible target.

The checklist

Keyboard and focus

  • Every interactive element (links, buttons, menus, form fields, modals) works with the keyboard alone
  • Focus is always visible, with a clear outline you can see on every background
  • Focus order follows the visual order of the page
  • Nothing traps keyboard focus: you can always tab out of menus, modals and embedded widgets
  • Sticky headers, cookie banners and chat widgets never cover the focused element
  • A “skip to main content” link is available at the top of each page

Screen readers and page structure

  • Each page has one H1 and a logical heading structure
  • Landmarks are used: header, navigation, main and footer
  • Images have meaningful alt text, and decorative images have empty alt text
  • Icon-only buttons (search, cart, close, menu) have accessible names
  • Custom components (dropdowns, tabs, accordions) announce their state, such as expanded or selected
  • The page language is set

Forms, errors and checkout

  • Every form field has a visible label that is programmatically linked to it
  • Required fields are indicated in text, not only by colour or an asterisk
  • Error messages explain what went wrong and how to fix it, and are announced to screen readers
  • Users aren’t asked for the same information twice in one process (WCAG 2.2)
  • Logging in doesn’t rely on memory or puzzle tests without an alternative, and password managers and pasting work (WCAG 2.2)
  • The full checkout, including payment and confirmation, can be completed with a keyboard and a screen reader

Visual design

  • Body text has a contrast ratio of at least 4.5:1, and large text at least 3:1
  • Form field borders, focus indicators and icons have a contrast ratio of at least 3:1
  • Colour is never the only way information is conveyed (for example, errors shown only in red)
  • The page works at 200% zoom, and content reflows without horizontal scrolling at 320 CSS pixels wide
  • Touch targets are at least 24 by 24 CSS pixels, or have enough space around them (WCAG 2.2)

Media and motion

  • Videos have captions, and audio-only content has a transcript
  • Nothing auto-plays for more than five seconds without a way to pause it
  • Animations respect the reduced-motion setting in the user’s operating system
  • Anything done by dragging, such as sliders or reordering, has a single-click or tap alternative (WCAG 2.2)

Help and consistency

  • Help options, such as contact details or a chat link, appear in the same place on every page (WCAG 2.2)
  • Navigation is consistent across pages

Documentation

  • You publish information on how your service meets the accessibility requirements, usually as an accessibility statement
  • The statement lists known limitations and gives users a way to report problems
  • Someone in your company owns accessibility and reviews new features before release

What happens if you don’t comply

Each EU member state enforces the EAA through its own national authorities and sets its own penalties, so consequences vary by country. Beyond fines, the practical risks are complaints, orders to fix specific problems, and losing customers who simply can’t use your site. In the US, website accessibility lawsuits under the ADA are common, with WCAG as the usual reference.

How to prioritize fixes

You won’t fix everything at once. A sensible order:

  1. Revenue-critical flows first: checkout, signup, login and contact forms. A barrier here stops people completing the task entirely.
  2. Shared components second: header, navigation, footer and design-system components. One fix improves every page.
  3. Templates third: product pages, listing pages and articles.
  4. Content last: alt text, link text and headings in individual pages, ideally with a process so new content gets them right.

Then keep it fixed. Add automated accessibility checks to your CI so new issues are caught before release, and include a keyboard test in your definition of done.

Automated tools are only the start

Free tools such as axe DevTools, WAVE and Lighthouse catch many issues quickly, and you should use them. But they can’t judge whether alt text makes sense, whether focus order is logical, or whether a screen reader user can actually finish checkout. That takes manual testing with a keyboard and a screen reader.

If you’d like that done for you, our accessibility audit tests your site against WCAG 2.2 AA, fixes the issues in your code, re-tests, and drafts your accessibility statement.

Want this done for you?

Our accessibility audit tests your website or web app against WCAG 2.2 level AA and EN 301 549, the standard behind the European Accessibility Act. After the audit, we fix the issues in your code or give your developers a precise fix guide, then re-test and draft your accessibility statement.