Budget & ROI

Web accessibility: what does it cost, what does it return

6 min read
Mikhail ShaymardanovWeb Quality and Accessibility Expert

A 60-person small business integrated accessibility into its e-commerce site from the ground up. Total budget over three years: €18,000. Its direct competitor waited. Cease-and-desist letter, emergency audit, fixes under pressure: €85,000. Same sector, same size. Five times more expensive.

Since June 28, 2025, the European Accessibility Act (EAA) has been in force. The first cease-and-desist letters have already been sent. The first court hearings took place in February 2026.

You have four options. Four different budgets. Here are the numbers.

Four scenarios, one calculation to make


#Scenario 1: you do nothing

You decide to ignore accessibility. No audit, no training, no fixes. The site stays as is.

This is the choice still made by 97% of French e-commerce sites, according to Pierre Marragou, president of the ApiDV association.

Here is what this costs over three years for a typical small e-commerce business (50–80 employees, 50–200 page site, one web application):

Estimated costs over 3 years for a small e-commerce business — inaction scenario
ItemEstimated amount
Accessibility investment€0
DGCCRF fines (private sector, EAA)€7,500 per violation, €15,000 on repeat offense
ARCOM fine (online services)Up to €50,000
DGCCRF injunction with daily penalty€3,000/day, up to €300,000
Legal fees (cease-and-desist, defense)€10,000 to €30,000
Loss of disabled customers (12 million people in France)5–15% of online revenue lost
Emergency remediation (express audit and pressure fixes)€40,000 to €80,000
Total 3 years (low end)€75,000
Total 3 years (high end)€450,000+

Why fines accumulate. The DGCCRF may impose €7,500 per violation, €15,000 on repeat offense. Each non-compliant service potentially counts as a separate violation. An e-commerce site with a checkout flow, a customer portal, and a contact form: three services, three possible violations.

The painful daily penalty. Beyond fines, the DGCCRF can issue an injunction with a daily penalty of €3,000, capped at €300,000. One hundred days of delay is enough to hit that cap.

What has already happened. In July 2025, the associations ApiDV, Droit Pluriel, and the Interest to Sue coalition sent cease-and-desist letters to Auchan, Carrefour, E. Leclerc, and Picard Frozen Foods for inaccessible online grocery services. In February 2026, all four companies were in court.

"For blind people who cannot shop alone in a physical store, the Internet represented an opportunity to be independent—provided that sites were accessible. Yet only 3% of e-commerce sites are."

Pierre Marragou, President of the ApiDV association (Le Monde)

These are not small businesses. But the legal mechanism is identical. The associations targeted the leaders to set a precedent. Small businesses will follow.

This is the most expensive scenario.

EAA and web accessibility: what changes for your business in 2026

#Scenario 2: you fix after launch

Your site has been live for six months. Someone mentions the EAA in a meeting. You order an audit. The report lands: 80 non-conformities. The team must return to shipped code, re-test, re-deploy—while building new features in parallel.

This is the path most businesses take. Result: tens of thousands of euros spent fixing what would have cost ten times less at the start.

Estimated costs over 3 years for a small e-commerce business — late correction scenario
ItemEstimated amount
Complete RGAA audit (50–200 page site)€3,000 to €15,000
Post-audit fixes€15,000 to €50,000
Re-testing after fixes (~30% of initial cost)€1,000 to €4,500
Project delay (2–6 weeks of mobilization)€5,000 to €20,000
Residual risk (partial compliance, follow-up audit)Variable
Total 3 years€24,000 to €89,500

Why fixing late costs ten times more. A button without an accessible label takes five minutes to fix during development. After launch, you must find the component in the codebase, understand its context, fix it, verify no regression, re-test across browsers. A minimum of two hours for a single button.

This ratio is not unique to accessibility. The NIST 02-3 report on software defect costs shows a bug found in production can cost up to ten times more than one detected during development. Deque documents it: accessibility debt accumulates exactly like technical debt. The longer you wait, the higher the bill.

"Issue prevention is the best way to save money. Once lawyers become involved, all roads lead to one destination—and it is an expensive one."

Karl Groves, web accessibility expert (karlgroves.com)

The classic trap. You pay €8,000 for an audit. The report lists 80 non-conformities. Your vendor quotes €35,000 for fixes. Unbudgeted sum. The project slips six weeks, and the compliance obtained remains partial: another audit will be needed in a year.

That same budget would have covered everything correctly from the start. It is arithmetic.

Forgotten Accessibility in Specifications: Who Pays the Bill?

#Scenario 3: you build in from the start

Accessibility is in your requirements. Your team is trained and equipped. Errors are caught during development, not after.

This is the only scenario where you don't pay twice.

Estimated costs and gains over 3 years for a small e-commerce business — building in from the start scenario
ItemEstimated amount
Team training (2–3 days)€2,000 to €5,000
Tooling (automated scanning, correction guides)€500 to €3,000/year
Development cost increase+3–5% of dev budget
Validation audit (fewer errors = faster audit)€2,000 to €8,000
Total investment 3 years€8,500 to €23,000

Gains over the same period:

Estimated gains over 3 years — building in from the start scenario
ItemEstimated gain
Fines avoided€7,500 to €45,000
Accessible disability market (12 million people in France)+5–15% of online revenue
SEO gain (organic traffic)+23% on average
Fix cost avoided (vs scenario 2)€15,000 to €66,500
Total gains 3 years€27,500 to €126,500

The market you are missing. 12 million people are affected by digital accessibility in France. Globally, 1.6 billion people live with a disability, with purchasing power estimated at $18 trillion when including their families. That is more than China's GDP—and most sites are closed to them.

