Skip to content

Shopify accessibility, audited and fixed against WCAG 2.2.

When you need it

When does a storefront need an accessibility audit?

  • A customer, retailer or lawyer has raised an accessibility concern.
  • An overlay widget is installed, but nobody has tested the theme itself.
  • Menus, filters or variant pickers can’t be used with a keyboard alone.
  • A redesign or a new theme is about to launch.
  • Nobody owns accessibility, so each campaign page adds new issues.
How we do it

How does an accessibility audit run?

  1. 01Agree the scopeTemplates, journeys and apps to test, from home page to cart.
  2. 02Test by handKeyboard, screen readers, zoom and contrast, alongside automated scans.
  3. 03Report against WCAGEach issue tied to a WCAG 2.2 success criterion, ranked by severity.
  4. 04Fix the themeChanges in the theme code, not an overlay, highest-impact barriers first.
  5. 05Retest and protectRetest the fixes, then add checks so new releases don’t regress.
What you receive

Barriers found, fixed and kept out

  • An audit mapped to WCAG 2.2 AA success criteria
  • Issues ranked by severity and by template
  • Fixes made in the theme code itself
  • A retest record for every fixed issue
  • Accessible patterns for components your team reuses
  • Automated checks added to your release process
Pitfalls we avoid

What usually goes wrong.

  • Relying on an overlay widget. Overlays don’t change the code, so barriers remain.
  • Trusting automated scans alone. Scans miss many issues; test with keyboard and screen readers.
  • Treating the audit as a one-off. New sections and apps bring new issues; check every release.
  • Ignoring the apps on the page. Third-party widgets count too; test them with the theme.
Before any build

Every engagement starts with the Architecture Review.

Three weeks, a fixed fee, and a roadmap your team can act on.

Book an Architecture Review
  • A written report: architecture map, findings ranked by impact
  • A sixty-minute readout with your leadership team
  • A fixed-fee proposal for the first phase, if you want one
Questions

What teams ask about Shopify accessibility.

Is accessibility required for ecommerce sites?

That’s a question for your counsel. We don’t give legal advice, and no audit can promise a site won’t receive a claim. What we do is audit your storefront against WCAG 2.2 AA, fix what we find and keep a record of the work.

Do accessibility overlay widgets work?

Not as a fix. An overlay adds a layer on top of the page but leaves the theme code unchanged, so the barriers for keyboard and screen reader users remain. Some get in the way of the assistive technology people already use. We fix the code instead.

What does an accessibility audit include?

Manual testing with a keyboard, screen readers, zoom and contrast checks, plus automated scans, across your key templates and the apps on them. Each issue is tied to a WCAG 2.2 success criterion, ranked by severity and paired with a recommended fix.

How do you keep a theme accessible after launch?

We build components on accessible patterns your team reuses, add automated checks to the release process and retest when sections or apps change. With an Engineering Partnership, accessibility becomes part of every release rather than an occasional audit.

What changed in WCAG 2.2?

It added criteria for focus that isn’t hidden by sticky elements, minimum target sizes, alternatives to dragging, sign-in that doesn’t rely on memory tests, consistent help, and not asking for the same information twice. Sticky headers, sliders and sign-in forms are the first places we check.

Start here

Find out where your storefront stands

Book an Architecture Review with accessibility as the priority. We audit against WCAG 2.2 AA, then price each phase of fixes in writing.