Accessibility statement generator
The page a compliant site is expected to publish, and most never do. Fill in four fields and get a statement that says what you tested, what you did not, and how somebody reports a barrier. Free, no account.
Your statement — preview, fill the fields above
# Accessibility statement for Your organisation Your organisation is committed to making example.com accessible to as many people as possible, including those using assistive technology. ## How accessible this website is We aim to meet WCAG 2.1 AA. This website is partially conformant — most of the content conforms, but some parts do not yet fully meet the standard. ## How we tested This website was tested using automated tooling that renders each page in a real browser and checks it against WCAG 2.1 AA. **What automated testing does not cover.** Automated tools detect only part of the applicable success criteria — commonly estimated at around a third. They cannot judge whether alternative text meaningfully describes an image, whether the reading order of a page makes sense, whether a custom control can be operated by keyboard, or whether content is understandable. Those require a person, and ideally people who use assistive technology daily. We therefore describe the results of automated testing as evidence, not as a determination of conformance. ## Feedback and contact If you find an accessibility barrier on this site, or need content in a different format, please contact [email protected]. We aim to respond within five working days. Tell us what you were trying to do, the page you were on, and what went wrong — that is usually enough for us to reproduce and fix it. ## Enforcement If you contact us about an accessibility problem and are not satisfied with our response, you may be able to escalate it to the relevant regulator for your jurisdiction. In the United States that is typically the Department of Justice under the Americans with Disabilities Act; in the European Union, the national body designated under the European Accessibility Act. ## Statement details This statement was prepared on 15 September 2026. It applies to https://example.com. It should be reviewed whenever the site changes materially, and at least once a year. A statement that describes a version of the site that no longer exists is worse than no statement at all.
Generated in your browser. Nothing you type here is sent to us or stored.
Why the wording matters
Most generated statements read like a compliance claim: a badge, a standard, a date. That is the version you do not want. A statement is a written assertion about your own site, and if it overstates what you have actually verified, it works against you rather than for you.
This one names the limits explicitly — automated testing detects roughly a third of WCAG success criteria, and cannot judge whether alt text is meaningful, whether reading order makes sense, or whether a custom control can be operated by keyboard. Saying so is not a weakness. It is the difference between a statement that survives scrutiny and one that invites it.
It also includes the part people most often leave out: a contact route with a stated response time. In most jurisdictions that route matters more than the conformance claim, because it is what a regulator or a complainant will actually test.