How to fix aria valid attr on WooCommerce

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 WooCommerce

  1. In your WordPress admin, go to Appearance → Theme File Editor (or use a code editor like VS Code connected via FTP/SFTP).
  2. Search your active theme's files (especially `header.php`, `footer.php`, `functions.php`, and any custom page templates) for the misspelled attribute using a global find (Ctrl+Shift+F in VS Code).
  3. Also search any active plugins' output — if the invalid attribute comes from a plugin, update the plugin first; if it persists, contact the plugin developer.
  4. Correct every instance of the misspelled attribute and save the file.
  5. If you use a page builder (Elementor, Divi, WPBakery), open the affected page in the builder and look for any custom HTML/code blocks containing the invalid attribute, then correct it there.
  6. Flush any caching plugin (e.g. WP Rocket, W3 Total Cache) after saving, then re-scan with axe DevTools.
Official WooCommerce documentation ↗

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 WooCommerce 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

Fix aria valid attr on another platform