WCAG A/AA requirement Priority: Critical
Custom buttons have no name
Some elements that act as buttons, links or menu items were custom-built and have no readable name.
This text was translated automatically and has not been reviewed by a native speaker yet.
Why it matters to your customers
Screen reader and voice control users cannot tell what the control does, so they may miss the menu, filter or add-to-cart action.
Who is affected
- blind customers
- screen reader users
- voice control users
How to fix it
Give every element with role="button", "link" or "menuitem" a name: visible text, aria-label or aria-labelledby. Better: use a native <button> or <a href>, which also adds keyboard support.
On Shopify
Usually custom icon controls in the theme or apps. Add names in the theme's Liquid snippets; report app controls to the developer.
On Shoptet (CZ)
Usually template controls or add-ons. Report it to Shoptet or a partner.
On PrestaShop
Usually theme or module controls. Add names in the .tpl templates or overridden module templates.
On WooCommerce
Usually page-builder or plugin controls. Add names in child-theme code or plugin settings, 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-command-name.
dequeuniversity.com, github.com, www.w3.org
Related checks
-
Custom menus or lists are built incorrectly
WCAG 1.3.1 A
-
Text spacing cannot be adjusted
WCAG 1.4.12 AA
-
The site works in only one screen orientation
WCAG 1.3.4 AA
-
Large tables have cells without headers
WCAG 1.3.1 A