EAA compliance for BigCommerce: WCAG 2.1 AA checklist & fixes

What the EAA actually requires from a BigCommerce site

BigCommerce ships the strong default Cornerstone theme, so under the EAA the obligation concentrates on custom Stencil theme overrides, the page builder, and third-party apps rather than the platform baseline. EN 301 549 conformance forces you to fix Stencil CSS that blanks focus outlines (the most common finding), page-builder text-on-image promotional banners that fail 4.5:1, and quick-view modals from apps that trap focus or skip Esc handling. If you run the headless Catalyst (Next.js-based) option, the requirement shifts entirely into your own codebase, mirroring a Next.js audit.

BigCommerce targets mid-market and enterprise merchants, so in-scope BigCommerce stores are frequently higher-revenue B2C operations where turnover-percentage penalties like France's up-to-4% become a real financial threat rather than a token fine. Many also run B2B alongside B2C, bringing the EAA's later B2B-services transition into play. As with any larger retailer, the practical exposure combines the fine itself with the significant revenue impact of an enforced remediation order during trading, so accessibility neglect scales into a material commercial risk.

Remediation is done by a Stencil-capable theme developer working in SCSS and Handlebars templates, or by the front-end team for a Catalyst headless build. The baseline move is enforcing a focus-visible outline theme-wide in the Stencil SCSS so no override can silently kill it, fixing banner contrast in the page builder, and reviewing app-injected modals for focus handling. Always audit the published storefront rather than the preview, and for mid-market stores this is a planned developer engagement with regression checks after theme changes.

Top WCAG failures we see on BigCommerce sites

Across hundreds of BigCommerce scans, the same handful of issues show up over and over. None of them require ripping the theme apart — most are fixable in a few hours by someone comfortable in the platform's editor or template files.

• Stencil theme overrides removing focus styles

  Custom CSS that blanks outlines is the #1 audit finding.

  2.4.7 — Level AA

• Page builder text contrast on sale banners

  Text-on-image promotional banners regularly fail 4.5:1.

  1.4.3 — Level AA

• Quick-view modal focus management

  Some apps trap focus or skip Esc handling.

  2.1.2, 2.4.3

Concrete code fixes for BigCommerce

Below are copy-paste fixes for the most common BigCommerce issues. They assume you have access to your theme code or the platform's custom-code injection panel. If you cannot edit code directly, share these snippets with whoever maintains the site — every one of them is a ten-minute change.

// In assets/scss/_focus.scss, then import into theme.scss
:where(button, a, input, [tabindex]):focus-visible {
  outline: 2px solid #1e1e1e;
  outline-offset: 2px;
}

Tools and plugins worth installing first

• BigCommerce Audit panel

• Stencil CLI for local theme work

How to scan a BigCommerce site without missing anything

Automated scanners catch about 30–40% of WCAG issues; the rest need manual review. The good news is that the 30–40% includes the most expensive issues to remediate after the fact, so an automated scan is the cheapest way to get unstuck. Run one before you change a line of theme code.

• Always audit the published storefront, not the preview.