How to fix aria allowed role on BigCommerce

Steps for BigCommerce

1. In the BigCommerce Control Panel, go to Storefront → My Themes → (active theme) → Advanced → Edit Theme Files.
2. Search for the offending `role` attribute value across your Stencil Handlebars templates (`.html` files under `templates/`).
3. Open the relevant template file and apply the fix: remove the invalid `role`, assign a permitted role, or use the correct native HTML element.
4. Save the file, preview in a test environment, and re-audit with axe DevTools.

What is aria allowed role?

ARIA roles tell screen readers and other assistive technologies what kind of thing an element is — a button, a text field, a navigation landmark, and so on. Every HTML element already has a built-in (native) role, and the ARIA specification only allows certain roles to be layered on top of certain elements. When you attach a role that is not permitted — for example, adding `role="textbox"` to a `<select>` dropdown, a `<div>` that contains a native `<input>`, or any other element where that role is forbidden — the browser and assistive technology receive a contradictory or invalid instruction. The `aria-allowed-role` rule flags exactly these mismatches.

Screen-reader users (who navigate entirely by announced roles) may hear the wrong element type, skip the control entirely, or be unable to interact with it at all — blocking them from completing purchases, filling out forms, or accessing account features. This directly reduces conversions and exposes your store to legal risk under accessibility laws (ADA Title III in the US, EN 301 549 in the EU, AODA in Canada) that reference WCAG 2.x as the standard. Google's crawler also processes accessibility signals, and persistent WCAG violations can undermine your site's credibility in quality assessments. Fixing invalid ARIA is usually a quick code change with zero visible impact on design.

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