EN
E-Commerce Nov 19, 2026

European Accessibility Act: What Your Online Store Must Pass

European Accessibility Act: What Your Online Store Must Pass

Time to read: 11 minutes

Content

  1. Does the EAA apply to your store?
  2. What "accessible" means: Annex I, EN 301 549 and WCAG
  3. The journey-by-criterion acceptance sheet
  4. Worked example: one blocker list, three owners
  5. Components you do not control: payment fields, cookie banners, chat and reviews
  6. Automated scans, overlays and manual testing
  7. Prioritize fixes and release them without breaking the theme
  8. Exceptions and edge cases
  9. Keep it accessible: regression checks and published information
  10. Check your result
  11. FAQ
Bookmark

If your online store sells to consumers in the EU and your business is not a microenterprise, the European Accessibility Act applies to it. The Act is Directive (EU) 2019/882. Member States had to apply their national rules from 28 June 2025; in Germany that law is the Barrierefreiheitsstärkungsgesetz (BFSG). What your store must pass is not a scanner score. A customer using only a keyboard, or a screen reader, must be able to search, choose a product variant, use the cart, check out, pay, sign in and request a return. Test those seven journeys against WCAG Level AA, fix whatever stops a purchase first, and retest them in every release.

The Directive covers "e-commerce services" provided to consumers after 28 June 2025 (Article 2(2)) and defines them as "services provided at a distance, through websites and mobile device-based services by electronic means and at the individual request of a consumer with a view to concluding a consumer contract" (Article 3(30)).

This is plain-language guidance, not legal advice. Confirm your obligations, and the national law in each country you sell into, with your counsel.

Does the EAA apply to your store?

Answer four questions in writing.

  1. Do consumers in the EU buy from you? A consumer is a natural person buying "for purposes which are outside his trade, business, craft or profession" (Article 3(22)).
  2. Are you a microenterprise? That is an enterprise "which employs fewer than 10 persons and which has an annual turnover not exceeding EUR 2 million or an annual balance sheet total not exceeding EUR 2 million" (Article 3(23)). Microenterprises providing services are exempt from the service requirements (Article 4(5)), but not from the rules for products the Directive lists, such as consumer computers and e-readers.
  3. Which national law applies? Expect the law of each Member State where you provide the service: the Directive has you inform the authorities "of the Member States in which the service is provided" (Article 13(4)). Confirm with counsel. Germany's BFSG covers e-commerce services provided to consumers after 28 June 2025 (§ 1(3)) and exempts microenterprises providing services (§ 3(3)); its regulation, the BFSGV, sets the e-commerce requirements in § 19.
  4. Do you sell only to businesses? The definition turns on a consumer contract, so a B2B-only shop may fall outside it. Get legal confirmation, especially if consumers can register or check out.

Then write it down in one sentence: "Our German storefront and app are e-commerce services under the BFSG; with 40 staff we are not a microenterprise."

What "accessible" means: Annex I, EN 301 549 and WCAG

Annex I requires websites and apps to be accessible "in a consistent and adequate way by making them perceivable, operable, understandable and robust" (Section III(c)). For e-commerce it adds three requirements (Section IV(g)):

The Directive does not name WCAG. It presumes conformity for services that meet harmonized standards whose references are published in the Official Journal (Article 15(1)). Version 3.2.1 (2021) of the standard EN 301 549, prepared for the public-sector Web Accessibility Directive, treats WCAG 2.1 Level AA as equivalent to its web clauses. Version 4.1.1, published in September 2026 under the Commission's standardization request for the EAA, aligns them with WCAG 2.2; its foreword says the presumption applies once it is cited in the Official Journal under the EAA, so check its status. In practice, test against WCAG 2.2 Level AA: the W3C states that content conforming to WCAG 2.2 also conforms to 2.0 and 2.1.

Which standard to test againstHow the standards connect: the Directive presumes conformity through harmonized standards cited in the Official Journal, EN 301 549 V3.2.1 treats WCAG 2.1 AA as equivalent, V4.1.1 aligns with WCAG 2.2, and in practice you test against WCAG 2.2 Level AA.Which standardto test againstThe Directive, EN 301 549 and WCAGThe Directive does not nameWCAGIt presumes conformity forharmonized standards cited in theOfficial Journal (Article 15(1))EN 301 549 V3.2.1 (2021)Treats WCAG 2.1 Level AA asequivalent to its web clausesEN 301 549 V4.1.1(September 2026)Aligns its web clauses with WCAG2.2; presumption once cited in theOfficial Journal under the EAAIn practice: test againstWCAG 2.2 Level AAThe W3C states that contentconforming to WCAG 2.2 also conformsto 2.0 and 2.1

WCAG's own example shows why you test journeys, not pages: "An online store has a series of pages that are used to select and purchase products. All pages in the series from start to finish (checkout) conform in order for any page that is part of the process to conform."

The journey-by-criterion acceptance sheet

Each row is a journey a customer must finish. The criteria are the WCAG 2.2 Level A and AA success criteria most likely to block that journey (the first two) or degrade it (the third).

