What is an accessibility statement?
An accessibility statement is a public page that tells visitors how accessible your website is: the standard you aim for, how far you meet it, what you know does not work yet, and how people with disabilities can reach you when they hit a barrier. It is a communication tool. It does not change your store, and it is only useful if it is accurate.
Some laws ask for this kind of information. In the EU, the European Accessibility Act (EAA) asks many businesses that sell online to explain how their service meets the accessibility requirements, and a statement page is a common way to provide it (microenterprises with fewer than 10 staff and no more than 2 million euros in annual turnover or balance sheet total are exempt from the service rules). In the US, the ADA does not require a statement, but a clear contact path for accessibility problems is widely recommended. Ask a legal adviser what applies to your business.
What to include, based on W3C guidance
The W3C Web Accessibility Initiative recommends a statement with a few core parts and some optional ones. This generator follows that structure:
| Section | What it says |
|---|---|
| Commitment | That you want the store to be usable by everyone, including people with disabilities. |
| Standard | The guideline you aim for, usually WCAG 2.1 or 2.2 at level AA. |
| Conformance status | Fully conformant, partially conformant or non-conformant, in W3C's terms, plus an explanation. |
| Known limitations | Parts that do not work yet, why, and what people can do instead. |
| Measures taken | What you actually do: design reviews, training, regular checks, alt text. |
| Feedback | Email or phone, and how fast you reply. |
| Date | When the statement was written or last reviewed. |
Optional sections cover third-party content, the assessment approach (self-evaluation or an external audit) and the technologies the site relies on.
Choosing the conformance status honestly
The conformance status is a claim about your store, so only you can make it. W3C defines the terms this way:
- Fully conformant: the content meets every success criterion of the chosen standard and level, without exceptions. Only claim this after a full evaluation.
- Partially conformant: some parts do not meet the standard. If that is your store, saying so plainly with a list of known limitations is more useful than a vague promise.
- Non-conformant: the content does not meet the standard.
If nobody has checked the store yet, pick "Not assessed" and say so. Do not base the status on an app or widget: an accessibility menu or overlay can help some visitors, but it does not make a store conform to WCAG on its own. An automated scan finds only part of the issues, so a meaningful status also needs manual testing with a keyboard and a screen reader.
Example: Acme Goods checked its product pages, cart and contact form and found that older product videos lack captions and some size charts are images. Its statement says "partially conformant with WCAG 2.2 level AA", lists those two limitations with an email alternative, and promises a reply within 5 business days.
Where to publish it on Shopify
- In your Shopify admin, go to Online Store, Pages, and click Add page. Title it "Accessibility statement".
- Click the Show HTML button (<>) in the content editor and paste the HTML from this generator, or paste the plain text into the normal editor. Save.
- Add the page to your footer menu, next to your privacy policy and terms (Online Store, Navigation, or Content, Menus in newer admins). That is where visitors look for it.
- If you use an accessibility menu, link the statement from it too.
Want to see a finished page first? Look at the example accessibility statement on this site.
How often to update it
Review the statement at least once a year, and also after any change that can affect accessibility: a new theme, a redesign, new apps that add things to the storefront, or new kinds of content such as video. Update it when you fix a known limitation, when your contact details change, and when you move to a newer WCAG version. Change the date each time, so visitors can see the statement is current.
Frequently Asked Questions
Is an accessibility statement legally required?
It depends on where you sell. The European Accessibility Act asks many online businesses in the EU to explain how their service meets the accessibility requirements, and a statement is a common way to do that. In the US the ADA does not require one. This generator is a template, not legal advice, so check with a legal adviser.
Does publishing an accessibility statement make my store compliant?
No. A statement describes your store and gives people a way to report barriers; it does not fix anything. Your store has to actually meet the standard, and the statement has to describe its real state.
Can I say my store is fully conformant because I installed an accessibility widget?
No. A widget or overlay can help some visitors adjust the page, but it does not make a store conform to WCAG on its own. Only claim full conformance after a complete evaluation of the content against the standard.
Should I choose WCAG 2.1 or WCAG 2.2?
WCAG 2.2 is the current W3C recommendation and includes everything in 2.1 plus a few more criteria. WCAG 2.1 level AA is the level referenced by the EU standard EN 301 549. Either is a reasonable target; pick the one you actually test against.
What is the difference between an accessibility statement and an accessibility policy?
People often use the terms for the same public page. Strictly, a policy is an internal commitment and process, while a statement is the public description of your site's accessibility, its known limitations and how to contact you. This generator writes the public statement.
Is anything I type sent to a server?
No. The statement is built in your browser, and Copy and Download work without sending anything anywhere.
