All industries » E-commerce accessibility audit

E-commerce accessibility audit: WCAG 2.1 AA on Shopify, WooCommerce, BigCommerce, Magento

E-commerce carries the heaviest ADA Title III lawsuit exposure of any web category. UsableNet's 2024 Year-End Report counted 4,187 federal accessibility cases filed in 2024; roughly 77 percent named online retailers. The platform underneath (Shopify, WooCommerce, BigCommerce, Magento, custom) changes the specific findings but not the lawsuit pattern: same defendant profile, same plaintiff-side firms, same demand-letter-to-settlement path. Site Brace audits any e-commerce site for $149 flat, with a per-platform mix of pages chosen to cover the high-risk surfaces.

The e-commerce lawsuit pattern

The 9th Circuit's 2019 Robles v. Domino's decision held that ADA Title III applies to commercial websites with a nexus to a physical place of business, and that ruling is the foundation of nearly every e-commerce accessibility case since. UsableNet's annual reports document a steady increase: about 2,800 federal cases in 2018, 4,187 in 2024, and a 2025 projection around 5,000. The bulk of these target online retailers because the legal theory is well-established, the screen-reader testing required to document a violation is low-cost for plaintiff-side firms, and most defendants settle rather than litigate.

The defendant profile is consistent across platforms:

• The store has more than $1 million in annual revenue (large enough to be a settlement target, small enough to lack in-house accessibility staff).
• The store has a visible brand and physical operations the plaintiff can document a nexus to.
• The store has at least one obvious WCAG failure on the home page that a screen-reader user can describe in a complaint, often a missing form label or unlabeled image carousel.

Settlement ranges run roughly $10k to $50k for a quiet pre-complaint resolution; $50k to $250k for cases that proceed past the demand-letter stage; six figures and up for litigated cases. Tribeca Skin Care v. accessiBe (2024) is the recent class action where plaintiffs argued they had installed accessiBe based on its compliance claims and were sued anyway. The FTC's April 2025 settlement with accessiBe ($1 million, 20-year consent decree) addresses the marketing of those compliance claims directly.

What an axe-core scan typically finds on an e-commerce site

The platform changes the specific selectors but the rule categories are the same across Shopify, WooCommerce, BigCommerce, Magento, and custom stores.

The first four (contrast, alt text, labels, button names) account for the bulk of findings on most stores. They are also the easiest to fix because the cause is concrete (a hex code, a missing attribute, a wrapper that should be a real button) and the fix propagates through a theme template or product import.

Per-platform notes

Shopify

The largest single source of e-commerce lawsuits. See our Shopify-specific page for theme-level patterns, app-injected ARIA, and Checkout Extensibility considerations.

WooCommerce

WooCommerce inherits accessibility from the WordPress theme and the active plugins. Common patterns: WooCommerce-native checkout (more accessible than legacy themes built on top of it), theme-overridden product loops (often less accessible), and third-party plugin checkboxes for opt-ins or marketing consent (often unlabeled). A WordPress accessibility plugin sometimes makes things worse by adding aria-label on generic elements.

BigCommerce

BigCommerce's hosted checkout has its own accessibility profile (relatively well-maintained). Stencil themes vary; older Cornerstone-based stores tend to ship with the same color-contrast and button-name issues you see on Shopify Dawn-based stores. App injection from the BigCommerce app store creates the same multi-source DOM problem as Shopify.

Magento (Adobe Commerce)

Older Magento stores (Magento 1, Magento 2 pre-2022) often have the most accessibility debt because the surface area is larger and the theme ecosystem is fragmented. Custom Magento storefronts built on PWA Studio or Hyva have a fresh start with newer markup but introduce their own React/Vue componentry that can break keyboard navigation if not built deliberately.

Custom stores

Custom React/Next.js/Remix/SvelteKit e-commerce sites have no platform-level defaults to inherit. They can be the most accessible or the least, entirely depending on the development team. Common pitfalls: client-side routing that does not announce page changes, drawer/modal components without focus management, and "headless" architectures where ARIA is bolted on after the markup is built.

Overlays are not the answer here either

Overlay subscriptions are heavily marketed to e-commerce stores because the lawsuit pressure is real and the value proposition ("install one line of code, become compliant") is appealing. We have written about why accessibility overlays do not actually make sites WCAG-compliant in detail, including the 2025 FTC settlement with accessiBe and the 2022 Murphy v. UserWay class action. For an e-commerce site specifically, the overlay also competes with the app-injected markup from reviews, subscriptions, upsells, and live chat, often producing more violations than it claims to fix.

How Site Brace audits an e-commerce site

The standard page mix for an e-commerce audit covers the high-risk surfaces:

• Homepage
• Two to three collection or category pages (your highest-traffic)
• Three to five PDPs with variant mix (one simple, one variant-heavy, one apparel-with-color, one subscription)
• Cart (drawer and full-page if both exist)
• Account login and account dashboard
• Checkout entry page (the page that triggers the hosted checkout or starts the custom checkout)
• Top content pages (About, Contact, FAQ, Shipping, Returns, Privacy, Terms)

That mix covers up to 25 pages depending on your specific structure. The audit runs axe-core 4.10 against each page, captures element-level screenshots of every contrast failure, and packages the findings into a written report with copy-paste fix code for each issue and 12 re-scans included over 12 months.

Pricing is $149 flat, one-time. To see what the report looks like, view a sample report we built for a fictional DTC apparel brand. The findings, the LLM prompts, and the verification steps are representative of what an e-commerce store report contains.

Start an e-commerce audit, $149

Related:

• Shopify store accessibility - platform-specific patterns and Checkout Extensibility notes
• Free single-page WCAG check
• Why accessibility overlays do not make sites WCAG-compliant
• axe-core vs WAVE vs Lighthouse
• aria-label on a div: why screen readers ignore it