EAA in force since 28 June 2025 · German market surveillance begins automated scans in Q3 2026

Prove it. Don't just scan it.

Every WordPress accessibility plugin can tell you what's broken. When a warning letter, a client question or an authority inquiry arrives, what you actually need is an accessibility statement in the form your national law asks for and a dated record of what you found and when you fixed it. A11yGuard is that layer — across every client site you run.

Per-country statements · Update tracking · Exportable audit trail · No overlay, no account, no branding on client sites

Why this is urgent now

The most common complaint isn't contrast. It's the missing statement.

In Germany, the warning letters (Abmahnungen) that started arriving after the BFSG took effect most often cite a missing or incomplete accessibility statement (Anlage 3) rather than a colour-contrast failure. The market surveillance body (MLBF) has said it will scan thousands of shops automatically from Q3 2026. In France, the court in Caen ordered Carrefour to make its site and app fully accessible within six months under a €500/day penalty, rejecting "we are ~71% compliant" as a defence — and E.Leclerc is listed for 22 September 2026 in Créteil, having moved from 32% to 50% conformity after a formal notice.

The statement
Most cited reason in German accessibility warning letters — not contrast, not alt text
Q3 2026
German market surveillance (MLBF) plans automated scanning of thousands of shops
22 Sep 2026
E.Leclerc hearing in Créteil, after Carrefour's "71% compliant" defence was rejected

To be accurate about it: no EU regulator has confirmed an administrative fine under the EAA yet. What is actually landing right now is civil action, warning letters and scan notices — and all three are answered with documents, not with a widget.

The gap

Scanning is solved. Evidence isn't.

Automated WCAG scanning, processing that stays on your own server, and a generic statement generator are table stakes now — several free plugins do all three. The part that is still manual, and the part an agency actually gets asked for, is everything that happens after the scan.

A scan report

  • Tells you what fails today, with no record of what failed last month or who fixed it
  • One generic statement template — usually English — that doesn't match the wording your national law expects
  • Nothing to hand over when a client forwards you a warning letter
  • Per-site, so a portfolio of client sites means opening twenty dashboards

An evidence file

  • Statement text shaped to the national rules (BFSG Anlage 3, RGAA, LPTT, ACM…) in the site's own language
  • Statements tracked for staleness — you're told when a site change or a review deadline makes one out of date
  • Every scan and every fix dated and exportable as PDF/CSV for a client, lawyer or authority
  • One view across every client site you maintain

How it works

Scan → State → Track → Export.

Four steps, inside your WordPress dashboard. The report is written so a client can read it, not just a developer.

Scan

Crawls your live pages and checks every template against WCAG 2.1 AA (EN 301 549) — contrast, alt text, labels, headings, keyboard traps, focus order. Runs on your own server.

State

Generates the accessibility statement in the structure your country's law asks for, in the site's language, filled from real scan results — including the honest "not yet conformant" parts.

Track

Watches for what makes a statement wrong: new content, theme updates, a passed review date. Tells you which client sites need attention before someone else notices.

Export

A dated evidence pack: what was scanned, what failed, what was fixed and when, and which statement version was live at the time. PDF or CSV.

Coverage

Built for the way agencies actually work

Statement wording per country (DE, FR, NL, ES, IT…)
Interface and output in the client's language
Dated scan history for every site
Fix log — what changed, and when
Evidence export as PDF or CSV
One dashboard across a client portfolio
No account required, no upsell shown inside client sites
WCAG 2.1 AA checks incl. WooCommerce checkout & product pages

Founding access

Lock in the launch price before we ship.

A11yGuard is in development — reserving founding access locks your price for life and puts you in the group shaping what ships. It does not give you the product today. Fully refundable, so there is no risk in reserving.

A manual WCAG audit costs €2,000–10,000. Overlay widgets cost €500–2,400/year and add legal risk. A11yGuard Pro is €149/year — and what you get is documentation you own.

Founding member · limited

A11yGuard Pro

€99/year
Regular €149/year
  • Unlimited full-site WCAG 2.1 AA scans
  • Country-specific accessibility statement, generated and kept current
  • Dated scan & fix history, exportable as PDF/CSV
  • AI-written fix suggestion for each issue — reviewed and applied by you
  • Founding price locked for life, including when multi-site agency plans land
Reserve founding access — €99

100% refundable until launch · Secure checkout by Stripe

Not ready to pay yet?

Join the waitlist and we'll email you the free WordPress plugin the day it lands on WordPress.org.

Questions

FAQ

Does a generated statement make my site legally compliant?

No, and nobody's plugin can promise that. A11yGuard produces two things: technical evidence of what was tested and fixed, and a statement drafted to the structure your national law asks for. Whether a specific site meets a specific legal obligation is a legal judgement about your situation. Treat any tool that guarantees compliance with suspicion — that claim is what led to overlay vendor accessiBe being ordered to pay $1M under an FTC settlement in 2025.

Isn't this what an accessibility overlay does?

The opposite. Overlays inject JavaScript that tries to patch a site at runtime and cannot change the underlying HTML that fails WCAG — which is why they show up in lawsuits, and why the German BIK will not test a site that uses one. A11yGuard never injects anything into your visitors' experience. It reads the rendered HTML, tells you what to change, and records what you changed.

How is this different from the scanner plugin I already use?

It probably isn't, on scanning — several plugins detect WCAG issues well and we are not trying to beat them at that. The difference is what happens after: statement wording that matches your country rather than a generic template, notification when a statement goes stale, and an exportable dated trail across a portfolio of client sites. If a scanner is all you need, keep it.

Does the European Accessibility Act apply to my clients?

If a business sells products or services to consumers in the EU — an online shop, booking, banking, many SaaS products — the EAA very likely applies, regardless of where the company is based. Micro-enterprises providing services may be exempt in some cases. The EAA has applied to websites since 28 June 2025; the transition period running to 2030 covers pre-existing service contracts, not live sites.

Where does my site data go?

Scanning is designed to run inside your own WordPress installation, so page content is not shipped to a third-party service to be analysed. AI fix suggestions are the exception — those are generated by a model, using your own API key or the connector built into WordPress core, and only for the specific element being fixed.

Will there be a free version?

Yes — a free plugin on WordPress.org that runs the core scan and a minimal evidence export. Join the waitlist above and we'll email you the moment it's live. Pro adds per-country statements, update tracking, AI fix suggestions and the full export.

What does "refundable until launch" mean?

Reserving founding access charges €99 now and locks your founding price for life (regular price is €149). If we haven't shipped by launch, or you change your mind before then, email us and we refund you in full — no questions.