What I found, and why I'm not building this.
For two weeks I asked WordPress agencies in Germany, France and the Netherlands one question: how do you keep a client's accessibility statement true after the site changes? This page is what they told me. It is also the answer I owe the people who replied.
What I was going to build
A WordPress plugin for agencies: generate the accessibility statement in the shape each country's law expects, notice when a site change makes it stale, and keep an exportable record of what was scanned and fixed. The pitch wrote itself — the EAA has applied since June 2025, and nobody seemed to own the part that comes after the audit.
Before writing any code I asked practitioners instead. Six agencies by email, and one public thread in the German WordPress forum. That was enough.
What they told me
1. The hard part of a statement cannot be generated
A German agency developer put it more clearly than any vendor page I had read:
"Generator yes, but only for the scaffolding. The substantive core of the statement is the list of points that are not conformant, with reasons, and a generator cannot know that — it comes out of an audit."
Free generators already exist for the scaffolding. What is left is the audit, and the audit is people.
2. The agency that needs it most has already built it
The same developer described their setup: a monthly automated check across client sites, the report filed, the date in the statement taken from that run, and any markup change — new template, new plugin, theme update — triggering an extra check. That is the product I was sketching, assembled from free tools and a deploy hook by someone who needed it.
3. Below the legal threshold, nobody is interested
The BFSG does not apply to pure B2B offerings, to micro-enterprises in services (under 10 employees and at most €2M turnover or balance sheet), or to non-commercial sites. One agency owner said the question is not who wants accessibility but who is legally obliged — and that his clients, freelancers and small firms, fall outside it. He asks them anyway. Most are not interested.
4. Above the threshold, the request never comes
A large French agency — the kind whose clients are squarely covered by the rules — told me by email that nothing at all triggers an update to a statement when a site changes, that the tracking lives in one spreadsheet per project and only during the audit, and that in ten years they have never once had a client ask about any of it.
That is the sentence that ended the project. The gap is real. Nobody is asking for it to be filled.
Two things I had wrong
I repeated both of these in my own posts. Practitioners with better sources corrected me, and the correction belongs in public, not only in my notes.
"Most German warning letters are about a missing statement"
I had this from trade press, not from a primary source. A German developer pointed out that the BFSG is enforced primarily through the market surveillance body, usually on a complaint, rather than through competitor warning letters — and that people citing statistics on this have generally only heard them. I have dropped the claim.
"The market surveillance body will start automated scans in Q3 2026"
Also from trade press. Someone with direct contact to the authority reported, as of June 2026, that the department meant to handle accessibility complaints is still being set up, that it works from reported cases, and that automated scanning of arbitrary websites was never on the table. I have dropped this claim too.
Both were load-bearing for my "why now". Neither survived contact with people who actually work in that market. If you are reading vendor content about EAA enforcement, this is worth knowing.
What is not in doubt
None of this says accessibility does not matter. One developer described finishing a full BFSG implementation and noted how much time it took, partly because disabled users tested the site before launch. Another pointed out that most of it overlaps with what makes a site good anyway, and that small changes remove real barriers even when you are not obliged to make any.
The demand is there. It is demand for people who do the work, not for a plugin that files the paperwork afterwards. That is a fine thing to learn in two weeks rather than in six months.
Thank you
To everyone in the German WordPress forum who answered a stranger's question carefully, and to the agency people who replied to a cold email with real numbers instead of a brush-off: thank you. You were more useful than any amount of desk research, and you cost me nothing but the willingness to ask before building.
Makoto Kuramochi — developer, Japan. The plugin is shelved, not abandoned in secret; this page replaced the pre-order page it used to be.