EAA Fines by Country for Ecommerce Non-Compliance: the Per-Day Penalty Explained

If you sell into the EU and your storefront isn't accessible, the question you're probably asking is "what's the fine?" The honest answer is that there isn't a fine. The European Accessibility Act (EAA, Directive 2019/882) doesn't name a number. Article 30 only requires that penalties be "effective, proportionate and dissuasive," and then hands each of the 27 member states the job of setting their own amounts, enforcement bodies and mechanisms. That's why EAA fines by country look so inconsistent — and why a flat "the fine is €X" answer is almost always wrong.

The more useful framing, and the one most owners miss, is this: the EAA non-compliance penalty isn't a single bill that lands once. In most markets it's a drip — a per-day coercive fine that keeps charging until the barrier is removed, layered on top of a headline maximum, and repeatable in every country you trade in. Left alone, that drip quietly outgrows the cost of just fixing the site.

Why "EAA fines by country" is the only honest way to read this

The EAA became enforceable on 28 June 2025. From that date, new products and digital services brought to the EU market — ecommerce included — must meet the accessibility requirements, which in practice means WCAG 2.1 Level AA on the web. But the directive deliberately left the teeth to national law. So when someone publishes a tidy table of "EAA fine amounts 2026," treat it with care: the figures shift depending on which national statute and which violation tier the author is quoting.

Here's what is well-supported across legal and accessibility sources:

• Germany — Under the Barrierefreiheitsstärkungsgesetz (BFSG, §37), fines reach up to €100,000 for non-compliant products and services, with a smaller penalty for failing to provide accurate accessibility information. Crucially, German authorities can also impose Zwangsgeld — a coercive penalty — and order substitute performance to force remediation.
• France — Roughly €50,000 for failing to meet web accessibility standards, with a separate penalty (commonly cited around €25,000) for a missing accessibility statement or multi-year plan. France's regime leans on escalating, repeat-able sanctions rather than a single ceiling.
• Italy — Around €40,000 for operators newly captured by the rules, and up to 5% of annual turnover for organisations already under the older Stanca Act. AGID enforces, typically after a notice period.
• Ireland — Frequently cited at up to €60,000 per violation, and notable for being one of the few regimes that pairs fines with the possibility of imprisonment (reported as up to 18 months on indictment) for deliberate, sustained refusal.
• Spain — A tiered structure by severity. Lower-tier breaches start in the tens of thousands; the most serious bands climb much higher (some sources cite ceilings into six figures). The spread between sources here is exactly why ranges, not single numbers, are the safe read.
• Netherlands, Sweden, Belgium, Finland — Among the higher and more active enforcement regimes, with headline maximums variously reported into the hundreds of thousands of euros, and several offering daily/conditional penalty mechanisms.

We've deliberately given you ranges where the public sources disagree. SOLMONARC won't print a precise "EAA maximum fine country" figure we can't stand behind — the directive's own structure makes a single authoritative table impossible, and anyone who claims otherwise is flattening 27 different statutes into one tidy lie.

The part that actually hurts: the EAA daily penalty per day

Headline maximums grab attention, but they're not usually how the money leaves your account. The mechanism that does the damage is the periodic penalty payment — a fine that recurs for every day (or week) the barrier stays live. Different legal systems have their own name for it: Germany's Zwangsgeld, France's astreinte, Finland's conditional fines. The shape is the same everywhere: comply, and it stops; ignore it, and it compounds.

You don't have to imagine how this plays out. In the closest live example to date, Norway's regulator issued a correction order against a digital service and imposed a compulsory daily fine of 50,000 kroner (roughly €4,300–€5,400) that began running once the deadline passed. That's not a one-time €100,000 ceiling — that's a meter. Run it for two months and the "small" daily figure has quietly overtaken most countries' headline maximums.

This is the editorial point worth sitting with: an accessibility fine for an ecommerce site in the EU is rarely a clean, survivable lump sum you can budget for and move past. It's a leak. And a leak you ignore costs more than the plumber.

Per-country, not per-company: the multiplier nobody priced in

Here's the second compounding factor. The EAA applies wherever you place a product or service on the market. If your store ships to Germany, France and Spain, you're subject to three national regimes — and penalties are cumulative across member states. A French consumer body can act in France while a German authority opens its own case, independently, over the same inaccessible checkout.

So the real exposure isn't "the German maximum." It's the German daily penalty plus the French astreinte plus a Spanish action, each ticking on its own clock, each with its own enforcement body — BAuA in Germany, the Défenseur des droits in France, ACM in the Netherlands, PTS in Sweden, ComReg in Ireland. For a pan-EU Shopify or custom store, the question "what's the EAA penalty?" multiplies by every flag in your shipping settings.

Enforcement is real, and it isn't waiting for 2027

A common bet is "they won't come for a mid-size shop." The early signals since June 2025 cut against that. Within months of the deadline, French disability organisations filed summonses for interim relief against four major grocers — Auchan, Carrefour, E. Leclerc and Picard — over inaccessible digital services. Sweden's PTS opened its first ecommerce compliance inspections. The Netherlands' ACM set reporting deadlines and flagged that non-reporters would be prioritised for audits in 2026. Ireland's ComReg began processing consumer complaints. The Czech Republic signalled it would publish public lists of non-compliant services.

Note the pattern: much of the early action is complaint-driven and reputational, not just financial. A "name-and-shame" list or a court summons does damage long before a euro changes hands — and disabled customers, advocacy groups and competitors are all motivated to file. Several regulators have also signalled they'll prioritise remediation over punishment for operators who can show documented, active fixing. The fine is, in part, a lever to make you move. Which means the smart response is to move first.

The maths that should actually drive your decision

Strip away the country tables and the cost of EAA non-compliance reduces to a simple comparison. On one side: a defined, one-time project to bring your storefront to WCAG 2.1 AA — audit, remediation, an accessibility statement, and a process to keep it from regressing. On the other: an open-ended liability with a daily meter, multiplied across markets, plus legal time, plus the reputational hit of a public complaint.

The fix is finite and predictable. The penalty is neither. That asymmetry is the whole argument. You're not buying down a fine — you're closing a leak before it starts running, and an accessible store also converts better, ranks better, and is usable by the roughly one in four EU adults living with some form of disability. The compliance spend pays rent even if no regulator ever knocks.

What this means for a Shopify or custom storefront

If you're on Shopify, "the platform handles it" is a half-truth. Shopify's checkout has improved, but your theme, your custom sections, your apps and your content are where most failures live — unlabelled buttons, poor colour contrast, keyboard traps in a custom cart drawer, images without alt text, forms a screen reader can't follow. The EAA penalty for a Shopify store attaches to your storefront, not to Shopify Inc. A custom or headless build gives you more control and, with it, more responsibility for getting it right.

An honest path forward is short: get a real audit against WCAG 2.1 AA (automated tooling catches maybe a third of issues — the rest needs human and assistive-tech testing), remediate by severity, publish an accessibility statement, and put a guard-rail in place so the next theme update or new app doesn't quietly reintroduce a barrier. None of that requires panic. It requires a plan and someone who's done it before.

We'll say the unglamorous thing plainly: if your store is small, single-market and already close to compliant, you may not need a build at all — a focused audit and a few fixes could be enough, and we'll tell you if that's the case. The point of understanding EAA fines by country isn't fear. It's to price the leak correctly, then decide with a clear head.