axe-core aria-meter-name error: meter missing accessible name
Fixes: axe-core aria-meter-name error: meter missing accessible name Applies when your scan flags this exact rule. Not for manual-only issues the rule does not report.
axe-core aria-meter-name error: meter missing accessible name - how to fix it
TL;DR
This fixes the flagged violation at its source instead of silencing the rule. A meter element has no accessible name, so its value is announced without context. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.
The error, verbatim
axe-core aria-meter-name error: meter missing accessible nameFix it step by step
Step 1
Associate a label element with the meter, or add aria-label like Disk usage.
Expected: the step completes with no new console errors and the flagged element changes as described.
Step 2
Keep the visible caption next to the meter matching the accessible name.
Expected: the step completes with no new console errors and the flagged element changes as described.
Step 3
Re-run axe to confirm.
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
- Meters are often decorative-adjacent; if it conveys real info, it needs a name.
- 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-meter-name, WCAG 1.1.1).
Variant phrasings
axe aria-meter-name: meter missing accessible name
Same underlying issue and the same fix. Searchers phrase it different ways; the remediation does not change.
Why it happens
A meter element has no accessible name, so its value is announced without context. 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_7hrAHPknvZXwumWIEWKrOg