Free tool
Accessibility statement generator
Answer a few questions and copy an accessibility statement for your website: the standard you aim for, your conformance status, what you know doesn't work yet, and how people can reach you.
Your statement
Check this wording
Paste it into a new page titled "Accessibility statement". Use "Copy HTML" for a page editor's HTML or code view, and "Copy text" anywhere else.
Example statement
Copy it and replace everything in square brackets. Delete anything that doesn't apply.
Accessibility statement for [Website name] [Organization name] wants everyone, including people with disabilities, to be able to use [Website name] ([website address]). We are working to make it accessible and easy to use. The standard we aim for We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, published by the World Wide Web Consortium (W3C). These guidelines explain how to make web content easier to use for people with disabilities. Conformance status [Website name] is partially conformant with WCAG 2.2 Level AA. Partially conformant means that some parts of the content do not fully conform to the standard. What we've done - [What you've done, such as: we tested our key pages with a keyboard and a screen reader]. Known limitations We know about these problems and are working on them: - [Page or feature]: [what the problem is, and what you're doing about it, by when]. What you can do: [what people can do in the meantime]. Technical specifications [Website name] relies on HTML, WAI-ARIA, CSS and JavaScript to work with your web browser and any assistive technologies you use. Feedback We welcome your feedback. If you have trouble using any part of [Website name], please tell us: - Email: [email address] - Phone: [phone number] We aim to reply within [number] business days. How we assessed this site We assessed [Website name] ourselves (self-evaluation). Date We created this statement on [date]. We last reviewed it on [date].
What is an accessibility statement?
A public page that says how accessible your website is. W3C recommends that it contains at least a commitment to accessibility, the standard you apply and contact information for people who hit a problem. It's a promise and a status report, not a certificate: describe what you've checked, and name what still needs fixing. Our guide on how to write an accessibility statement explains each part.
What should go under known limitations?
Anything you know doesn't work well yet. For each one, say:
- what doesn't work, such as "Product videos" or "The store locator map";
- why, or what you're doing about it, and by when;
- what people can do in the meantime, such as asking you for a transcript.
A short, honest list builds more trust than a claim that nothing is wrong. If you've run an audit, start with the issues it found that you haven't fixed yet.
Where should I publish it?
On its own page, linked from your footer next to your other policies, so it's reachable from every page. Call the link "Accessibility" or "Accessibility statement". On Shopify, create the page under Online Store › Pages › Add page, then add it to your footer menu under Content › Menus.
When should I update it?
Whenever something changes: a new theme or redesign, a new app that adds features to your site, or a fix to something on your known-limitations list. Update the review date each time, so visitors can see the statement is current.
Prefer a different format? W3C's own accessibility statement generator is free too, and walks you through each part in more detail.
Frequently asked questions
Is this accessibility statement generator free?
Yes. It runs in your browser: nothing you type is sent to us. Your answers are saved in your own browser so you can come back to them, and the Clear form button deletes them.
Which conformance status should I choose?
Partially conformant fits most sites that have been tested and still have known issues. Choose fully conformant only if a full evaluation, including manual testing, found no exceptions. If you haven't evaluated the site yet, choose not assessed and say what you plan to do.
Should my statement say WCAG 2.1 or WCAG 2.2?
Name the version you actually test against. W3C designed WCAG 2.2 to be backward compatible, so content that conforms to 2.2 also conforms to 2.1.
Does publishing a statement make my website accessible?
No. A statement describes your site and tells people how to reach you. It doesn't fix anything, and it isn't a legal shield. Pair it with real fixes and testing.
Is an accessibility statement required by law?
It depends on where you are and what you do. Public bodies in countries that implement the EU Web Accessibility Directive may have to publish one, and the European Accessibility Act asks businesses in its scope to publish information on how their service meets its accessibility requirements. This is general information, not legal advice.