JourneyCriteria to check firstHow to testUsual owner
1. Search and filters2.1.1 Keyboard; 4.1.2 Name, Role, Value; 4.1.3 Status MessagesFilter and sort by keyboard; result count announcedTheme, search app
2. Product page and variants2.1.1 Keyboard; 4.1.2 Name, Role, Value; 1.1.1 Non-text ContentSelect each variant by keyboard; selected option announcedTheme
3. Cart4.1.2 Name, Role, Value; 2.4.3 Focus Order; 4.1.3 Status MessagesChange quantity, remove an item, open and close the mini-cartTheme
4. Checkout forms3.3.1 Error Identification; 3.3.2 Labels or Instructions; 3.3.7 Redundant EntrySubmit empty and invalid fields; each error announced at its fieldTheme, checkout app
5. Payment and 3-D Secure2.1.1 Keyboard; 2.1.2 No Keyboard Trap; 2.2.1 Timing AdjustablePay with a test card by keyboard, including the challenge windowPayment provider
6. Sign-in and sign-up3.3.8 Accessible Authentication (Minimum); 3.3.1 Error Identification; 1.3.5 Identify Input PurposeSign in with a password manager; paste a one-time codeTheme, login app
7. Returns request2.1.1 Keyboard; 3.3.2 Labels or Instructions; 1.3.1 Info and RelationshipsStart a return for one item from the order historyReturns app, content team

Check on every page: 1.4.3 Contrast (Minimum), 2.4.7 Focus Visible, 1.4.10 Reflow, 2.4.11 Focus Not Obscured (Minimum) and 2.5.8 Target Size (Minimum). Criteria 2.4.11, 2.5.8, 3.3.7 and 3.3.8 are new in WCAG 2.2. They are not in WCAG 2.1 or EN 301 549 V3.2.1; V4.1.1 includes them but gives a presumption only once cited in the Official Journal.

Add three columns as you test:

Test each journey four ways: keyboard only (Tab, Shift+Tab, Enter, Space, arrows, Escape); with a screen reader, such as NVDA on Windows or VoiceOver on iPhone; at a 320-pixel-wide viewport; and with an automated scan, which cannot pass a journey on its own.

Seven buying journeys and the WCAG criteria most likely to block themSeven journeys in buying order, from search to returns. Each shows two WCAG 2.2 criteria most likely to block the purchase, one most likely to degrade it, and the usual owner of the fix. A bottom band lists five criteria to check on every page.JourneyWCAG 2.2 criteriaUsual owner1 Searchand filters2.1.14.1.24.1.3Theme · search app2 Product pageand variants2.1.14.1.21.1.1Theme3 Cart4.1.22.4.34.1.3Theme4 Checkoutforms3.3.13.3.23.3.7Theme · checkout app5 Payment and3-D Secure2.1.12.1.22.2.1Payment provider6 Sign-inand sign-up3.3.83.3.11.3.5Theme · login app7 Returnsrequest2.1.13.3.21.3.1Returns app · contentEvery page: 1.4.3 · 2.4.7 · 1.4.10 · 2.4.11 · 2.5.8Likely to block purchaseLikely to degradeJourney, in buying orderUsual owner of the fix
The seven journeys in buying order. Solid red chips mark the WCAG 2.2 criteria most likely to block each journey, outlined amber chips the one most likely to degrade it, and the pill names the usual owner of the fix. The bottom band applies to every page.

Worked example: one blocker list, three owners

Fictional, illustrative example. A German direct-to-consumer cookware brand with about 40 staff sells through a Shopware 6 storefront. It is not a microenterprise, so the BFSG applies. Its automated scan is mostly green. Keyboard and screen-reader testing of the seven journeys finds three purchase blockers.

JourneyFindingCriterionSeverityOwnerFix release
2. Product pageColor swatches cannot be reached or selected by keyboard2.1.1Blocks purchaseTheme teamRelease 1
4. Checkout formsErrors shown only as a red border, with no text tied to the field1.4.1, 3.3.1Blocks purchaseCheckout app vendorRelease 1
All, on mobileCookie banner traps keyboard focus2.1.2, 2.4.3Blocks purchaseConsent vendorRelease 1
5. PaymentHosted card fields and challenge window2.1.1, 2.1.2PassPayment providerNone
All22 text and button contrast failures1.4.3DegradesTheme teamRelease 2

Release 1 ships the three blockers, then a keyboard retest of all seven journeys; the contrast fixes follow next sprint.

Components you do not control: payment fields, cookie banners, chat and reviews

The e-commerce requirements name "identification, security and payment" functions, which often come from third parties, as do the consent banner, chat, reviews and search. The Directive excludes "third-party content that is neither funded, developed by, or under the control of, the economic operator concerned" (Article 2(4)(d)), but its Recital 20 adds: "Even if a service, or part of a service, is subcontracted to a third party, the accessibility of that service should not be compromised". A widget you chose, configured and placed in your purchase path is unlikely to count as content outside your control. Ask counsel before relying on that exclusion.

