The European Accessibility Act: a design checklist for UK websites selling to the EU
The European Accessibility Act has applied across the EU since 28 June 2025, and it covers e-commerce. For a UK business that sells online to consumers in EU countries, that makes accessibility of the shop, the product pages and the checkout a commercial question as well as a good-practice one. The quickest route to being in good shape is to design to WCAG 2.2 level AA, the current version of the web accessibility guidelines, and to fix the parts of the buying journey where people most often get stuck.
What the Act covers
The European Commission's overview of the Act describes it as a directive to improve the internal market for accessible products and services by replacing differing national rules with common ones. The listed products and services include computers and operating systems, smartphones, ticketing and check-in machines, banking services, e-books, passenger transport services and e-commerce.
Each EU country has put the directive into its own law and appointed authorities to check compliance. In Ireland, for example, the Competition and Consumer Protection Commission announced that it is the compliance authority for e-commerce and e-books, and that it has produced guidance for microenterprises. Very small service businesses can benefit from a limited exemption, but the conditions are specific and some countries expect businesses to notify the authority if they rely on one. If you are unsure whether your EU sales bring you into scope, take advice from a specialist before deciding to do nothing.
Why WCAG 2.2 is the practical target
The W3C published WCAG 2.2 as a web standard on 5 October 2023. According to the W3C's summary of what is new in WCAG 2.2, it adds nine success criteria to WCAG 2.1. Several of them are directly about the kind of interface details designers control, which makes them a sensible starting point for a review.
The checklist, stage by stage
Navigation and product listings
- Visible focus that is not hidden. WCAG 2.2 adds "Focus Not Obscured": when an item receives keyboard focus, it must be at least partly visible. Sticky headers, cookie notices and chat widgets are the usual culprits for covering it.
- Filters without dragging. "Dragging Movements" asks for a simple pointer alternative to any drag action. A price slider needs minimum and maximum fields or buttons alongside it.
- Images with useful alt text. Describe what distinguishes the product (colour, pattern, what is in the box), not "product image".
Product pages
- Tap targets big enough to hit. The new "Target Size (Minimum)" criterion sets a target of at least 24 by 24 CSS pixels, with exceptions such as where smaller targets have enough spacing. Size swatches and quantity steppers often fall short on mobile.
- Contrast for prices and stock messages. Pale grey "only 2 left" text or a light sale price is easy to miss. Our piece on colour contrast and accessible design explains the ratios to check.
- Do not rely on colour alone. An out-of-stock size shown only by a faded colour needs a label or a strike-through too.
Basket and checkout
- No asking twice. "Redundant Entry" says information a user has already given in the same process should be filled in or available to select. The "billing address same as delivery" tick box is the classic example.
- Login without puzzles. "Accessible Authentication (Minimum)" aims to stop sign-in depending on a cognitive test such as remembering or transcribing a code, unless there is an alternative or support such as allowing password managers and paste.
- Help in the same place. "Consistent Help" asks that contact details or help links appear in the same relative position across pages. Do not move the help link on the payment step.
- Errors people can fix. Say what went wrong next to the field and how to correct it, in words, not just a red outline.
Content and copy matter too
Accessibility is not only a front-end job. Plain product descriptions, clear delivery and returns information, and headings that describe what follows all help people using screen readers and anyone reading on a small screen in a hurry. Writers and designers should agree heading structure together rather than treating headings as decoration; we cover that working relationship in why copy and design should be planned together.
How to run a first review in a day
- Pick your three most important journeys, for example: find a product, add to basket, pay.
- Complete each one using only the keyboard. Note anywhere focus disappears or gets trapped.
- Repeat on a phone with the text size turned up in the device settings.
- Run an automated checker on each page and log the issues, accepting that automated tools catch only some problems.
- Ask someone who uses assistive technology to try the journeys if you can, and pay them for their time.
Fix the problems that block a purchase first, then the ones that slow people down.
Do not forget documents and downloads
Product manuals, size guides and returns forms are often uploaded as PDFs that nobody has checked. A scanned page is a picture to a screen reader, and a size chart saved as an image cannot be enlarged without blurring. Where you can, publish this information as an ordinary web page with real headings and tables. If a download is unavoidable, export it from the original document with tags and reading order intact, and test it once with a screen reader before you put it live.
Write down what you did
Keep a short record of what was tested, what was fixed and what is still open, along with an accessibility statement on the site that tells people how to report a problem. It shows good faith, helps the next designer who works on the site, and gives you something concrete to show a partner or authority if anyone asks. For questions about whether and how the law applies to your particular business, an accessibility or legal specialist is the right person to ask.