How to fix aria valid attr on BigCommerce
Find and replace every misspelled or non-existent ARIA attribute name (e.g. `aria-labeledby`) with the correct, spec-defined name (e.g. `aria-labelledby`) across your entire site's HTML and templates.
Steps for BigCommerce
- In your BigCommerce admin, go to Storefront → Themes → (your active theme) → Advanced → Edit Theme Files.
- Use the search functionality or download the theme as a ZIP file and open it in a code editor (VS Code) to run a global search for the misspelled attribute (e.g. `aria-labeledby`).
- Locate the relevant template files (commonly in `templates/components/`, `templates/layout/`, or `templates/pages/`) and correct the attribute name.
- If using Stencil CLI locally, run a global find-and-replace, then `stencil push` to deploy the corrected theme.
- For issues inside a third-party widget or script injected via Script Manager (Storefront → Script Manager), edit the script directly in the Script Manager editor.
- After deploying, verify using the axe DevTools browser extension on a live storefront page.
What is aria valid attr?
ARIA (Accessible Rich Internet Applications) attributes are special HTML attributes — like `aria-label`, `aria-labelledby`, or `aria-hidden` — that tell screen readers and other assistive technologies what an element is and how it behaves. Every valid ARIA attribute has an exact, officially defined name. An "invalid ARIA attribute name" means your HTML contains an ARIA attribute that doesn't exist in the official specification — most commonly a typo like `aria-labeledby` (one 'l' instead of two) instead of `aria-labelledby`. Because the attribute name is wrong, the browser and assistive technology silently ignore it entirely, as if it were never there.
When an ARIA attribute name is misspelled, screen readers receive no accessibility information from it — the element appears unlabelled or unidentifiable to blind and low-vision shoppers. This directly harms the shopping experience for millions of people with disabilities and puts your store at legal risk under laws like the ADA (US), AODA (Canada), EAA (EU), and Equality Act (UK), all of which reference WCAG 2.x conformance. Accessibility lawsuits targeting online stores have increased sharply year over year, and a simple typo is exactly the kind of findable, actionable violation that appears in demand letters. Fixing it is quick and meaningfully improves usability for customers using assistive technology, which can also improve conversion rates in that segment.
See the complete Aria valid attr 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 valid attr and every other issue across your whole site.
Scan my site free