How to fix aria valid attr value on PrestaShop

Audit every ARIA attribute on your pages and correct any that have invalid or mismatched values so assistive technologies can interpret them correctly.

Steps for PrestaShop

  1. In your PrestaShop back office, go to Design → Theme & Logo → click 'Use this theme' or navigate to your active theme's files via FTP.
  2. In your active child theme folder (themes/<your-theme>/), search all .tpl (Smarty template) files for ARIA attributes using a code editor.
  3. Correct ID-reference mismatches and invalid keyword values directly in the template files.
  4. Clear the theme cache via Design → Theme & Logo → Advanced Settings → Clear cache, then retest with axe DevTools.
Official PrestaShop documentation ↗
<button aria-expanded="false" aria-controls="nav-menu">Menu</button>
<nav id="nav-menu"><!-- links --></nav>

What is aria valid attr value?

ARIA (Accessible Rich Internet Applications) attributes are special HTML attributes — like `aria-label`, `aria-expanded`, `aria-describedby`, and dozens of others — that give screen readers and other assistive technologies extra information about what an element is and how it behaves. Every ARIA attribute has a strict set of allowed values defined by the ARIA specification. For example, `aria-expanded` must be `"true"` or `"false"`, and `aria-describedby` must point to a real element ID that actually exists on the page. An "invalid attribute value" means one of these attributes has been given a value that doesn't match the rules — such as a typo, a number where a true/false is expected, or a reference to an ID that doesn't exist.

When an ARIA attribute carries an invalid value, screen readers either ignore it entirely or misread the element to the user — for example, announcing a navigation menu as always collapsed, or linking a form field to a description that doesn't exist. This directly breaks the experience for blind and low-vision shoppers, which can cost you sales from that audience. More critically, WCAG 4.1.2 (Name, Role, Value) is a Level AA requirement in most jurisdictions — including the EU's EAA (enforceable from June 2025), the US ADA, and the UK's PSBAR — meaning non-compliance creates real legal exposure and risk of accessibility lawsuits. Google also evaluates accessibility signals as part of overall quality, so repeated failures can suppress organic rankings and reduce trust signals.

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

Not sure if your PrestaShop store has this?

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

Scan my site free

Fix aria valid attr value on another platform