Build your statement
Everything runs in your browser - nothing you type is sent anywhere. The statement is yours: review it, adapt it, and have it checked against the laws that apply to you.
Where is an accessibility statement required?
An accessibility statement is a public page that says what accessibility standard your site targets, how far along you are, what you are doing about it, and how users can reach you when something blocks them. In a growing list of jurisdictions it is not optional:
- Israel - the Service Accessibility Regulations under the Equal Rights law make publishing an accessibility statement on the website mandatory for service providers, alongside IS 5568 conformance.
- European Union - public-sector bodies must publish and maintain a statement under the Web Accessibility Directive, and the European Accessibility Act extends documentation duties to in-scope private services.
- France - the RGAA regime requires an accessibility declaration per site, a visible conformance status, and a multi-year plan - with fines for missing publications.
- United Kingdom - public-sector websites and apps must publish an accessibility statement under the 2018 regulations; see the UK page.
- Canada - AODA obliges organizations (50+ employees) to publish accessibility policies and multi-year plans, and the federal ACA requires published accessibility plans and feedback processes.
- United States - no statute mandates a statement, but courts and the DOJ treat a current, honest one as evidence of good-faith effort, and it is standard practice for ADA risk reduction.
Place it on its own URL - /accessibility-statement is the convention - and link it from the footer of every page, next to your privacy policy.
Keep it honest
The strongest statement is an accurate one. "Partially conformant" with named limitations and a working feedback channel is more credible - and more legally defensible - than a perfect-sounding claim your site cannot back. Declare "fully conformant" only after testing against every applicable success criterion, and re-review the statement whenever the site changes significantly. If you have not audited yet, a professional accessibility audit gives your statement the evidence base it needs.
Frequently asked questions
Is an accessibility statement legally required?
In many places, yes: Israel mandates one for service providers under the accessibility regulations, EU and UK public-sector bodies must publish one, France requires a declaration per site, and Canadian organizations publish accessibility policies and plans under AODA and the ACA. In the US it is not statutory, but it is standard practice and good-faith evidence. Check the laws that apply to you.
What must an accessibility statement include?
The standard your site targets (for example WCAG 2.2 Level AA), your conformance status, the measures you take, known limitations, a way for users to report barriers, your expected response time, and the statement and review dates.
Should I claim full conformance?
Only if testing genuinely supports it. "Partially conformant" with honest limitations is credible and defensible; an inflated claim invites complaints and undermines the statement's legal value.
Where should the statement live?
On its own page, linked from every footer - /accessibility-statement is the convention. Search engines, auditors and users all look for it there.
Does this generator store my data?
No. It runs entirely in your browser; nothing you type leaves the page.
- W3C WAI, Developing an Accessibility Statement - w3.org/WAI
- European Commission, Web Accessibility Directive - accessibility statements - digital-strategy.ec.europa.eu
Last updated . Reviewed by the EqualWeb accessibility team.
Back your statement with the real work
A statement is a claim - testing is the proof. Scan one page instantly, crawl the whole domain and monitor continuously with the Accessibility Testing suite.