How to fix aria command name on WooCommerce

Steps for WooCommerce

1. In WordPress admin, go to Appearance → Theme File Editor (or use a child theme and edit files via FTP/SFTP).
2. Identify the template file rendering the flagged element: common files are `header.php`, `functions.php` partial includes, or block template HTML files in block-based themes.
3. Find the `<button>`, `<a>`, or ARIA-role element without text.
4. Add `aria-label="Descriptive action name"` to the tag, OR wrap the inner text/icon in `<span class="screen-reader-text">Label text</span>` — WooCommerce and most WP themes already include a `.screen-reader-text` CSS class that hides text visually but keeps it accessible.
5. Alternatively, install the 'WP Accessibility' plugin (by Joe Dolson) which automatically adds accessible labels to common WooCommerce controls like cart and search buttons.
6. Save, clear any caching plugins, and re-run axe to verify.

What is aria command name?

The `aria-command-name` rule flags interactive elements — specifically buttons (`role="button"`), links (`role="link"`), and menuitems (`role="menuitem"`) — that have no accessible name. An "accessible name" is the text a screen reader reads aloud when a user lands on that element. It can come from visible text inside the element, an `aria-label` attribute, an `aria-labelledby` attribute pointing to another element's text, or (for images used as buttons) a meaningful `alt` attribute. When none of those exist, the screen reader either reads nothing at all or reads something meaningless like the raw URL or a string of punctuation, leaving visually impaired shoppers completely in the dark about what the control does.

WCAG 2.1 Success Criterion 4.1.2 (Name, Role, Value) is a Level AA requirement, meaning it is referenced in most accessibility laws worldwide — including the ADA (US), EN 301 549 (EU), AODA (Canada), and EAA (UK/Europe). Failing it exposes your store to legal complaints and demand letters that are increasingly common against ecommerce sites. Beyond legal risk, blind and low-vision shoppers using screen readers simply cannot use controls without accessible names — they cannot add items to a cart, navigate menus, or complete a purchase — directly costing you revenue and customers. Additionally, Google uses accessibility signals as one of many quality indicators, so a more accessible site can support better crawlability and user experience scores.

See the complete Aria command name guide for every platform and the full background.