WCAG A/AA requirement Priority: Serious
Accessibility attributes have wrong values
Some accessibility attributes in the code have values that are not allowed or point to elements that do not exist.
This text was translated automatically and has not been reviewed by a native speaker yet.
Why it matters to your customers
Screen readers may announce the wrong state, lose a field's description or ignore the attribute. Shoppers then get misleading information about menus, filters or form errors.
Who is affected
- screen reader users
- blind customers
How to fix it
Use only allowed values (for example aria-expanded="true" or "false"). IDs in aria-labelledby, aria-describedby and aria-controls must exist on the page. Check values that scripts set dynamically.
On Shopify
Usually in theme JavaScript or app widgets that set ARIA values. Fix it in the theme's Liquid and JavaScript files; report app issues to the app developer.
On Shoptet (CZ)
Usually in template scripts or add-ons. Report it to Shoptet or a partner.
On PrestaShop
Usually in theme scripts or modules. Fix it in the theme's templates and JavaScript or report it to the module developer.
On WooCommerce
Usually in theme scripts, page builders or plugins. Fix it in child-theme code or report it to the plugin author.
Standards
| Standard | Clause |
|---|---|
| WCAG 2.2 | 4.1.2 (A) Name, Role, Value |
| WCAG 2.1 | 4.1.2 (A) Name, Role, Value |
| WCAG 2.0 | 4.1.2 (A) Name, Role, Value |
| EN 301 549 4.1.1 | 9.4.1.2 |
| EN 301 549 3.2.1 | 9.4.1.2 |
| Section 508 2017 | E205.4 |
| ДСТУ EN 301 549 2022 | 9.4.1.2 |
Automated check: axe-core rule aria-valid-attr-value.
dequeuniversity.com, github.com, www.w3.org
Related checks
-
Videos have no captions
WCAG 1.2.2 A
-
Custom buttons have no name
WCAG 4.1.2 A
-
Some tooltips are empty
WCAG 4.1.2 A
-
Images have no text description
WCAG 1.1.1 A