Shopify Checkout Accessibility in 2026: What You Can Actually Fix

Last updated: September 30, 2026

Only 11% of cart and checkout pages meet minimum WCAG standards, which leaves roughly 89% failing — and on Shopify, most of those failures sit in code merchants own, not in the checkout Shopify renders. Since `checkout.liquid` was retired, the platform handles the core payment flow and publishes a conformance report for it. The risk moved upstream to the cart, and sideways into extensions and apps.

Key numbers: Only 11% of cart and checkout pages meet minimum WCAG standards, and inaccessible checkouts cost retailers an estimated $2.3 billion a year (AccessibilityChecker.org, 2025 eCommerce Accessibility Study). Shopify's checkout accessibility conformance report — the March 2026 edition, replacing June 2025 — evaluates checkout against WCAG 2.0, 2.1 and 2.2 Level A and AA, and lists several criteria as "partially supports." Ecommerce businesses are named in 69–77% of website accessibility lawsuits (Seyfarth Shaw). Low-contrast text appeared on 83.9% of home pages in February 2026 (WebAIM Million) — the same styling decisions that flow into checkout branding.

Why is checkout the highest-stakes accessibility surface?

Checkout is where an accessibility defect stops being an inconvenience and becomes a denial of service: a blocked checkout is a blocked purchase, and that is the cleanest damage theory a plaintiff's firm can plead.

Everywhere else on a store, a barrier is arguable: a shopper who cannot operate your filters can still browse the collection. But a shopper who cannot complete payment has been excluded from the transaction itself — on a date, with a cart value attached. That combination of a specific person, a specific attempt, and a documented failure to buy is why checkout shows up in so many demand letters.

The financial case runs parallel. The 2025 eCommerce Accessibility Study put annual losses from inaccessible checkouts at roughly $2.3 billion — abandonment, not litigation, revenue that left before anyone filed anything.

What does Shopify's checkout give you in 2026?

Shopify's platform-rendered checkout is the strongest-tested surface in a typical store, and Shopify publishes a conformance report for it — but "strongest-tested" is not the same as "conformant," and the report says so.

The March 2026 edition of Shopify's checkout accessibility conformance report evaluates checkout against WCAG 2.0, 2.1, and 2.2 at Levels A and AA. Most criteria are marked "supports"; a meaningful minority are marked "partially supports," including focus order on the primary call to action not matching visual presentation, insufficient contrast in some text labels and input borders, focus rings that are inconsistent or invisible in some themes, form labels that can become hidden at high zoom, and barriers introduced by third-party payment controls. Shopify describes its testing as daily automated checks, annual manual review against its internal checklist, and quarterly usability testing with people with disabilities.

Read those exceptions closely, because two of them — focus ring visibility "in some themes" and third-party payment controls — are yours, not Shopify's.

What can you customize in Shopify checkout by plan?

Since `checkout.liquid` was retired, no plan can edit checkout markup directly. What each tier can change is narrow, well-documented, and almost entirely about styling and inserted blocks.

Shopify sunset `checkout.liquid` in stages: the information, shipping, and payment steps in August 2024, then the Thank you and Order status pages on August 28, 2025, with script tags on those pages sunsetting for non-Plus stores on August 26, 2026. Everything since runs through checkout extensibility.

The last row is the one merchants misread as safety. You cannot fix Shopify's checkout, but you also cannot break it — except through the two levers you do hold: branding and extensions.

Where do merchant-added elements break Shopify checkout?

Branding is the quiet failure mode. A brand palette that fails contrast on the storefront fails identically inside checkout, because the checkout editor applies your colors to Shopify's accessible components.

This is the most common checkout finding in our work: a button color, an input border, or a "secondary" link that clears contrast against a mockup background and fails 4.5:1 against the live one. WebAIM found low-contrast text on 83.9% of home pages in February 2026, and the same tokens usually travel straight into the checkout editor. Contrast is cheap to detect and slow to fix, because the change is a brand decision, not a CSS edit.

