BigCommerce Accessibility in 2026: What Cornerstone Covers, What You Own

Last updated: November 13, 2026. This guide is general information, not legal advice.

A BigCommerce store's accessibility is decided by the layer nobody audits as a single system: the Cornerstone or Stencil theme, whatever Page Builder assembled, the installed apps, and the checkout shoppers complete a purchase through. BigCommerce documents real accessibility work in its reference theme, but the platform doesn't gate what merchants build on top of it — and the law doesn't change because the codebase is Stencil instead of Liquid or PHP.

Key numbers: BigCommerce's developer docs map its Cornerstone reference theme against WCAG 2.1's A, AA, and AAA criteria, but stop short of certifying it at any single conformance level (BigCommerce Developer Center, 2026). In 2026, 95.9% of the top one million home pages carried a detectable WCAG failure, averaging 56.1 errors per page (WebAIM Million, 2026). Ecommerce is named in 69–77% of digital accessibility lawsuits, the largest share of any website category (Seyfarth Shaw). Automated detection covers roughly 60–70% of WCAG issues on any platform; manual testing finds the rest (TestParty platform analysis across 100+ brands). As of 2026, TestParty has remediated 35 million-plus accessibility issues across customer stores.

What decides whether a BigCommerce store is accessible?

Four layers stack to make a BigCommerce store — the Stencil theme, whatever Page Builder assembled, installed apps, and checkout — and BigCommerce controls the frame, not the assembly a shopper uses.

BigCommerce ships Stencil and documents accessibility guidance for it in more detail than most SaaS platforms bother with: Cornerstone, its reference theme, is mapped criterion by criterion against WCAG 2.1 in BigCommerce's own docs. That's the floor. What a shopper experiences is whatever was built inside it — a customized Cornerstone build, or a marketplace theme with no comparable documentation; Page Builder pages; installed apps; and a checkout customized within, or beyond, BigCommerce's limits.

None of the laws a merchant answers to care which layer produced the failure. WCAG 2.2 Level AA is the practical benchmark under ADA Title III, the EAA, and Ontario's AODA alike, regardless of platform. For the platform-agnostic version, see our ecommerce accessibility guide.

How accessible is Cornerstone and the Stencil ecosystem?

Cornerstone is the most accessibility-documented default theme of any major ecommerce platform — mapped against WCAG 2.1's A, AA, and AAA levels by component — but documented isn't the same claim as compliant, and marketplace themes on the same Stencil framework carry no comparable guarantee.

BigCommerce's guidance is specific: Level A covers alt text and a skip-to-main option; Level AA adds 4.5:1 contrast and multiple ways to find content; Level AAA adds 7:1 contrast and breadcrumb wayfinding. That's more transparency than most platforms publish about a reference theme — and it's scoped to Cornerstone alone. The Theme Marketplace sells hundreds of Stencil-built themes from independent studios, none held to that mapping before listing.

Before buying a marketplace theme, run this on its public demo store — about 10 minutes:

A theme that fails all three isn't disqualified — most will — but it tells you what your remediation budget is buying before you commit.

Where do BigCommerce stores fail audits?

BigCommerce audits fail in a consistent handful of places regardless of theme: faceted search, product options, quick-view modals, carousels, app-injected UI, and checkout errors.

• Faceted search. Facets often render as plain links with no indication a filter is active, and result counts update silently with no live region announcing the change.
• Product options and swatches. Color and size options commonly ship as styled `<div>` elements with a background-image, not a form control with an accessible name.
• Quick-view modals. The single most common focus trap in TestParty's audits of BigCommerce catalogs: focus never moves into the modal, or never returns to the trigger on close.
• Carousels. Auto-advancing carousels with no pause control violate WCAG's Pause, Stop, Hide criterion, and slide changes go unannounced to a screen reader.
• App-injected UI. Reviews widgets and upsell popups from the App Marketplace inject front-end code with no accessibility review before listing.
• Checkout errors. A rejected field shows a red border alone, with no text explanation tied to the field.

Quick-view and faceted search are the surfaces Cornerstone's documentation doesn't resolve, since both depend on merchant configuration, not the base theme. See our breakdown of the most common WCAG violations for how these rank against home-page-only data.

How do you fix a Stencil theme?

Fixing a Stencil theme means editing the Handlebars templates, SCSS, and JavaScript inside the theme's own files — durable only if the fix lives in a proper theme edit, not a runtime script layered on top.

A Stencil theme bundles Handlebars templates, SCSS partials, and front-end JS. A missing accessible name on a facet checkbox is usually a small template change:

