BigCommerce WCAG 2.2 Checker

WCAG 2.2 for BigCommerce Sites

WCAG 2.2 became a W3C Recommendation in October 2023. It keeps every WCAG 2.1 requirement except 4.1.1 Parsing and adds six success criteria at Level A and AA, mostly about people with low vision, motor disabilities and cognitive disabilities. A BigCommerce site that meets WCAG 2.2 AA also meets 2.1 AA and 2.0 AA.

This checker runs the same free scan as the BigCommerce accessibility checker with the WCAG 2.2 AA preset, so the results include the 2.2 rules that automated testing can check.

On BigCommerce stores, WCAG 2.2 failures cluster in the purchase path: small quantity buttons and swatches (target size), sticky add-to-cart bars that cover focused fields, and checkouts that ask for an address twice. Test the cart and checkout by hand as well as scanning product pages.

Who Should Run the BigCommerce WCAG 2.2 Checker

• BigCommerce site owners who want the most current, future-proof target.
• Teams redesigning a BigCommerce site, where adopting the latest version costs little extra.
• Organizations selling into the EU, where EN 301 549 V4.1.1 now uses WCAG 2.2.
• Anyone preparing for new rules, which tend to adopt the latest WCAG version.

The New WCAG 2.2 Criteria to Check on BigCommerce

• 2.4.11 Focus Not Obscured (Minimum)

  Sticky headers, cookie banners and chat widgets must not completely hide the element that has keyboard focus.

• 2.5.7 Dragging Movements

  Anything that works by dragging, such as sliders, carousels and sortable lists, needs a single-pointer alternative.

• 2.5.8 Target Size (Minimum)

  Buttons and links need a target of at least 24 by 24 CSS pixels, or enough space around them. Icon buttons and pagination links often fail.

• 3.2.6 Consistent Help

  Help such as a contact link or chat must appear in the same place on every page that has it.

• 3.3.7 Redundant Entry

  Do not ask for the same information twice in one process, such as shipping and billing addresses, without offering to fill it in.

• 3.3.8 Accessible Authentication (Minimum)

  Sign-in must not depend on a cognitive test, such as remembering a password without paste support or solving a puzzle.

Where BigCommerce Sites Usually Fail WCAG 2.2

These problems come up again and again on BigCommerce sites, and each one fails WCAG 2.2. The BigCommerce accessibility checker explains how to fix them in BigCommerce.

• Product options and swatches. Swatch and radio-style options that are restyled with CSS can lose their visible focus ring or their label, so shoppers cannot tell which option is selected.
• Faceted search filters. Filter lists on category and search pages update the results without telling screen reader users how many products remain, and collapsible filter groups often ignore the keyboard.
• Quick view and cart preview dialogs. Modal windows that do not take focus when they open, or do not return it when closed, strand keyboard users behind them.
• Script Manager additions. Chat widgets, cookie banners, review badges and pop-ups added through Script Manager load on every page, so one inaccessible script affects the whole store.
• Images in Page Builder. Banners and promotional tiles added in Page Builder with no alt text, or with text baked into the image, hide offers from screen reader users.

Worried about ADA claims as well? The BigCommerce ADA compliance checker covers the BigCommerce risks behind most complaints.

What to Test by Hand on BigCommerce

Automated testing finds many, but not all, WCAG 2.2 failures. Check these yourself after the scan:

1. Tab through each page and check the focused element is never fully covered by sticky content (2.4.11).
2. Try every drag interaction with a single click or tap instead (2.5.7).
3. Sign in with a password manager and check paste works (3.3.8).
4. Rescan after each fix. Continuous monitoring rescans up to 500 URLs per domain daily and keeps a dated record in the Compliance Vault.

Start 3-day free trial

Related Guides

• WCAG 2.2 AA CheckerThe WCAG 2.2 standard in full, for any website.
• WCAG 1.1.1 Non-text Content Explained in Plain EnglishWCAG 1.1.1 Non-text Content explained simply: how to write alt text for every kind of image, icon, chart and CAPTCHA, with code examples and a test routine.
• WCAG 4.1.2 Name, Role, Value Explained in Plain EnglishWCAG 4.1.2 Name, Role, Value explained simply: give every control a name, role and state with native HTML and ARIA, with code examples and how to test.
• Keyboard Accessibility TestingA practical guide to keyboard accessibility testing: what to check, the exact keys to use, and a component-by-component reference table mapped to WCAG.
• WCAG Success Criteria LibraryLook up any criterion the scan flags, in plain language.

BigCommerce WCAG 2.2 Checker: Frequently Asked Questions