Shopify ADA Compliance Checklist (2026)

The Americans with Disabilities Act doesn't mention websites. It was written in 1990, before most people had email. But courts have consistently ruled that ADA Title III — which bans discrimination in "places of public accommodation" — applies to ecommerce stores, and Shopify merchants are being sued over it in growing numbers. If you sell online in the US, this isn't a hypothetical risk.

This is the checklist we use when we audit a Shopify store for accessibility. It won't make you bulletproof — nothing does — but it will close the gaps that plaintiffs' attorneys look for first.

What ADA actually requires (there's no official standard)

Here's the part that trips people up: the ADA itself doesn't name a technical standard for websites. Congress never updated the law for the internet, and the Department of Justice has stated that Title III applies to online stores without formally adopting a specific set of rules.

In practice, that gap gets filled by WCAG (Web Content Accessibility Guidelines) 2.1 or 2.2, Level AA. It's not law, but it's what settlement agreements, DOJ guidance letters, and court rulings reference over and over. If your store meets WCAG 2.2 AA, you're aligned with what every party in a lawsuit — plaintiff, defendant, and judge — will be measuring you against.

Two more things worth knowing before you start:

• The EU's Accessibility Act is now separately enforceable (since June 2025) for businesses selling into the EU, with its own requirements loosely mapped to WCAG. If you ship to European customers, this checklist covers most of the same ground.
• Compliance isn't binary. You don't "pass" ADA the way you pass a driving test. You reduce your exposure by fixing real barriers, and you keep reducing it as you find more.

The Shopify ADA compliance checklist

Work through these in order. Each section takes a few minutes to check manually, even without specialist tools.

1. Images and media

• Every product image has descriptive alt text — not "IMG_2481.jpg," not the product title repeated with no useful detail, but a description a blind shopper could act on ("navy wool crew-neck sweater, folded, on a grey background").
• Decorative images (background textures, spacers) have empty alt attributes (alt="") so screen readers skip them instead of reading a filename aloud.
• Any video on your site has captions. Any audio has a transcript.

2. Colour and contrast

• Body text has a contrast ratio of at least 4.5:1 against its background; large text (18pt+) needs 3:1. Free contrast checker tools will confirm this in seconds against your theme's colour palette.
• Sale badges, "sold out" labels, and form errors don't rely on colour alone. A red "out of stock" label also needs the word "out of stock" — colour-blind users can't distinguish red from green.
• Placeholder text in form fields isn't the only label. Placeholder text disappears once a field is filled and often fails contrast requirements outright.

3. Keyboard navigation

• Every interactive element — nav links, filters, "add to cart," quantity selectors, the cart drawer, checkout fields — is reachable and operable using only the Tab and Enter keys, no mouse.
• Focus is visible. When you Tab to a button or link, there's a clear visual outline showing where you are. Many themes strip this out for aesthetics with outline: none and never replace it.
• Modals and cart drawers trap focus correctly — Tab cycles within the open modal, not out to page content hidden behind it — and Escape closes them.

4. Forms and checkout

• Every input has a <label> programmatically tied to it, not just visually placed nearby. Screen readers announce the label when the field receives focus; without the connection, they announce nothing useful.
• Error messages are specific ("Enter a valid postal code") and announced to screen readers when they appear, not just shown in red text.
• Checkout works start to finish with a keyboard and a screen reader. This is the single highest-value flow to test — it's also revenue-critical, so bugs here cost you sales even before they cost you a lawsuit.

5. Structure and semantics

• Headings follow a logical order (one H1, then H2s, then H3s nested under the right H2) instead of skipping levels for visual sizing.
• Landmark regions exist — header, nav, main, footer — so screen reader users can jump between sections instead of listening to the whole page top to bottom.
• Links describe their destination ("View return policy," not "click here" repeated six times on a page).

6. Third-party apps

This is the category most Shopify merchants miss. Your theme might be clean, but the review widget, upsell popup, chat bubble, and countdown timer you installed from the App Store often aren't — and they load on every page. Audit each installed app individually; a single broken popup can undo everything else.

7. Mobile touch targets

• Buttons and links are at least 44×44 pixels on mobile, with enough spacing that a user with limited fine motor control doesn't tap the wrong one.

How to test your store

Manual review catches things automated tools miss, and automated tools catch things manual review misses. Use both:

1. Run an automated scan first. Our free AccessScan tool checks your homepage, a product page, and your cart against WCAG 2.2 A/AA rules using axe-core, and flags severity-ranked issues in about a minute. It's a genuinely useful starting point — but automated testing typically catches only 30–40% of real barriers, so treat a clean scan as a floor, not a finish line.
2. Navigate your own site with only a keyboard. Unplug your mouse for ten minutes and try to buy something.
3. Spot-check with a screen reader. VoiceOver ships free on every Mac and iPhone; NVDA is free on Windows. You don't need to be fluent — five minutes on your homepage and checkout will surface obvious problems fast.
4. Re-test after every theme or app update. Accessibility isn't a one-time project. A theme update or a new app can silently reintroduce issues you already fixed.

A quick warning about accessibility widgets

You will see apps in the Shopify App Store promising instant ADA compliance via a single script install — usually a small accessibility icon in the corner of your site with a menu of display adjustments. These are called overlay widgets, and they don't reliably prevent lawsuits. We've written a full breakdown of why accessibility overlay widgets don't work the way they're marketed — worth reading before you install one instead of doing the checklist above.

What remediation actually costs

It depends entirely on how far off your store currently is. A store with a clean, modern theme and a handful of misbehaving apps might need a few days of focused developer time — labelling forms, fixing contrast, auditing apps. A store built on an old, heavily customised theme with dozens of accessibility gaps baked into custom Liquid code is a bigger project, closer to a partial theme rebuild.

Either way, the fix is cheaper than the lawsuit. Legal defence and settlement costs for ADA web accessibility claims routinely run into five figures even when the underlying fix would have taken a developer a week. If you want a scoped estimate, Devmerx builds accessibility into every theme and migration we deliver and can quote remediation work separately if you already have a store.

Frequently Asked Questions

Is Shopify ADA compliant out of the box?

No platform is "ADA compliant" by default, including Shopify. Shopify's checkout and core admin have had accessibility work put into them, but your theme, your content, and every app you install are your responsibility. A default Shopify theme still needs the checklist above applied to your specific store.

Does meeting WCAG 2.2 AA guarantee I won't be sued?

No. WCAG compliance dramatically reduces your risk and gives you a strong legal position if a claim does arrive, but no technical standard is a legal guarantee. Some claims are opportunistic regardless of how compliant a site is. What WCAG conformance does is remove the easy, obvious violations that make a site an easy target in the first place.

Do I need an accessibility statement page?

It's not legally required, but it's good practice. A short page stating your commitment to accessibility, listing the standard you're targeting (WCAG 2.2 AA), and giving a contact method for reporting barriers shows good faith and gives users a channel other than a lawsuit.

How often should I re-check accessibility?

At minimum, after every theme update, every new app install, and every major content push (new collection pages, new landing pages). Many stores set a quarterly reminder to run a full scan even if nothing obvious has changed.

Will fixing accessibility issues slow down my store?

Generally the opposite. Semantic HTML, clean markup, and fewer bloated third-party scripts — the same fixes that improve accessibility — tend to improve page speed too. The two goals rarely conflict.