Is an accessibility statement legally required?

For EU public-sector websites, yes — Directive 2016/2102 (Web Accessibility Directive) requires a published accessibility statement. For private-sector services under the EAA, a statement is strongly recommended as part of the documented evidence trail and is explicitly required for some categories under national transpositions like Spain’s Ley 11/2023 and France’s Article 47 of Loi 2005-102.

What does an accessibility statement need to include?

Five elements: compliance status (full / partial / non-compliant), known accessibility limitations, the date the statement was prepared and last reviewed, the method used to assess accessibility, and a feedback mechanism plus enforcement-procedure pointer. Our generator covers all five aligned to the EU directive template.

Can I publish the generated statement directly?

Treat the output as a starting template, not a final legal document. The wording is aligned to EU directive requirements and national transposition templates, but every accessibility statement should be reviewed against the specific facts of your site and (where stakes are high) by your legal counsel before publishing.

Does the statement need to be in the user’s language?

Generally yes. National authorities expect the statement in at least the official language(s) of the country where the service is offered. Our generator produces English, German, French, and Spanish output. For Italian, Dutch, Romanian, and other languages, generate the English version then translate with a native-language reviewer.

Free Tool

Accessibility statement generator

Generate an EAA-aligned accessibility statement in English, German, French, or Spanish. Covers compliance status, known limitations, contact, and the enforcement-procedure pointer your client's national regulator expects to see.

Generated statement (HTML)

<!-- Accessibility Statement generated by AccessiProof. Review with your legal counsel before publishing. -->
<article lang="en">
  <h2>Accessibility Statement</h2>
  <p>Your Organization is committed to making example.com (https://example.com) accessible to all users in line with applicable European accessibility law. This statement applies to the website listed above.</p>

  <h3>Compliance status</h3>
  <p>example.com partially conforms the requirements of Directive (EU) 2019/882 (European Accessibility Act), the relevant European technical standard EN 301 549, and Web Content Accessibility Guidelines (WCAG) 2.1 Level AA.</p>

  <h3>Known accessibility limitations</h3>
<p>Some PDF documents linked from the site are not yet fully tagged for screen-reader access.</p>

  <h3>Preparation of this statement</h3>
  <p>This statement was prepared based on the following assessment: Independent third-party accessibility audit by AccessiProof, supplemented by automated scanning with axe-core.. The statement was first prepared on 9 May 2026 and last reviewed on 9 May 2026.</p>

  <h3>Feedback and contact</h3>
  <p>If you find an accessibility barrier on this site, or want to request information in an accessible format, contact our Accessibility coordinator at accessibility@example.com. We aim to respond within ten business days.</p>

  <h3>Enforcement procedure</h3>
  <p>If our response is unsatisfactory, you can escalate to the relevant national market-surveillance authority in each EU member state where the service is offered. More information: Submit complaints to the national consumer-protection authority in your country..</p>
</article>

Heads up: this template mirrors what EU directive 2016/2102 and EAA-derived national transpositions ask for. It is a starting point — review the wording with your legal counsel before publishing on a client site.

Why this matters

The accessibility statement is the regulator's first touchpoint

When a complaint reaches a national accessibility authority — in Germany the Bundesfachstelle, in France the DGCCRF, in Spain OACIAP — the first thing they look for is a published accessibility statement. A site without one signals that accessibility hasn't been formally assessed, which itself becomes a finding. A site with a thorough statement signals good-faith compliance work and gives the regulator a starting point for dialogue.

From audit to statement

Most EU agencies pair this tool with a paid audit. The audit identifies the “known limitations” section. The audit date populates the “prepared” field. The audit's scope statement informs the “preparation method” section. Generating the statement at the end of an audit engagement turns it into a twenty-minute deliverable rather than a half-day exercise.

Pair with full audit

Run a 15-page audit — 399 € →

Audit findings populate the “known limitations” section. White-label PDF for EU agencies.

EAA accessibility statement guide →

What the statement needs, why template-only statements fail, and how to keep yours audit-ready.

Generated statements are produced locally in your browser based on the inputs you provide. AccessiProof does not collect, log, or store any of the form data. Treat the output as a starting template — review wording with your legal counsel before publishing on a client site.