axe-core aria-command-name error: button command missing name
Fixes: axe-core aria-command-name error: button command missing name Applies when your scan flags this exact rule. Not for manual-only issues the rule does not report.
axe-core aria-command-name error: button command missing name - how to fix it
TL;DR
This fixes the flagged violation at its source instead of silencing the rule. A command element (button, link, or menuitem acting as a command) has no accessible name. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.
The error, verbatim
axe-core aria-command-name error: button command missing nameFix it step by step
Step 1
Give the command an accessible name from its text content, aria-label, or aria-labelledby.
Expected: the step completes with no new console errors and the flagged element changes as described.
Step 2
For icon-only command buttons, aria-label is the standard fix.
Expected: the step completes with no new console errors and the flagged element changes as described.
Step 3
Activate each command with a screen reader running and confirm the announced name makes sense.
Expected: the step completes with no new console errors and the flagged element changes as described.
Step 4
Re-run axe.
Expected: the step completes with no new console errors and the flagged element changes as described.
When to use this skill
- Your scan report lists this exact rule or failure
- You are clearing automated accessibility failures before release or audit
- A CI accessibility gate is red because of this item
When NOT to use this skill
- This is the command-context cousin of button-name; the same naming rules apply.
- The issue only appears in manual screen-reader testing and no automated rule flags it
- You are doing a full manual WCAG audit; this skill covers one automated check
Compatibility
axe-core 4.8+ (rule aria-command-name, WCAG 4.1.2).
Variant phrasings
axe aria-command-name: button command missing name
Same underlying issue and the same fix. Searchers phrase it different ways; the remediation does not change.
Why it happens
A command element (button, link, or menuitem acting as a command) has no accessible name. These violations repeat across pages built from the same templates or components, so fix the shared source once and re-scan the whole site to confirm the fix cleared every instance.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_UYRVinAic1S-49txIsjgxA