— A manifesto for real compliance

Widgets don't make a site compliant. We do—by helping you fix the code.

The European Accessibility Act took effect on 28 June 2025. For the first time in the EU, digital accessibility is no longer a best practice: it is a legal obligation, enforceable, with penalties.

In response, vendors are selling accessibility widgets—floating panels promising compliance in one click. The US Federal Trade Commission fined AccessiBe $1 million in April 2025 for exactly that pitch. Independent audits agree: overlays do not create compliance.

We do the opposite. We audit your store's code, map every finding to RGAA 4.1, and show you what to fix, where, and why. You do the work. We give you the means—and the proof.

28 June 2025

The EAA enters application for every new e-commerce store.

$1M

FTC fine against AccessiBe in April 2025 for misleading advertising.

~300,000

Active PrestaShop stores in France—most of them non-compliant.

30–40%

The share of non-conformities an automated audit can detect. The rest still requires human review.

§ 01 · — Why now

The EAA is in force. The first formal complaints landed against Auchan, Carrefour, E. Leclerc and Picard as early as July 2025.

The waiting is over. Sites created or substantially modified after June 2025 must be compliant immediately—no grace period. Legacy sites have until 2030, but that deadline assumes you can show an active remediation effort, not inaction.

In concrete terms: a formal complaint triggers a notice, an investigation by the DGCCRF (or the equivalent authority in your member state), and—if non-compliance is confirmed—fines of up to €250,000 for legal entities (French law of 9 March 2023, transposing EU Directive 2019/882).

These penalties did not exist before 2025. They do now. And experience from other European countries shows that disability rights associations are the first to act on them.

§ 02 · — The problem with overlays

An accessibility widget fixes nothing in your code. It paints a cosmetic layer over the problem.

Accessibility widgets—AccessiBe, UserWay, AudioEye, EqualWeb, and PrestaShop equivalents like PrestaShow or STK Accessibility—all work the same way: client-side JavaScript that tweaks the DOM (contrast, font size, text-to-speech).

Those tweaks never touch the source. Bad markup stays bad. Images without an alt attribute stay without one. Form fields without a label stay without one. The assistive technology used by actual people—screen readers, keyboard navigation, refreshable braille displays—sees the raw site, not the widget.

This is exactly the confusion the FTC sanctioned in April 2025. AccessiBe was selling "ADA compliance in one click" for $49 a month. The investigation found the compliance didn't exist. The federal court ordered a $1 million penalty and an injunction against the claims.

The lesson is simple: there is no shortcut. Accessibility compliance is code work, done by humans, over time. Our job is to make that work visible, prioritized, and measurable.

§ // Our commitment

Widgets don't make a site compliant.

AccessiBe was fined $1 million by the FTC in April 2025 for misleading advertising on exactly this point.

Widget · JS overlay
Code-based audit
Approche
Only changes what the browser displays
Audits and pinpoints issues in the source code
Code conforme
The source code stays non-compliant
Fixes are durable—they live in your templates
Compatibilité réelle
Invisible to real assistive technologies
Compatible with real screen readers
Déclaration valide
Can't produce a valid declaration
Generates your accessibility declaration
Statut juridique
Not enforceable in court
An audit trail that holds up in court
Performance
Weighs pages down—Core Web Vitals suffer
Zero JavaScript injected on the visitor side

Our stance is not neutral: we explicitly reject the overlay model, out of respect for the standards and for the users they're supposed to serve.

§ 03 · — Our approach

Audit the code. Pinpoint the issues. Measure the progress. Produce the proof.

We combine the open-source axe-core engine (the industry reference, maintained by Deque since 2015), a proprietary mapping layer that connects every detection to the 106 official criteria of RGAA 4.1, and a scoring system weighted by legal severity and user impact.

In concrete terms, you get:

  • 01

    A live compliance dashboard

    An "estimated score (automated audit)" headline—honest wording, not over-promised—with its 30-day trend, its monitored regressions, its priorities ordered by legal severity.

  • 02

    Pinpoint accuracy

    On PrestaShop, WooCommerce, Shopify, each finding is traced back to the template, module, or component responsible. On custom sites, you get a precise DOM selector and a screenshot of the element.

  • 03

    A ready-to-sign accessibility declaration

    An RGAA-conforming document generated from your audit, with a dated audit trail. You sign it, you publish it, you're on record. (You remain responsible for the content—we provide the tool, not the attestation.)

  • 04

    A defensible audit history

    Every audit is timestamped and kept. If you ever receive a complaint, you can demonstrate an active remediation effort: successive audits, resolved issues, an upward trend.

— Get started

Five minutes to your first audit.
From €225.

You get the full audit, 30 days of dashboard access, and the accessibility-declaration generator. Continuous monitoring is optional at €14/month — activate it any time, or not at all.