{{!-- templates/components/facets.html — adds the accessible name BigCommerce's default facet markup omits --}}
{{!-- Fixes WCAG 4.1.2 (Name, Role, Value) and 1.3.1 (Info and Relationships) --}}
<label for="facet-{{this.id}}" class="facetedSearch-label">
  <input type="checkbox" id="facet-{{this.id}}" name="{{this.name}}"
    {{#if this.isSelected}}checked aria-pressed="true"{{/if}}>
  {{this.label}} ({{this.count}})
</label>

A quick-view focus trap is a similarly contained JS fix:

// assets/js/theme/quick-view.js — moves focus in on open, restores it on close
// Fixes WCAG 2.1.2 (No Keyboard Trap) and 2.4.3 (Focus Order)
function openQuickView(trigger) {
  lastFocused = trigger;
  modal.hidden = false;
  modal.querySelector('[data-quick-view-close]').focus();
}
function closeQuickView() {
  modal.hidden = true;
  lastFocused.focus();
}

Both changes live in the theme's own files, not a third-party script — the same principle behind source-code remediation on any platform. Stencil themes version as a whole package, so the durability risk is applying a marketplace update, or restoring an older version, without carrying the fix forward.

On a headless Catalyst storefront, the same defects move into React components — the facet checkbox becomes a component prop, the focus trap a `useEffect` hook. The violations relocate; they don't disappear.

What about BigCommerce's checkout?

On BigCommerce's default Optimized One-Page Checkout, merchants can restyle nearly everything through the theme's `optimized-checkout.scss` file but cannot change the underlying HTML structure or rename classes. BigCommerce's own docs state that limit directly, since each class maps to multiple checkout elements the platform needs to keep stable.

That cuts a specific way: SCSS fixes contrast and typography, but can't add a missing label or restructure a confusing error message. Teams needing that control use BigCommerce's Checkout SDK to build a fully custom checkout instead — full markup control, and full accessibility responsibility, with none of BigCommerce's template inherited.

Either way, the audit that finds what matters isn't a homepage scan — it's a full keyboard and screen-reader walkthrough of the purchase path. For the patterns that pass at each stage, see our guide to building an accessible ecommerce website.

What's the compliance sequence?

The sequence that holds up runs in order: audit the full purchase path, remediate in source at the template level, produce documentation buyers ask for, then monitor continuously.

Automated scanning finds roughly 60–70% of issues in a day; it won't tell you whether a swatch's state gets announced or a checkout error gets read aloud, which is what the manual pass is for. Fix at the template level first — one corrected facet template clears the defect across every page rendering it — with a realistic 14-day window for a well-scoped store's highest-traffic templates. Running axe-core against those templates on every deploy turns a one-time fix into one that stays fixed.

BigCommerce's B2B base makes documentation less optional than on a purely direct-to-consumer platform: wholesale buyers increasingly request an Accessibility Conformance Report as routine procurement. Our ACR guide covers which VPAT edition to file under. Daily automated scans plus a monthly manual pass — targeting Lighthouse 90+, five or fewer WAVE errors, three or fewer axe errors — keeps that result true after the next Page Builder edit or app install.

Do accessibility apps in the BigCommerce marketplace solve it?

No — the App Marketplace carries the same category of overlay-script apps sold on every ecommerce platform, and the evidence against them is category-wide, not specific to any one storefront.

Based on TestParty's analysis of Court Listener public records, more than 1,000 businesses running overlay widgets were named in lawsuits in 2024 — a pattern showing up regardless of whether the store runs Stencil, Liquid, or PHP. In April 2025 the FTC finalized a $1 million order and a 20-year consent decree against accessiBe specifically. A script layered over the DOM doesn't rewrite the Handlebars template or React component an auditor parses. Our full breakdown of overlay mechanics covers the evidence.

Marketplace "accessibility checker" apps are a more honest category — scanners that flag problems without fixing them. A checker can surface a missing alt attribute; it can't write one that describes the product, or judge whether a modal traps focus.

Frequently Asked Questions

Is Cornerstone WCAG compliant out of the box? BigCommerce's docs map Cornerstone's components against WCAG 2.1's A, AA, and AAA criteria in detail, but don't certify it as conformant at any level. Treat it as a well-documented starting point, not a finished audit.

Does BigCommerce publish a VPAT for its own platform? BigCommerce publishes theme-level WCAG guidance, but no public platform-wide VPAT or ACR was identifiable as of 2026. That's separate from whether your store needs one — B2B buyers ask sellers for an ACR describing the storefront, not BigCommerce itself.

Can I fully customize the default checkout for accessibility? Only through SCSS styling — BigCommerce restricts changing the checkout's HTML structure or class names. Teams needing markup-level fixes move to a custom build on the Checkout SDK instead.

Is Catalyst more accessible than a Stencil theme? Not automatically. Catalyst's React and Next.js foundation names accessibility as a design goal, but BigCommerce calls it visually unopinionated — the result still depends on how a team assembles it.

How much of BigCommerce accessibility can be automated? Roughly 60–70%, consistent with any platform. Scanners catch missing alt attributes and contrast issues; they can't judge whether a facet's state is announced or a modal traps focus.

Will a marketplace accessibility app protect my store from a lawsuit? No. Overlay apps change how a page behaves in the browser without touching the markup a plaintiff's expert tests, and more than 1,000 businesses running these widgets were named in lawsuits in 2024 (TestParty analysis of Court Listener records).

Like everything at TestParty, this article reflects our cyborg philosophy: AI handles the heavy lifting, humans bring the expertise. The data and opinions here are based on publicly available sources as of publication. TestParty is a participant in the accessibility market — we believe in transparency, so we encourage you to cross-reference our claims and evaluate all options for your business.