In one paragraph
ARIA meter nodes must have an accessible name means a tested gauge role lacks a meaningful subject for its value. Label the measured quantity and expose an accurate value within a defined range. Descendant percentage text is not automatically the meter's name. Choose meter for a bounded measurement, not as a universal role for loading progress, editable ratings, or decorative bars.
Why it matters
A percentage needs context. Sixty percent could describe storage usage, battery charge, or another bounded measure. A clear name tells the user what the figure means, while value text can communicate units or interpretation that a percentage alone loses.
A meter is not a user-operated slider and is not a task-progress indicator. Choosing the right role matters before filling required attributes. The native meter element may provide a simpler foundation where it fits the content and supported rendering needs.
Naming, required current value, range limits, and readable interpretation are separate concerns. Some roles define implicit bounds, and requirements can vary by specification and host element. Do not claim every numeric attribute is unconditionally required merely because a neighbouring rule checks required properties.
How WebAuditOS evaluates this finding
The supplied aria-meter-name implementation selects applicable explicit role=meter elements and accepts supported ARIA labels or references and a title fallback. It does not take ordinary descendant value text as the name.
Serious impact maps to high severity. The described selector does not cover native meter without an explicit role, nor does the naming result validate all range properties or role choice. A password-strength gauge created after typing may be outside the initial rendered snapshot.
How to fix it
- Identify the measured quantity and confirm it has a meaningful bounded range. For task completion use appropriate progress semantics; for an editable value consider the correct input widget rather than a read-only gauge role.
- Connect a visible label when possible. A static illustrative ARIA gauge is:
<p id="storage-label">Storage used</p>
<div role="meter" aria-labelledby="storage-label" aria-valuemin="0" aria-valuemax="100" aria-valuenow="60" aria-valuetext="60 GB of 100 GB">60 GB of 100 GB</div>Use real data and units. This example deliberately states bounds and value; it is not a claim that every role and native equivalent shares identical defaults or required attributes.
- Consider a native meter with a correctly associated label where its semantics suit the task. Do not add an explicit redundant role solely to make it enter this scanner's custom-role selector.
- Keep the current number within the applicable minimum and maximum and maintain accurate human-readable value text. A label such as Storage used should stay distinct from the number that changes.
- Update visible and programmatic data together. If the account quota changes or a percentage is recalculated, stale ARIA can contradict the dashboard even when its syntax remains valid.
- Avoid unnecessary keyboard focus on a noninteractive gauge. Users should still be able to find its information through normal reading or supported navigation, and any related action needs its own correct control.
- Test multiple gauges, loading and unavailable data, translated units, and dynamic appearance. Do not announce an invented zero when data is unknown merely to satisfy a numeric field.
- Rescan and review required-property, value, naming, and content-equivalence checks together. A named bar can remain misleading if the role or measurement itself is wrong.
What the fix can break
A generic label such as Score may be ambiguous when several gauges appear together. Provide the subject while keeping names concise and avoiding repetition of nearby context that is not needed.
Incorrect value text can override useful numeric interpretation. Ensure its units and meaning match the actual data rather than a prewritten template.
Changing a progressbar to meter to clear a warning is not a semantic repair when the content still represents task completion. Select the role from meaning, not the easiest rule outcome.
Questions
Does 60% inside the bar name it?
Not under the supplied name-from-author rule. Provide the measured subject through a supported name.
Is meter suitable for upload completion?
Use progress semantics for task completion rather than a measurement gauge.
Does a native meter escape all accessibility requirements?
No. It is only outside this explicit-role selector as documented; naming and meaningful information still apply.
Which related checks help?
Review progressbar names, required attributes, and the automation limits guide.
What severity does this get in the report?
High. An axe finding takes its severity from the impact axe reports for the element that failed, and the report maps critical and serious to high, moderate to medium, minor to low. axe declares this rule serious, so a failure arrives as high. The panel above shows a conformance level because for axe rules severity comes from the scan.