How to fix aria roles on BigCommerce

Audit every element that has a `role` attribute and replace any invalid or misspelled role value with a valid WAI-ARIA role from the official specification.

Steps for BigCommerce

  1. In BigCommerce Admin, go to Storefront → Themes → click Customize on your active theme, then Advanced → Edit Theme Files.
  2. Use the file browser to search template files (`.html` Handlebars templates) for `role=` — check `templates/layout/base.html`, `templates/components/`, and `templates/pages/`.
  3. Correct the invalid role value in the appropriate file and save.
  4. For Stencil CLI users: edit the same files locally in your theme directory, then run `stencil push` to deploy.
  5. If the issue is in a BigCommerce widget or app, update the widget HTML in Page Builder (Content → Page Builder) or contact the app vendor.
  6. Preview and re-run axe to confirm the fix.
Official BigCommerce documentation ↗

What is aria roles?

The `role` attribute tells assistive technologies (screen readers, braille displays, voice control software) what kind of interface element something is — for example, a button, a navigation landmark, a dialog, or a list. The WAI-ARIA specification defines an exact list of allowed role names. If any element on your store carries a role that isn't on that list — whether it's a typo like `role="buton"`, an invented name like `role="product-card"`, or an outdated value like `role="presentation"` used incorrectly — the browser and screen reader simply ignore it or misinterpret the element entirely. WCAG Success Criterion 4.1.2 (Name, Role, Value) requires that every user interface component exposes a valid, programmatically determinable role so all users can understand and operate it.

Screen reader users — who include people with visual impairments, motor disabilities, and cognitive disabilities — rely on role information to navigate and interact with your store. An invalid role means those customers hear confusing or missing announcements, cannot identify interactive controls, and may abandon your checkout or product pages. Beyond lost conversions, accessibility failures carry real legal risk: WCAG 2.1 AA compliance is referenced in ADA Title III lawsuits and, in many jurisdictions, is a statutory requirement for online businesses. Google also uses accessibility signals as a quality factor, so pages riddled with invalid ARIA can indirectly suppress organic rankings. Fixing invalid roles is typically a quick code change with outsized impact on both compliance and customer experience.

See the complete Aria roles guide for every platform and the full background.

Not sure if your BigCommerce store has this?

Run a free SEOLZ scan — we’ll find aria roles and every other issue across your whole site.

Scan my site free

Fix aria roles on another platform