Pavol Rašev
Available for remote contracts from December
Blog

European Accessibility Act for online stores: what changed and what to fix first

If you sell to consumers in the EU and you are not a microenterprise, your store has had to meet the European Accessibility Act since 28 June 2025. In practice that means WCAG 2.1 AA on the whole path from product page to payment, plus a short description of your store's accessibility in your terms. On the store I audited, the first contrast check alone found 32 failures in the cart, the checkout and one category page.

Contrast audit on a real online store Text failing WCAG AA contrast before and after the fix: 15 in the cart, 14 in the checkout and 3 on a category page, 32 in total, down to 0 on each page. The brand grey #77787B had 4.41:1 on white, just under the 4.5:1 minimum; the darker #6F7074 has 4.95:1. European Accessibility Act, online stores First contrast audit on a real store: 32 texts below WCAG AA Cart Checkout Category 15 14 3 0 0 0 failures before and after, one script, same three pages Item price €4.90 #77787B on white · 4.41:1 · below AA Item price €4.90 #6F7074 on white · 4.95:1 · passes AA In force since 28 June 2025 Online stores selling to EU consumers · WCAG 2.1 AA · microenterprises exempt pavolrasev.com

On 8 September 2026 I ran a small script over the cart, the checkout and one category page of Vlnkovo, a yarn store I’m moving to PrestaShop 9. It walks every visible piece of text, works out the colour actually behind it (stacking any semi-transparent layers on the way up the page) and checks the pair against WCAG AA. Thirty-two texts failed: 15 in the cart, 14 in the checkout, 3 on the category page. Eight more were smaller than 13 pixels.

