European Accessibility Act, in force since 28 June 2025

Accessibility fixed in your code, not papered over by an overlay.

We scan your site against WCAG 2.2 AA, fix what fails in your own templates and components, and hand you the diff with a before and after re-scan. Our software makes the changes. A person reviews every one before it reaches you.

No card, no script to install. You get a plain English report of what an automated scan found, and a note on what it cannot check.

What a Fix Sprint delivers: a diff of your own code, each change mapped to the WCAG success criterion it addresses, then re-scanned.
The law

The EAA now covers online shops selling to consumers in the EU

Since 28 June 2025 the European Accessibility Act covers e-commerce and other consumer-facing digital services sold in the EU, including by businesses based outside it. Service providers with fewer than 10 staff and an annual turnover or balance sheet total of EUR 2 million or less are exempt.

The European standard behind it, EN 301 549, moved to WCAG 2.2 in version 4.1.1, published in September 2026; until the Commission cites that version in the Official Journal, the cited version is still based on WCAG 2.1. We fix to 2.2 AA, which also covers the 2.1 AA baseline. Enforcement is national: Germany’s BFSG allows fines up to EUR 100,000, and in November 2025 French disability groups took four national retailers to court over inaccessible sites.

The shortcut that failed

Overlay widgets do not fix the code

An overlay is a script that adjusts the page in the browser after it loads. Your templates, components and markup stay exactly as they were.

In 2025 the US Federal Trade Commission fined accessiBe USD 1 million for misrepresenting what its widget does. And 28% of the US digital accessibility lawsuits filed in 2025 named a site that was already running an overlay.

Overlay or code fix

An overlay changes what the browser shows. We change the source.

The difference is where the fix lives, and what is left when someone checks.

Overlay widget compared with a CodeBetter code fix
Overlay widgetCodeBetter
Where the fix livesA JavaScript layer loaded on top of the pageIn your site's own HTML, CSS and components
What a screen reader user getsOften the same barriers, sometimes new ones where the overlay conflicts with their own toolsThe corrected markup, on every page load, with no extra script
Legal exposureNot reduced: 28% of US accessibility lawsuits in 2025 named sites already running an overlayNot eliminated either, but backed by a documented before and after re-scan
Cost over timeA recurring license fee for as long as the script stays onA one time Fix Sprint, plus optional Watch if your site keeps changing
How it works

Scan, fix, then keep it fixed

See the full process
  1. 01

    Free Scan

    Automated checks with axe-core, plus a scripted keyboard and contrast pass, on up to 10 pages. The report lists what a machine can catch and names what it cannot.

    Free

  2. 02

    Fix Sprint

    Our software fixes the issues on a branch of your codebase. A person reviews the changes, then we re-scan and deliver a before and after proof page.

    EUR 1,500 to 3,000, fixed before work starts

  3. 03

    Watch

    New pages and components bring new issues. Watch re-scans monthly, fixes what has regressed, and sends a short report.

    EUR 49 to 149 a month

What you can check

Everything we claim, you can verify

The diff

Every change is a commit in your own repository. You or your developer can read each one before merging.

The re-scan

The proof page shows the issues found, the code that changed, and a fresh scan of the fixed branch. Nothing is marked fixed on our word alone.

The limits

Automated tools find only part of WCAG issues, so a person checks what they cannot, such as whether alt text makes sense. We do not promise legal compliance, because nobody legitimately can. We commit to conformance work against WCAG 2.2 AA, with the evidence attached.

The 30 day regression guarantee. If an issue we fixed comes back within 30 days, we fix it again for free. The conditions

Proof

Real sites, re-scanned after the fix

Read the case studies
  • CogniDeck

    138 issues before, 0 after

    issues, before and after

    Every one of the 15 pages we scanned failed on the same thing: the small grey labels, dates and puzzle numbers were too faint to read. One design-token change plus three targeted fixes took the scan from 138 serious findings to zero, with all 449 existing tests still green.

    How we did it: CogniDeck
  • DesignDeck

    110 issues before, 6 after

    issues, before and after

    DesignDeck sells finished websites you can try live, in an embedded frame. Thirteen marketing pages had no main landmark, the order form's fields showed no visible focus, and three of the showcased designs had unreadable labels. We took the automated findings from 110 to 6 on the same 15 pages and proved the scanner's 'keyboard trap' warnings were not real.

    How we did it: DesignDeck
  • SearchAll

    651 issues before, 0 after

    issues, before and after

    A clean, minimal AI tool directory that failed contrast on every page we scanned. Fixing four colour tokens and three styling patterns at the source took 651 findings to zero across the same 15 pages, without touching the look of the brand.

    How we did it: SearchAll

See what an automated scan finds on your site.

Free, no obligation, and the same scanner that produced the sample report.

Get a free scan