The SEO gain. A Semrush study of 10,000 sites shows accessible sites gain on average 23% more organic traffic. Accessibility fixes (heading structure, alt text, form labels) directly improve what Google evaluates.

The cascade effect. 71% of disabled users abandon a hard-to-navigate site. 48% go straight to a competitor. This is not potential loss: it is real loss, every day.

An accessible site keeps these users. It also retains older users, mobile users in difficult conditions, and anyone in a temporary disability situation—broken arm, migraine, noisy environment.

Tools like Includdy let you scan a webpage in five seconds and get detailed correction guides for each identified error, cutting development cost to the minimum.

Accessibility and SEO: How the same fixes boost your Google rankings

#Scenario 4: the "magical" overlay

A salesman promises automatic compliance for €500 per year. You install a JavaScript widget. No code changes. Problem solved.

Except it is not.

Estimated costs over 3 years for a small e-commerce business — overlay scenario
ItemEstimated amount
Overlay subscription (3 years)€1,500 to €6,000
Real compliance achieved~5–10% of criteria
DGCCRF fines (same as scenario 1)€7,500 to €15,000 per violation
DGCCRF injunction with daily penalty€3,000/day, up to €300,000
RGAA audit (still necessary)€3,000 to €15,000
Fixes (still necessary)€15,000 to €50,000
Total 3 years (low end)€76,500
Total 3 years (high end)€456,000+

The overlay adds to the bill. It does not replace it.

Proof in court. In January 2025, the FTC fined accessiBe $1 million for false advertising: the company claimed its overlay made sites compliant. The FTC found this claim false and misleading. Result: the vendor pays, and customers who bought the tool still have to achieve compliance.

The number that matters. According to data compiled by Karl Groves, a significant share of ADA lawsuits in the US target sites already using an overlay. Buying an overlay has never stopped a lawsuit.

Why it does not work. An overlay adds a JavaScript layer on top of your code. It does not touch the HTML structure, does not fix missing labels, does not restructure heading hierarchy. These are exactly the errors that 94.8% of web pages share. Open 20 sites at random, and 19 have them. The overlay fixes nothing at the source.

This is the scenario of triple payment. You pay for the overlay. You pay fines. Then you pay for real compliance.


#All four scenarios side by side

Comparison of 4 accessibility scenarios over 3 years
InactionLate correctionBuild in from startOverlay
Total cost 3 years€75,000 to €450,000+€24,000 to €89,500€8,500 to €23,000€76,500 to €456,000+
Real compliance0%~70–90%~90–100%~5–10%
Legal riskVery highModerateLowVery high
Accessible marketsNoYes (delayed)YesNo
SEO gainNonePartial (delayed)+23% on averageNone (possibly negative)
VerdictMost expensiveExpensive and stressfulMost profitableThe trap

Only one scenario costs less and returns more: building in from the start. The other three cost two to twenty times as much, with no upside.

There is nothing to weigh.


#Where to start with a limited budget

Here is a phased plan, from least to most expensive.

Tier 1: €0, today

Publish your accessibility statement. Until your site is audited, this is a default declaration of non-compliance. The law requires it anyway: failure to publish is itself a sanctionable violation.

Run a first free scan to know your current level. Includdy offers a free express scan that gives you a snapshot in seconds.

Tier 2: ~€100/month, the first month

Move to manual verification of your pages, criterion by criterion. This is where the 70% of problems that automated scans miss live.

Includdy (around €100/month per site) speeds up this step with interactive guides that walk your team step-by-step through verifying each accessibility criterion, without prior expertise.

Prioritize fixing the six error types that account for 96% of detectable issues: insufficient contrast, missing alt text, missing form labels, empty links, empty buttons, undeclared page language.

Tier 3: €2,000 to €5,000, quarter 1

Run a partial RGAA audit (on your 5–10 most-used templates). Prioritize fixes by impact: start with checkout flows and forms. Establish a verification process at each release.

Tier 4: €5,000 to €15,000, year 1

Complete RGAA audit with a certified auditor. Remediate all non-conformities. Establish ongoing monitoring.

Each tier reduces your legal risk. Tier 2 alone eliminates the six error types that account for 96% of detectable issues, for around €1,200 per year.

To identify accessibility errors that free tools miss and get a prioritized remediation plan, try Includdy for free.


Share this article

Frequently asked questions

Does the EAA apply to my business?

If your business has more than 10 employees or more than €2 million in annual revenue and provides digital services to consumers in the EU, yes. Microenterprises (fewer than 10 employees AND less than €2M revenue) benefit from an exemption in the directive. Above these thresholds, the obligation applies regardless of the type of digital service involved.

Must we be 100% compliant or is partial compliance sufficient?

The directive sets no tolerance threshold. Each non-compliant service is potentially subject to sanctions. In practice, enforcement targets the most visible and impactful failures first. A site that is 80% compliant and actively remediating the remaining 20% is in a much better position than a site that did nothing. The realistic objective: aim for 100%, document progress.

Can we achieve compliance without hiring an expert?

Yes, for most of the work. The six most common errors (contrast, alt text, labels, empty links, empty buttons, page language) account for 96% of detectable issues. A trained and equipped developer can fix them. Formal RGAA auditing, however, requires a certified auditor to be defensible.

How long does a typical compliance effort take?

For a small e-commerce business with a 50–200 page site: plan for three to six months by integrating accessibility into existing sprints. In 'catch-up' mode (scenario 2), the same work takes six to twelve months because the team must juggle corrections alongside new features.

Are there financial aids available for accessibility compliance?

No dedicated web accessibility funding exists today. However, general digital transformation programs (France Num, regional grants, employer co-funded training) can cover part of the budget, particularly team training and tooling. Check with your training fund administrator about the training component.