Bench note
Shopify Accessibility: What the Theme Store Guarantees and What Your Apps Break
Shopify sets a floor for themes and tests its own checkout. Everything you add between the two is yours to check.
Published 26 October 2026
Jump to a section8 sections
Shopify accessibility comes in three layers, and only two of them are Shopify's. The Theme Store sets an accessibility floor that a theme must clear to be listed. Checkout is Shopify's own code, and Shopify publishes a conformance report for it. Everything between those two, your theme settings, your content and every app you install, is yours, and that middle layer is where most stores lose accessibility they started with.
This entry reads Shopify's theme requirements, its merchant accessibility guidance and its accessibility statement, all on Shopify's own sites, as of 18 Oct 2026. Nothing here is legal advice, and nothing here says your store is or will be compliant with any law. That is a determination about a specific store that only someone who has examined it can make.
Short answer
- A theme from Shopify's Theme Store has passed published accessibility requirements, including a minimum automated accessibility score and specific keyboard, focus, contrast and label rules.
- Shopify says its checkout is tested against WCAG 2.2 Level AA and publishes a report on it.
- Your colours, images, text, custom sections and apps are not covered by either. Shopify's own guidance says following its guidelines "doesn't guarantee that your online store is fully accessible".
- Apps that add an accessibility toolbar or widget are overlays, and an overlay does not fix the store underneath.
The Theme Store accessibility requirement (the floor)
Shopify's requirements for themes listed in its Theme Store include a numeric threshold: themes must have "a minimum average Lighthouse accessibility score of 90 across the theme's product, collection, and home page, for both desktop and mobile", measured on a benchmark dataset with real images and content in every section.
An automated score only catches what a machine can detect, so Shopify adds explicit rules. Its list, as read on 18 Oct 2026, requires that:
- all parts of a page are keyboard accessible, "including dropdown navigation";
- focusable elements show a visible focus state;
- form inputs have a unique ID and a label whose
forattribute matches it; - themes are built with valid HTML;
- body text has a contrast ratio of 4.5:1, with 3:1 allowed for non-text items like icons and borders, and for text above 18pt;
- keyboard focus order matches the DOM order;
- pointer targets are at least 24 by 24 CSS pixels, with stated exceptions;
- headings
h1toh6are visually different from each other.
Those requirements line up with WCAG success criteria: keyboard operation (2.1.1, Level A), visible focus (2.4.7, Level AA), focus order (2.4.3, Level A), contrast (1.4.3, Level AA) and minimum target size (2.5.8, Level AA, new in WCAG 2.2). A Theme Store theme, as submitted, starts you on reasonable ground. How that compares with the starting point on other builders is set out on ADA compliant website builders.
The limit is in the word "submitted". The requirements describe what a theme had to demonstrate to be listed. They say nothing about the theme after you change its colour scheme, swap its fonts and add sections.
Checkout accessibility: Shopify's part
Shopify's accessibility statement, last updated on 7 July 2025, says it uses WCAG 2.2 as its "guiding principle" and tests "for WCAG 2.2 Level AA compliance". It publishes conformance reports in the VPAT format for several products. As listed on 18 Oct 2026:
| Product | Version tested | Standard tested |
|---|---|---|
| Checkout | Production | WCAG 2.2 A/AA |
| Admin | Production | WCAG 2.1 A/AA |
| Dawn theme | v2.4.0 | WCAG 2.1 A/AA |
| Mobile Admin | v1.0 | WCAG 2.1 A/AA |
Shopify's published accessibility conformance reports, as listed on its accessibility statement on 18 Oct 2026
Checkout
- Version tested
- Production
- Standard tested
- WCAG 2.2 A/AA
Admin
- Version tested
- Production
- Standard tested
- WCAG 2.1 A/AA
Dawn theme
- Version tested
- v2.4.0
- Standard tested
- WCAG 2.1 A/AA
Mobile Admin
- Version tested
- v1.0
- Standard tested
- WCAG 2.1 A/AA
Two things to read from that table. The checkout report is against the current WCAG version, on the production product, which is the strongest position in the list. The Dawn report is for version 2.4.0 of that theme, which may not be the version your store runs; check the version in your theme library before leaning on it. How to read a conformance report critically is covered in conformance reports and VPATs.
The same statement makes the division of labour explicit: "merchants have complete control over their theme codes." It also says Shopify is working to comply with accessibility standards for its e-commerce services covered by the European Accessibility Act.
Where stores fall below the floor
The places a store loses ground are predictable.
Colour changes. The theme passed contrast with its default palette. A brand colour on a button, light grey body text or white text over a photograph can each fall below 4.5:1. Shopify's merchant guidance asks for at least 4.5:1 for body and button text, 3:1 for large text of 24 px and up, sufficient contrast for all text over images, and 3:1 for input borders and icons.
Images without text alternatives. Product photos, banners and collection images each need alt text you write. Shopify lets you add it to product images from the admin and to theme images from the theme editor.
Custom sections and edited code. Anything pasted into a custom liquid block or edited in the theme code sits outside what the Theme Store checked.
Popups and widgets. Newsletter popups, cookie banners, chat bubbles, review carousels and countdown timers arrive through apps and scripts. Each can trap keyboard focus, hide behind or cover content, or fail to announce itself to a screen reader. A popup that cannot be closed by keyboard blocks the whole store for someone who does not use a mouse.
Motion. Shopify's guidance says slideshows should not play automatically, or should have controls to pause, advance or stop them, because moving content can cause dizziness for people with vestibular disorders.
Accessibility apps are mostly overlays
Some accessibility apps add a toolbar or widget to the storefront, such as font-size buttons or contrast toggles, and some make AI "remediation" claims. This entry did not survey the App Store and names none of them, but any app of that kind is what our accessibility overlays page calls an overlay, and the record there applies, including the $1 million that a January 2025 order from the US Federal Trade Commission required accessiBe to pay over its claims that its AI tool could make websites compliant.
An overlay sits on top of a store that still has unlabelled fields, missing alt text and inaccessible popups underneath. If an app description promises compliance, treat that promise as a warning sign, not a comfort. Rampline links to no overlay vendor, and our cookie consent page explains why consent banners, a separate obligation, also need checking for keyboard use.
A 15-minute store test
Run this on your live store, on a desktop browser, with the mouse set aside.
- Keyboard through the header (3 minutes). Press Tab from the address bar. Can you reach and open the menu, including any dropdowns, and move through every item? Is the focus ring always visible? The full method is in the keyboard test.
- Product to cart (4 minutes). Choose a product, select a variant, change the quantity and add to cart, all by keyboard. Then open the cart drawer or page and reach checkout.
- Popups (2 minutes). Trigger anything that appears on a timer or on exit intent. Can you close it with Escape or by tabbing to a close button?
- Contrast (3 minutes). Measure body text, button labels, sale badges and any text over images with a contrast checker against Shopify's thresholds above. Our notes on contrast in builder themes show where themes slip.
- Images and forms (3 minutes). Spot-check alt text on a few product images, and check that the newsletter and contact forms have visible labels rather than placeholder-only fields. Forms that fail screen readers shows what to look for.
Write down what fails. That list is the start of your accessibility statement.
Edge cases
A theme bought outside the Theme Store. The requirements above apply to themes listed in Shopify's Theme Store. A theme bought from a third-party marketplace or built by an agency has not necessarily been through them, so run the store test before launch rather than after.
A custom or headless storefront. If your storefront is built outside Shopify's theme system, none of the theme requirements apply to it. Only the checkout, if you use Shopify's, carries Shopify's own conformance report.
An older theme version. Theme updates can change markup. If you have not updated your theme in a long time, you may be running a version from before the current requirements; check the version and its changelog.
Writing a store accessibility statement
A store statement should say what standard you are working towards, what you have checked, what you know is not yet right, and how a customer who hits a barrier can still buy from you, by email, phone or another route. It should not claim compliance nobody measured. Our guide to writing an accessibility statement sets out what belongs in one, and if you sell to consumers in the EU, publishing that kind of information is part of what the European Accessibility Act asks of in-scope shops.
If you are choosing a platform rather than fixing one, Shopify is the one examined here; compare its starting point with the others before you decide.
Questions from the bench
Is Shopify ADA compliant?
Are Shopify themes accessible?
Do Shopify accessibility apps work?
Does Shopify have an accessibility statement?
How do I check my Shopify store for accessibility?
Where this is filed
Every note here sits underneath one assessment: ADA-compliant website builders, which is where the platforms are read side by side. Nothing on this site is legal advice, and no builder on that page is sold as a route to compliance.
The recheck notice
When a platform quietly changes what it gives you
Builders move accessibility features without a changelog: a theme restyles its focus ring, a wizard learns a check, a field migrates to another panel. The recheck list is meant to carry one short note whenever a page here has to be corrected. It is not switched on yet, so this form keeps nothing — until it is, the corrected page itself is the record.