The worst one was the “Edit” link next to finished checkout steps, at 2.30:1. AA asks for 4.5:1. Nobody chose that grey. It came from the parent theme, as .text-muted { color: #ababab !important }, and nobody had looked at it because who reads the Edit link?

That is most of what the European Accessibility Act means for an online store. Not a redesign. A long list of small things that nobody owns. The legal part first, then the list. This is an engineer’s reading of the law, not legal advice.

Does the EAA apply to your store?

The European Accessibility Act, Directive (EU) 2019/882, covers “e-commerce services”: selling at a distance, through a website or an app, “with a view to concluding a consumer contract”. EU countries had to start applying it on 28 June 2025. Three questions decide whether it is your problem.

Do consumers buy from you? A shop where every customer is a business falls outside that definition. If consumers can check out too, you are in.

Do you sell to consumers in an EU country? The national laws are written around the market, not around where the seller sits. The Slovak one, for example, covers anyone who offers the service “to consumers on the market of the Slovak Republic”. A UK or US store selling into the EU should assume it is covered.

Are you a microenterprise? Microenterprises that provide services are exempt (Article 4(5)). The directive defines one as fewer than 10 people and an annual turnover or an annual balance sheet total of no more than €2 million. Most guides only mention turnover; the balance sheet route is in the text too. Germany’s BFSG (§ 3(3)) and Slovakia’s Act 351/2022 (§ 2(3)) carry the same exemption.

I would still fix the checkout on an exempt store. The exemption keeps the inspector away. It does not bring back the customer who could not tick the terms checkbox.

What the law actually asks for

Annex I of the directive says websites must be “perceivable, operable, understandable and robust”. Those are the four principles of WCAG, and the yardstick in practice is the European standard EN 301 549, which for websites points to WCAG 2.1 level AA. For online stores the annex adds two things: show the accessibility information about the products you sell when the manufacturer provides it, and make identification, security and payment accessible.

One version note, checked again on 2 November 2026. ETSI published EN 301 549 v4.1.1 in September 2026, and it moves the web requirements to WCAG 2.2. According to the Commission’s AccessibleEU centre, the new version is not yet the legal reference: until the Commission cites it in the Official Journal, that stays v3.2.1 with WCAG 2.1 AA. The citation is expected around the end of 2026, but the Commission hasn’t set a date. For new work I’d build to 2.2 anyway. It adds six criteria at levels A and AA, and several of them land right in a checkout: big enough click targets, focus that a sticky header doesn’t hide, not asking for the same details twice, and logins without memory puzzles.

The part most stores miss is not technical. Annex V says the service provider has to describe how the service meets the requirements “in the general terms and conditions, or equivalent document”: a general description of the service in accessible formats, what a user needs to know to operate it, and how the requirements are met. That is not the same thing as the accessibility statement public sector websites publish, although that template is a fine starting point. Slovakia copied the requirement almost word for word into § 6(2) of its law.

The 2030 date is probably not yours

Article 32 has two transitional rules. Services may keep using products that were lawfully used to provide them before 28 June 2025 until 28 June 2030, and service contracts signed before 28 June 2025 may run on unchanged until they expire, for at most five years. Some guides read this as five extra years for existing websites. I don’t. The first rule is about things like terminals you already use to deliver the service, the second about contracts such as an existing subscription. A storefront that takes new orders every day is neither. Slovakia did not even take over the products part: § 12 of its law only mentions contracts. If you plan to rely on 2030, ask a lawyer first.

Who checks, and what it costs

Country Law Who checks Fines for the store
Slovakia Act 351/2022 Coll., in force since 28 June 2025, amended twice (current version from 30 May 2026) Slovak Trade Inspection (SOI), also on consumer complaints €200 up to 3% of last year’s turnover, capped at €6,000 for an inaccessible service or missing information, €20,000 for missing procedures or corrective action, €30,000 for not cooperating. For an inaccessible service or missing procedures, SOI has to drop the fine if you take corrective action.
Germany Barrierefreiheitsstärkungsgesetz (BFSG) MLBF in Magdeburg, a joint authority of the 16 states, working since September 2025. In June 2026 it was handling about 700 reports. Up to €100,000 for offering an inaccessible service (§ 37), up to €10,000 for most information failures

One of the top-ranking guides for this topic quotes €500,000 for Germany. The BFSG says €100,000. Every other EU country has its own law and its own authority, so check the one for each market you sell into.

What failed on a real store

Back to Vlnkovo. These are the eight worst contrast results from that first run, before any fix:

Contrast What Where the colour came from
2.30:1 “Edit” next to finished checkout steps parent theme, .text-muted #ababab !important
2.32:1 “(2 × €0.90)” in the mini cart and order summary parent theme, #aaa at 12.8 px
2.75:1 “Last items in stock” on product cards #d98b0e
2.85:1 checkout steps not reached yet, such as “4. Payment” #999
2.99:1 “In stock” on product cards #2faa5e
3.11:1 footer copyright a page builder element, #929292
4.29:1 opening hours in the header the page builder’s global text colour, #7a7a7a
4.41:1 item price, address, delivery time, payment description our own brand grey, #77787B

The last row is the one that hurt, because it was ours. The brand palette’s grey sat just under AA, and it carried almost every small label in the cart and the checkout. One change fixed about ten places at once:

:root {
  /* The raw brand grey was 4.41:1 on white, just under AA,
     and it carries most small text in the cart and checkout. */
  --vlnkovo-grey: #6F7074; /* was #77787B, now 4.95:1 */
}

The stock labels got darker shades that still read as green and amber (#238247 at 4.82:1, #9C6207 at 5.04:1). The header and footer come from a page builder, so I overrode them with an ID selector in CSS, but the real fix is to change the colours inside the builder. CSS is only a floor there. Breadcrumbs, the cart counter and a few buttons went up to at least 13 px. After the changes I ran the same script on the same three pages: 0, 0 and 0, and nothing under 13 px.

The audit was about contrast, but the weeks around it turned up other accessibility bugs, none of them from a checklist. I found them because something felt off or a click didn’t work:

  • Text typed into a form field turned light grey while you typed, because the theme set .form-control:focus { color: #acaaa6 }. The value was hardest to read exactly when the customer was checking it.
  • The checkbox frames were 20×20 px, but the real input under them was the browser’s 13×13. Clicking most of the frame did nothing. Two checkboxes on the address step, “Use this address for invoices too” and “I’m buying as a business”, had a <label> without a for, so clicking their text did nothing either.
  • Placeholders in this theme carry the field’s name, so they have to pass contrast like normal text. (Better still is a visible label that does not vanish the moment you start typing.)
  • To fit the product card, the “Add to cart” button became an icon. The words stayed in the markup, in a visually hidden span, so a screen reader still says “Add to cart”.
  • A sold-out product showed a disabled quantity stepper and button that still looked clickable. Now it shows a sentence saying the product is sold out.

While writing this I searched the theme for outline: none. Most hits replace the outline with a coloured ring. The quantity field on product cards does not get its own: it removes the outline and is left with the site-wide focus style for inputs, a soft ring in the brand purple at 12% opacity. The stepper around it has overflow: hidden, so most of that ring got cut off. The field now gets its own 3 px ring in the brand colour, drawn inside the field, so the stepper can’t cut it off.

All of this came from the contrast script, from using the store and from reading its CSS. None of it comes from a screen reader test.

All of this was found and fixed on the new store before launch. The live shop still runs on the old platform until the switch.

How to test it yourself

You don’t need a paid tool to find most of this. Four passes, in this order:

  1. An automated check. The free axe DevTools extension or the Lighthouse accessibility audit in Chrome. Run it on the home page, a category, a product with variants, the cart, every checkout step, login and the order confirmation. It catches missing labels, missing alt text and a lot of contrast. It cannot judge contrast on top of images or semi-transparent layers; axe lists those under “needs review”, and on Vlnkovo that is exactly where the theme’s leftovers were hiding.
  2. Keyboard only. Put the mouse away and buy something. You should always see where you are, reach every control, and get in and out of the cookie banner, the variant picker and the pickup point map. Third-party widgets deserve the most suspicion, because you don’t control their markup.
  3. A screen reader. VoiceOver is built into every Mac (Cmd+F5), NVDA is free on Windows. Listen to a product page: is the price read out, are the variants named, does “Add to cart” say what it does? Then submit a form with a mistake and listen for the error.
  4. Zoom: 200% and a 320 px wide window. Nothing should overlap or need scrolling sideways.

What to fix first

In the order I would do it on a store that has never been checked:

  1. The checkout, end to end, by keyboard. Shipping, pickup point, payment, the terms checkbox, the order button. If someone cannot pay, nothing else matters, and payment is named in the law.
  2. Form labels and errors. Every field has a visible label tied to its input with for and id. Errors say in words what is wrong, next to the field, not only as a red border.
  3. Contrast, starting from your variables: 4.5:1 for normal text, 3:1 for large text and for things like input borders and focus rings. Fix the design tokens first, then hunt the colours inherited from the theme and the page builder.
  4. Visible focus everywhere. Search your CSS for outline: none and check that each one has a replacement.
  5. Names for images and icons: alt text on product photos that says what the name doesn’t (the colour, the texture), names on icon-only buttons, and colour variants named in text, not only as swatches.
  6. Product accessibility information from the manufacturer, when you have it.
  7. The accessibility section in your terms, as Annex V describes it.
  8. A habit, not a project. Rerun the four passes after every theme or module update. The laws ask for procedures that keep the service compliant when it changes, and a theme update is exactly how #ababab !important comes back.

If something really cannot be made accessible without an unreasonable cost, the directive lets you claim a disproportionate burden, but only with a written assessment that you keep for five years (Article 14). I would not count on it for a checkout. I also would not buy an overlay widget: it adds a toolbar on top and leaves the markup underneath exactly as it was.

A new store is the cheap case: setting the colour tokens and form patterns right on day one costs almost nothing compared with hunting 32 values later, so it belongs in the brief when you have a store built.

Sources