Extensions are the loud failure mode. Anything added through checkout extensibility — a delivery-instructions field, a gift-note input, a subscription toggle, an in-checkout upsell — is merchant code running in Shopify's sandbox, and Shopify's conformance report does not cover it. In audits of migrated stores the recurring pattern is a field ported from old `checkout.liquid` code with a placeholder instead of a programmatic label (3.3.2 Labels or Instructions), an upsell block that changes the total with no status announcement (4.1.3), and a validation message rendered as red text with no association to its input (3.3.1). Express payment buttons need their own check: restyled wallet buttons routinely lose their focus indicator (2.4.7) and drop below the 24×24 CSS pixel minimum in WCAG 2.2's 2.5.8 Target Size.

Why is the cart usually worse than the checkout?

The cart page and cart drawer are 100% merchant-controlled theme code, which makes them consistently the weakest link in the purchase path — a shopper blocked in the cart never reaches Shopify's tested checkout at all.

When we test a Shopify purchase path end to end, the first blocker is almost never inside checkout. It is the drawer that opens without moving focus into it, leaving a screen reader user reading the collection page underneath while a dialog they cannot perceive sits on top. Four cart defects recur across nearly every audit:

• Quantity steppers built from unlabeled `+` and `−` buttons, with the new quantity never announced (1.1.1, 4.1.3, and often 2.5.8 on mobile).
• Remove buttons labeled only by an icon or by the word "Remove" repeated eight times, giving no way to tell which line item disappears (2.4.4, 2.4.6).
• Promo-code fields with placeholder-only labeling and an invalid-code error shown by color alone (3.3.2, 3.3.1, 1.4.1).
• Drawer focus management with no focus trap, no `Escape` to close, and no return of focus to the trigger button on close (2.4.3, 2.1.2, 2.4.11).

None of this is exotic. It is default theme behavior: Theme Store requirements cover only 16–22% of WCAG success criteria by TestParty's analysis, which is why our theme audits find 30–100 violations in a stock Dawn install and 100–350 in premium themes. Fixing the cart is theme work, and it belongs in the same sprint as any checkout project. The layer-by-layer mapping is in our guide to Shopify WCAG compliance.

Which barriers appear at each step of the purchase path?

Map violations to the step where a shopper actually encounters them, then to the party who can fix them. Ownership is what turns an audit finding into a ticket someone can close.

How do you test a Shopify checkout end to end?

Checkout testing is manual by definition: place a real order with a keyboard only, then place another with a screen reader, and deliberately trigger errors at each step. Automated scanners cannot log in, cannot pay, and cannot judge whether an error message is recoverable.

Run the keyboard pass first. Start at a product page, add to cart, and never touch the mouse. Confirm that focus enters the cart drawer, that `Escape` closes it and returns focus to the trigger, that every express wallet button shows a visible focus indicator, and that you can reach and operate the continue button at each step. Then repeat with VoiceOver or NVDA, listening for three things: whether each field's label and purpose are announced, whether subtotal and shipping-rate changes are announced as status messages, and whether a deliberately invalid postal code produces an error that is announced, tied to its field, and correctable.

Express wallets need their own script because they bypass your form entirely. Test Shop Pay, Apple Pay, Google Pay, and PayPal separately: keyboard access into the sheet, focus visibility inside it, and behavior on cancel — several implementations dump focus back to the top of the document. Shop Pay's one-time code flow is worth checking against WCAG 2.2's 3.3.8 Accessible Authentication, which prohibits cognitive function tests without an alternative.

Automated detection covers roughly 60–70% of issues in TestParty's audits; the remaining 30% concentrates in exactly this flow. The broader methodology is in our Shopify accessibility audit walkthrough.

How do checkout barriers show up in ADA lawsuits?

Ecommerce absorbs 69–77% of website accessibility lawsuits (Seyfarth Shaw), and checkout is the surface most often described in the complaint itself — because it is the point where the plaintiff can allege they were unable to complete a purchase.

