Honest answers, including the ones that do not sell anything

Often, if you sell to consumers in the EU, but this is general information, not legal advice about your business. Since 28 June 2025 the EAA covers e-commerce and other consumer-facing digital services sold in the EU, and that includes sellers based outside the EU. The exemption is narrow: a service provider with fewer than 10 staff and an annual turnover or balance sheet of EUR 2 million or less. Both conditions have to be true.

Business-to-business only sites, and content that is not part of a consumer service, can fall outside it. If you are unsure, ask a lawyer in your main market; we can tell you what fails, not whether a regulator will act.

Enforcement is national, so it depends on the country. Germany’s BFSG allows fines up to EUR 100,000 and orders to fix or withdraw a service. In France, disability associations took four national retailers (Auchan, Carrefour, E.Leclerc and Picard) to court in November 2025 after their sites stayed inaccessible past a deadline they had been given. Most action so far has started with a complaint. What a regulator or court would do in your case is a question for a lawyer in your market.

WCAG 2.2 level AA. The European standard behind the EAA, EN 301 549, is currently cited in its version 3.2.1, which is based on WCAG 2.1 AA, and its next version moves to WCAG 2.2. Fixing to 2.2 AA covers both.

No, and nobody legitimately can. Whether a site complies with the EAA is decided by national regulators and courts, each member state enforces it differently, and no automated or manual audit can prove the absence of every barrier. What we guarantee is the work: conformance fixes against WCAG 2.2 AA for the issues in the agreed scope, a human review of every change, and a before and after re-scan as evidence. If the re-scan still shows an in-scope failure, we fix it at no extra charge, and the 30 day regression guarantee covers anything we fixed that comes back.

An overlay is a script that runs on top of your page after it loads; your code stays as it was. 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. Overlays also cost around USD 490 a year or more, every year, for as long as the script stays on. A fix that holds up has to live in your site’s own HTML, CSS and components, which is what a Fix Sprint changes, once.

A branch (or pull request) with the in-scope issues fixed in your own codebase, a human accessibility review of those changes, and a before and after proof page built from a fresh re-scan. You or your developer review and merge it.

By size. Small (up to 15 unique templates) is EUR 1,500, Medium (up to 50 templates, or a standard shop) is EUR 2,200, Large (up to 120 templates, custom checkout or app-like flows) is EUR 3,000. A template is a unique page layout, so 4,000 products on one product template count once. The free scan tells you which size you are, we confirm it before work starts, and the price does not change after that.

If an issue we fixed comes back within 30 days, we fix it again for free.

• Covers every issue listed as fixed on your proof page, whatever caused it to come back.
• Runs for 30 days from the day we deliver the branch, once you have merged it.
• Tell us by email; we re-fix on a new branch within 5 working days.
• Does not cover new pages or components added after delivery (that is what Watch is for), or third party code we have no access to.

No. We are not a law firm, we do not give legal advice, and to the extent the law allows, our liability is capped at what you paid for the service (see the Terms). What you do get is a record: a dated scan before, the code changes, and a dated re-scan after. It shows what was fixed and when, and you or your lawyer can use it when answering a complaint. Whether it is enough in a given case is for your lawyer, the regulator or a court to judge.

Prices are in EUR and exclude VAT. Online orders go through Paddle.com, our merchant of record: it charges the right VAT for your country, applies the reverse charge if you give a valid EU VAT ID, and sends the invoice. Until online checkout opens, booking is by email and we invoice you directly.

That is what Watch is for. New pages, new components and redesigns bring new issues. Watch re-scans monthly, fixes what has regressed since the last clean baseline, and sends a short report. It is optional, and starts only after a Fix Sprint has set that baseline.

Yes, any time. It runs month to month with no long term contract; cancel and the current billing period simply runs out.

Yes, as long as we can access the source: theme files, templates, or a git repository. That covers WordPress and Shopify themes, Next.js, Astro and plain HTML. If your platform locks the markup (some hosted builders do), the free scan report will say which issues we cannot reach.

Full refund if work has not started. Once a Fix Sprint is underway you pay for the agreed scope; if the delivered branch does not match that scope, we fix it at no extra charge. Watch is billed monthly in advance and a started month is not refunded, but you can cancel before the next one at any time. Full terms are on the Terms page.

Our remediation software, built on coding agents, makes the changes. A human accessibility reviewer checks every Fix Sprint before delivery, specifically for what a script cannot judge: whether alt text is meaningful, whether an ARIA role fits the widget it is on. Nothing is delivered without that review, and you get the full diff to read yourself.

No. We work in a copy of your codebase or a branch you give us access to. We never change production, and we deploy nothing on your behalf unless you ask us to in writing.

Typically 5 to 10 working days from confirmed scope and access, depending on site size.

It catches the mechanical issues a script can verify: missing labels and alt attributes, contrast ratios, focus visibility and some keyboard traps. Published estimates of how much of WCAG that covers range from about a third to about half, depending on how issues are counted. It cannot judge whether alt text makes sense, whether reading order works for a screen reader user, or how the page behaves with a person using assistive technology. The sample report shows what a real scan returns.