Free tool

Accessibility statement generator.

Answer a few questions and get a complete, honest accessibility statement you can paste onto your site. Free, no signup, and the result is fully visible right here.

The statement is built in your browser. Nothing you type here is sent anywhere unless you choose the optional email below the result.

What an accessibility statement needs to say

A useful statement covers a handful of things: a commitment, the standard the site is measured against, an honest conformance status, known limitations, how the evaluation was done, and a working way to reach you. The European Accessibility Act and public sector rules in several countries expect statements along these lines, and EN 301 549 is the standard they typically point to. Our guide on what a statement needs to say goes through each part in detail.

A statement describes your site. It does not fix it.

The generator drafts wording from what you tell it; it cannot verify any of it. Publishing "fully conformant" without testing is worse than publishing nothing, because it is a written claim regulators and users can check. Before you choose a status, test: run the free checker on your key pages, and review the criteria that need a human against a manual checklist.

The step after the statement

A statement should rest on evidence and stay current as the site changes. That is the job of the full Complaudax workflow: audits on any page including behind a login, issue tracking per site, and conformance reports and statements generated from the actual audit history, so the document and the site never drift apart. See how it works and what it costs.

Questions about this generator

Is the generated statement visible without giving an email?

Yes. The full statement appears on this page the moment you generate it. Emailing yourself a copy and setting a review reminder are optional and never required.

Does publishing a statement make my site compliant?

No. A statement describes the state of your site; it does not change that state. Regulators expect the statement to be accurate, which is why it should rest on real testing.

How often should an accessibility statement be reviewed?

Review it whenever the site changes significantly, and at least once a year. A stale statement that no longer matches the site is worse than none, because it is inaccurate.

What should I do before claiming partial conformance?

Test the site: run automated checks, review the criteria that need human judgment, and list the known limitations honestly. The statement is only as good as the evaluation behind it.