An accessibility statement is a short public page that tells shoppers how accessible your store is, what you are doing about known problems, and how to contact you if something does not work for them. It takes about an hour to write, costs nothing, and gives a shopper who gets stuck a clear way to reach you. This guide explains what to include, what not to claim, and how to add the page to a Shopify or WooCommerce store.
What an accessibility statement is (and isn't)
The W3C's Web Accessibility Initiative describes an accessibility statement as a way to show your commitment to accessibility and to give people information about the accessibility of your content, including known limitations and how to get help (Developing an Accessibility Statement (W3C WAI)). It is a communication tool, not a certificate.
A statement does not make a website accessible, and it is not a legal shield. Adding one will not fix an unlabeled button or a checkout step that traps keyboard focus. What it does do is:
- Give a shopper who hits a barrier a way to reach you and still complete their purchase, for example by email or phone order.
- Show that you know about specific problems and have a plan for them, instead of pretending they don't exist.
- Force you to find out where your store actually stands, which is useful in itself.
What not to write
The most common mistake is overclaiming. Avoid phrases like:
- "This website is fully ADA compliant." Nobody can certify that from an automated scan, and a statement that is not true is worse than no statement.
- "This website conforms to WCAG 2.1 AA" unless a full manual evaluation of the whole site has confirmed it. WCAG conformance has specific requirements, including that full pages and complete processes, such as checkout, meet every criterion (WCAG 2.1, Conformance Requirements (W3C)).
- "Our accessibility widget makes this site accessible." Overlay widgets have been heavily criticised, and in 2025 the U.S. Federal Trade Commission finalised an order against one vendor over its claims (FTC Approves Final Order Requiring accessiBe to pay $1 Million (Federal Trade Commission, April 22, 2025)).
Write what is true: what you have done, what you know is still wrong, and how people can get help.
Step 1: Find out where your store stands
Before writing anything, collect some facts. You don't need an expensive audit to start:
- Run a free automated scan of your key pages (home, a collection, a product and the cart). Our free store scan does this in about a minute and lists what it found in plain English.
- Do a 10-minute keyboard-only test of the path from the homepage to checkout.
- Note your platform and theme. On Shopify, the checkout is controlled by Shopify, not your theme. On WooCommerce, your theme and plugins shape almost everything.
- List the apps or plugins that add visible features: pop-ups, reviews, chat, quick view, wishlists. These are frequent sources of problems (see our guide on apps).
Step 2: Use this template
Here is a plain-English template. Replace the parts in square brackets and delete anything that does not apply. The W3C also has a free generator if you prefer a form (Accessibility Statement Generator (W3C WAI)), and our own statement generator fills in this template for you.
Accessibility statement for [Store name]
We want everyone to be able to browse and buy from [Store name],
including people who use screen readers, keyboards, voice control,
screen magnifiers or other assistive technology.
What we have done
- We checked our home, collection, product and cart pages with an
automated accessibility tool on [date] and fixed [what you fixed,
for example: missing image descriptions and unlabeled buttons].
- We tested the path from the homepage to checkout using only a
keyboard on [date].
- We use [theme name] on [Shopify / WooCommerce].
Known problems we are working on
- [Example: Some older product photos do not have text descriptions
yet. We expect to finish adding them by [month].]
- [Example: Our reviews widget is provided by a third party and is
hard to use with a keyboard. We have reported this to the vendor.]
Our goal
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1
at level AA. We have not had a full independent audit, so we do not
claim that the site fully meets this standard.
Need help or found a problem?
If anything on our site is hard to use, please tell us and we will
help you place your order another way.
Email: [your email]
Phone: [your phone, optional]
We aim to reply within [2 business days].
This statement was last reviewed on [date].Notice what the template does: it states a goal (WCAG 2.1 AA, explained in our plain-English WCAG guide) without claiming to have reached it, it is specific about what was tested and when, and it gives a real way to get help.
Step 3: Publish the page on Shopify
- In your Shopify admin, go to Online Store > Pages and click Add page.
- Title it "Accessibility" or "Accessibility statement" and paste your text. Use the editor's heading options for "What we have done", "Known problems" and "Need help?" rather than bold text, so screen reader users can jump between sections.
- Save. The page address will usually be
/pages/accessibilityor similar.
If your theme's footer is built from a menu, add the page to that menu in the navigation settings. If you want a link in a custom footer section instead, a minimal Liquid example looks like this:
<ul class="footer-links">
{%- for link in section.settings.menu.links -%}
<li><a href="{{ link.url }}">{{ link.title | escape }}</a></li>
{%- endfor -%}
<li><a href="{{ pages.accessibility.url }}">Accessibility</a></li>
</ul>pages.accessibility looks the page up by its handle, so this only works if the handle is accessibility. Editing theme code is easiest on a duplicate of your theme, which you can preview before publishing (Duplicating themes (Shopify Help Center)).
Step 4: Publish the page on WooCommerce (WordPress)
- Go to Pages > Add New, title it "Accessibility statement" and paste your text. Use Heading blocks for the section titles.
- Publish, then add it to your footer: in a classic theme via Appearance > Menus (or a footer widget), in a block theme via Appearance > Editor and the footer template part's Navigation block.
If your footer is hard-coded in a classic theme and you are comfortable with a child theme (Child Themes (WordPress Theme Handbook)), you can add the link with a small hook. Many themes print footer content on wp_footer; a safer option is your theme's own footer hook if it has one. A generic example:
<?php
// Adds an "Accessibility" link to the footer of a classic theme.
add_action( 'wp_footer', function () {
$page = get_page_by_path( 'accessibility-statement' );
if ( ! $page ) {
return;
}
printf(
'<p class="a11y-footer-link"><a href="%s">%s</a></p>',
esc_url( get_permalink( $page ) ),
esc_html__( 'Accessibility statement', 'your-child-theme' )
);
} );Put custom code in a child theme or a code-snippets plugin, never in the parent theme files, or the next theme update will erase it.
Check your own store in a minute or two. Our free scanner opens your homepage, a collection page, a product page and your cart in a real browser and lists the problems it can detect automatically, in plain English.
Step 5: Keep it true
A statement that was accurate a year ago may not be today. New apps, theme updates and new product photos all change what shoppers experience. Put a reminder in your calendar to re-check every three months: run the scan again, repeat the keyboard test, update the "known problems" list and change the "last reviewed" date. If someone emails you about a barrier, reply quickly, help them complete their order, and add the problem to your list.
Common questions
Do I legally need an accessibility statement?
That is a legal question we can't answer. Requirements differ by country and situation; ask a qualified attorney. From a practical point of view, it is a low-cost way to help shoppers who get stuck.
Can I copy another store's statement?
You can borrow structure, but the facts must be yours: your tests, your dates, your known problems and your contact details. A copied statement that describes someone else's site is misleading.
Should I mention the platform's own accessibility work?
You can say which platform and theme you use. Shopify and WooCommerce both publish information about their own accessibility work (Accessibility for themes (Shopify Help Center); Accessibility at Woo (WooCommerce)), but their work on the platform does not cover your theme edits, apps or content.
Technical fixes, not legal advice. This guide explains website accessibility from a technical point of view. We are not a law firm, and nothing here is legal advice. No scan, fix or guide can guarantee legal compliance, the outcome of any demand letter or lawsuit, or protection from future claims. If you have received a legal claim, please consult a qualified attorney about it.
Sources
- Developing an Accessibility Statement (W3C WAI)
- Accessibility Statement Generator (W3C WAI)
- WCAG 2.1, Conformance Requirements (W3C)
- FTC Approves Final Order Requiring accessiBe to pay $1 Million (Federal Trade Commission, April 22, 2025)
- Duplicating themes (Shopify Help Center)
- Child Themes (WordPress Theme Handbook)
- Accessibility for themes (Shopify Help Center)
- Accessibility at Woo (WooCommerce)