WCAG A/AA requirement Priority: Serious
Accessibility attributes are misspelt
Some attributes start with "aria-" but are not real ARIA attributes, usually because of a typo.
This text was translated automatically and has not been reviewed by a native speaker yet.
Why it matters to your customers
The attribute is ignored, so a label or state meant for screen reader users never reaches them. For example, a button meant to be named "Close" may have no name at all.
Who is affected
- screen reader users
- blind customers
How to fix it
Check the spelling against the WAI-ARIA list, for example aria-labelledby (not aria-labeledby). Remove made-up aria-* attributes; use data-* for custom data.
On Shopify
Usually a typo in theme code or an app. Search the theme's Liquid and JavaScript files for the attribute and correct it.
On Shoptet (CZ)
Usually in template code or custom code you added. Fix your own code; report template issues to Shoptet or a partner.
On PrestaShop
Usually a typo in theme or module templates. Correct it in the .tpl or JavaScript files.
On WooCommerce
Usually a typo in the theme, a page builder or a plugin. 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.
dequeuniversity.com, github.com, www.w3.org
Related checks
-
Form fields have no label
WCAG 4.1.2 A
-
Some form buttons have no name
WCAG 4.1.2 A
-
A dropdown has no label
WCAG 4.1.2 A
-
Text is hard to read because of low contrast
WCAG 1.4.3 AA