Free Accessibility Statement Generator
Required by most accessibility laws. Generate a compliant statement for your website in under 2 minutes.
Your Details
Your Statement
Why Publish an Accessibility Statement?
An accessibility statement is a public-facing document on your website that declares your commitment to accessibility, describes the conformance level you're targeting, and gives visitors a way to report barriers they encounter.
Publishing one is legally required under several major laws:
- EAA / EN 301 549 — required for all covered digital services
- RGAA (France) — annual statement mandatory, fines apply if missing
- Section 508 — federal agencies publish conformance reports
- AODA — public-facing accessibility policy required
Even where not legally required, an accessibility statement is a strong signal to users, regulators, and courts that you take accessibility seriously. It can also help reduce the likelihood of a “drive-by” ADA lawsuit.
Back Your Statement with a Real Audit
A statement without an audit is just a promise. Scan your site to know exactly where you stand.
What a good accessibility statement actually contains
A statement is not a disclaimer and it is not a legal shield. It is a public, dated record of where your site stands and how someone can reach you if it fails them. The ones that are worth publishing share five things: the standard you are working to, usually WCAG 2.1 AA; an honest conformance status; the known gaps you have not fixed yet; a way to report a problem that reaches a human; and the date it was last reviewed.
The last two carry most of the practical weight. A statement with no working contact route is where accessibility complaints turn into formal ones, because someone who hit a barrier had nowhere else to go. And an undated statement quietly becomes worthless — reviewers treat a statement with no date, or a date from three years ago, as evidence that nobody is looking.
The honesty problem
The most common mistake is claiming full conformance because it reads better. It is also the most expensive one: an overclaim that turns out to be false is far worse than a partial claim that turns out to be accurate, both in how it is treated and in how it reads to the person it failed. Listing known gaps with an intention to address them is a stronger position than a clean claim you cannot support. Run a scan first so that whatever you publish is something you can actually stand behind.
Accessibility statement questions
Is an accessibility statement legally required?
It depends on where you are and what kind of organisation you are. Public-sector bodies in the EU and UK are generally required to publish one. For private companies it is more often strongly expected than strictly mandated — but it is cheap to publish, and its absence is conspicuous when someone goes looking.
Where should I publish it?
At a stable, predictable URL such as /accessibility, linked from your site footer on every page. People look for it in the footer, and so do the people assessing you.
How often should it be updated?
Review it at least annually, and any time the site changes materially — a redesign, a new checkout, a platform migration. Update the review date even when nothing else changed, because the date is part of what the statement is telling people.
What if my site is not fully conformant yet?
Say so. A statement that names its known gaps and what you intend to do about them is more credible and more defensible than a claim of full conformance that does not survive contact with a real audit.