Demand letters follow a pattern: a list of automated findings across the storefront, then a narrative paragraph about the attempted transaction. The first part is generated; the second is what raises the settlement number. Documentation is the counterweight. In TestParty's work, the stores that resolve these matters cheaply are the ones that can produce a dated audit of the purchase path, a remediation log, and evidence of ongoing testing — Dorai Home settled a demand for $2,000 against an initial $74,999 ask. In the history of the company, fewer than 1% of TestParty customers have been named in an accessibility lawsuit while on the platform. Overlay widgets are not the shortcut: based on TestParty's analysis of Court Listener records, more than 1,000 businesses with widgets installed were sued in 2024, and a widget cannot reach into a sandboxed checkout extension anyway. The wider pattern is covered in our guide to ecommerce ADA compliance.

What should you fix first on your plan?

Priority order is the same on every tier for the first two items, because both live in theme code that every merchant controls regardless of plan.

All plans, in order: (1) Fix cart drawer focus management, quantity steppers, remove buttons, and promo-code labeling — this is where shoppers are actually blocked. (2) Audit checkout branding against 1.4.3 and 1.4.11 in the live checkout, not in a design file; adjust the tokens that fail. (3) Restore visible focus indicators and adequate target sizes on express payment buttons. (4) Keyboard-test every thank-you and order-status extension you have installed.

Shopify Plus, additionally: treat every checkout UI extension as untested until it has passed keyboard and screen reader review inside live checkout. Extensions ported during the `checkout.liquid` migration are the highest-yield place to look — they were moved for functional parity and almost never re-tested for accessibility.

For the full store-wide sequence — theme, apps, content, checkout, custom code — see our Shopify ADA compliance guide, and for the criteria that matter most across ecommerce generally, our breakdown of WCAG for ecommerce.

Frequently Asked Questions

Can I edit Shopify's checkout code to fix accessibility issues? No. `checkout.liquid` was retired across 2024 and 2025, and no plan can edit checkout markup, field labels, inline error text, or `autocomplete` attributes. Those belong to Shopify. What you can change is branding on all plans, checkout UI extensions on Shopify Plus, and thank-you and order-status extensions on all plans except Shopify Starter.

Does Shopify's checkout conformance report cover my store? Only the base checkout Shopify renders. The March 2026 report evaluates Shopify's own checkout against WCAG 2.0, 2.1, and 2.2 Level A and AA. Your theme, your cart, your apps, your branding choices, and any checkout UI extension you install are merchant code and sit outside its scope entirely.

If Shopify renders checkout, am I still liable for it? Yes. ADA Title III claims name the business operating the store, not the platform. Shopify's own accessibility documentation is explicit that merchants are responsible for their store's accessibility. The practical consequence: you defend the surfaces you control, and the cart is one of them.

Will an accessibility overlay fix my checkout? No. Overlays inject JavaScript into pages they can reach; sandboxed checkout extensions and Shopify's own checkout are not among them. Based on TestParty's analysis of Court Listener records, more than 1,000 businesses with widgets installed were named in accessibility lawsuits in 2024.

How long does it take to remediate a Shopify purchase path? The cart and theme layer is where the work lives, and TestParty's initial remediation typically completes in 14 days, targeting Lighthouse 90+, WAVE 5 or fewer errors, and axe 3 or fewer. Extension review adds time proportional to how many custom blocks the store runs in checkout.

Which WCAG criteria matter most in a checkout flow? 3.3.1 Error Identification, 3.3.2 Labels or Instructions, and 1.3.5 Identify Input Purpose govern the forms; 1.4.3 and 1.4.11 govern contrast; 2.4.3, 2.4.7, and 2.4.11 govern focus; 4.1.3 governs announcements when totals change; and WCAG 2.2 adds 2.5.8 Target Size, 3.3.7 Redundant Entry, and 3.3.8 Accessible Authentication.

Humans + AI = this article. TestParty uses a cyborg approach to content — combining human accessibility expertise with AI capabilities to produce accurate, comprehensive guides. This content is for educational purposes and reflects our analysis of publicly available information as of the publication date. TestParty competes in the digital accessibility market, and we encourage readers to evaluate all solutions independently based on their specific needs.