How to fix aria prohibited attr on WooCommerce

Steps for WooCommerce

1. Access your WordPress Admin → Appearance → Theme File Editor (or use a plugin like Advanced Code Editor for syntax highlighting).
2. Locate the theme file containing the flagged element — typically header.php, content-product.php, or a block template in /templates/.
3. Search for the prohibited ARIA attribute and correct it as described in the generic steps.
4. If the attribute is injected by a plugin (e.g. a slider or mega-menu plugin), check that plugin's settings panel or custom CSS/JS area for the offending markup, or contact the plugin author.
5. Save, then validate with the axe DevTools browser extension on the frontend.

What is aria prohibited attr?

ARIA (Accessible Rich Internet Applications) is a set of special HTML attributes like `aria-label`, `aria-checked`, or `aria-expanded` that tell screen readers and other assistive technologies what an element is and how it behaves. However, every ARIA role — and every native HTML element that maps to a role — has a defined list of attributes it is allowed to use. Putting a prohibited ARIA attribute on an element is like giving a screen reader contradictory instructions: for example, adding `aria-checked` to a plain `<div role="heading">` makes no sense and causes confusion. The WCAG 4.1.2 success criterion requires that all user interface components have names, roles, and values that can be programmatically determined, which means the attributes must be valid for the element's role.

Screen readers (used by millions of people who are blind or have low vision) rely on ARIA attributes to announce what a control does and its current state. When a prohibited attribute is present, screen readers may announce garbled, incorrect, or completely missing information — making the element unusable for those shoppers. Beyond accessibility, WCAG 2.1 Level AA compliance (Success Criterion 4.1.2) is increasingly required by law in the EU (European Accessibility Act 2025), the US (ADA, Section 508), and other jurisdictions — non-compliance carries real legal risk for online retailers. Automated scanners such as Lighthouse and axe flag this rule and it directly affects your accessibility audit score, which is a growing signal for brand trust and, in some markets, a procurement requirement.

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