Produce a publishable, EAA-compliant accessibility statement in English, German, or French — with the right enforcement procedure for your country baked in.
Generate your statement
The address where users can report accessibility barriers.
Used for the enforcement procedure section.
Most organisations should pick partial — the EAA expects you to be honest about gaps you're aware of.
One issue per line, or comma-separated. Required for partial / non-compliant status.
All seven required sections
Compliance status, applied standard, known issues, preparation date, evaluation method, feedback channel, enforcement procedure.
Country-specific enforcement
Direct links to the right regulator for Germany, France, Austria, Belgium, Netherlands, Ireland, Spain, and Italy.
Markdown and HTML exports
Paste straight into your CMS, blog, or static site. The HTML is a self-contained document you can host as-is.
Three languages, more coming
English, German, and French templates — the structure is identical so you can publish parallel versions for multilingual sites.
Yes — for the vast majority of EU consumer-facing sites. Under the European Accessibility Act (in force since 28 June 2025), the German BFSG, the French RGAA, the UK PSBAR, and equivalent laws across the EU, organisations covered by the legislation must publish an accessibility statement that explains compliance status, known gaps, and how users can report problems. France even charges a separate €25,000/year fine for missing or incomplete statements.
EN 301 549 and the EAA expect the statement to cover: (1) compliance status against WCAG 2.1 AA, (2) the standard you applied, (3) any non-accessible content you know about, (4) the date of preparation, (5) how the website was evaluated, (6) a contact channel for accessibility feedback, and (7) the enforcement procedure for users in your jurisdiction. This generator produces all seven sections.
No. This generator produces a structurally complete starting template using the model required by the EAA and EN 301 549. You should review it with someone familiar with your specific compliance situation before publishing — particularly the "non-accessible content" section, which should reflect a real audit of your site.
The enforcement procedure section must point users to the regulator in your jurisdiction. Each EU member state designates a different body — Schlichtungsstelle BGG in Germany, Défenseur des droits in France, College voor de Rechten van de Mens in the Netherlands, etc. Picking your country populates the right enforcement contact automatically.
Yes — that is the point. Download the Markdown or HTML version and edit it in your CMS, doc editor, or static site. The "non-accessible content" section in particular benefits from concrete bullet points based on a real scan of your site.
Yes — under the EAA the statement must be in the languages your site uses to serve consumers. If your site is published in German and English, publish two statements. The generator supports English, German, and French; more languages are coming.
Best Practices
The accessibility statement that holds up
Country-by-country enforcement paragraphs, plus the seven sections every statement needs.
Read
Legal Compliance
EU Accessibility Act fines in 2026
How much each EU country can fine you, and what their enforcement looks like in practice.
Read
Best Practices
Top 10 EAA violations + DIY fixes
Common WCAG 2.1 AA failures we find on EU sites, with copy-paste fixes.
Read
Legal Compliance
France RGAA + EAA: la conformité en 2026
How French enforcement works and the €25,000/year fine for missing statements.
Read
The “non-accessible content” section needs real findings. Run a free WCAG 2.1 AA scan and get a list of issues mapped to EAA legal risk.