Keep a second tab next to the sheet:

ComponentWhat to testEvidence to request
Payment fields and 3-D Secure challengeLabels, errors and keyboard use inside the frame and challenge windowA written conformance report against WCAG 2.2 AA or EN 301 549, with test date and known exceptions
Cookie or consent bannerCloses by keyboard; never traps or hides focusThe same report, plus focus and wording settings
Chat widgetLauncher name, focus in and out, new messages announcedThe same report
Reviews widgetStar ratings available as text; filters and pagination by keyboardThe same report
Search or merchandising serviceAutocomplete by keyboard; result count announcedThe same report

Log a failing component with the vendor as owner and a fix date, or record a decision to replace it.

Automated scans, overlays and manual testing

The W3C is direct: "no tool alone can determine if a site meets accessibility standards. Knowledgeable human evaluation is required to determine if a site is accessible." Run scans on every build to catch missing labels, alternative text and contrast regressions; they cannot tell you whether a screen-reader user can choose a variant or pay. Failures such as unclear form labels and lost focus also surface in a UX audit of the buying journey.

Overlay widgets that promise automatic compliance add a script on top of your pages; they do not fix the theme, checkout or vendor components that produce the barriers.

Germany's monitoring method also follows the journey: Annex 1 to the BFSG tells the market surveillance authority to check all steps of a service at least in a typical user's standard order, assessing forms, controls, dialogs, error messages and behavior with assistive technologies (our translation); § 28(2) lets the authority check services by sample even without a specific cause.

Prioritize fixes and release them without breaking the theme

Exceptions and edge cases

Keep it accessible: regression checks and published information

Article 13(3) requires procedures that keep the service in conformity as it changes:

Annex V also requires published information, in your general terms and conditions or an equivalent document: "a general description of the service in accessible formats", "descriptions and explanations necessary for the understanding of the operation of the service" and "a description of how the relevant accessibility requirements set out in Annex I are met by the service." Germany's BFSG (Annex 3) adds the competent market surveillance authority, and the information itself must be accessible (Article 13(2)).

Article 13(4) requires corrective measures for a non-conformity and, where the service is not compliant, informing the competent authorities. Penalties are national: Germany's BFSG allows fines of up to EUR 100,000 for offering or providing a service in breach of § 14(1), and up to EUR 10,000 for the other listed offenses (§ 37(2)).

Keep it accessibleFour points for after release: keep the service in conformity under Article 13(3), publish accessibility information under Annex V, take corrective measures under Article 13(4), and note that penalties are national, in Germany set by BFSG § 37(2).Keep it accessibleArticle 13, Annex V and penaltiesKeep the service inconformity: Article 13(3)Top three journeys by keyboard perrelease; full sheet on theme,checkout, payment provider or widgetchangePublish accessibilityinformation: Annex VIn general terms and conditions oran equivalent document, itselfaccessible (Article 13(2))Correct non-conformities:Article 13(4)Corrective measures; where theservice is not compliant, inform thecompetent authoritiesPenalties are nationalGermany's BFSG sets fines in §37(2), the higher cap for a servicein breach of § 14(1)

One limit: this sheet does not prove conformance. It covers the purchase path, not every page or app screen, and does not replace a full EN 301 549 audit or a legal review.

Check your result

You have finished the first pass when you can:

  1. State in one sentence whether your store is in scope and which national law applies.
  2. Complete your top three journeys by keyboard only and with one screen reader, on desktop and mobile.
  3. Show every blocker on the sheet with an owner and a target release, and a vendor evidence request for every third-party component.

If you want to discuss an accessibility review of your buying journey, Dinarys' ecommerce testing and QA team can include the seven journeys in your release testing as agreed scenarios with keyboard input checks, reporting each as passed, failed, blocked or untested.

FAQ

Does the EAA apply if our company is outside the EU?

It can: a service provider includes anyone who "makes offers to provide such a service to consumers in the Union" (Article 3(4)). Confirm with counsel.

Is WCAG 2.1 AA enough, or do we need WCAG 2.2?

Test against WCAG 2.2 AA. EN 301 549 V3.2.1 maps to WCAG 2.1 AA and V4.1.1 to WCAG 2.2, and content that conforms to WCAG 2.2 also conforms to 2.1.

Will an accessibility overlay make our store compliant?

Not on its own. No tool alone can establish conformance; fix the components and test the journeys by hand.

Lassen Sie Profis Ihre Herausforderung meistern

Unsere zertifizierten Spezialisten finden die optimale Lösung für Ihr Unternehmen.

Bitte einen gültigen Namen eingeben
Bitte geben Sie ein gültiges Unternehmen ein
Bitte geben Sie eine gültige Telefonnummer an
Bitte geben Sie eine gültige E-Mail-Adresse ein
Kurze Botschaft

    Ihre Nachricht wurde erfolgreich verschickt. Wir melden uns in Kürze! Success icon