meter-name-present
Meters have an accessible name
Checks that elements with role="meter" expose a non-empty accessible name.
Applies to. Applies to elements whose role attribute resolves to meter (the first token naming a known role, matched case-insensitively, so role="foo meter" and role="METER" count) that are included in the accessibility tree. An element with the matching implicit role but no role attribute is out of scope. A custom element whose ElementInternals give it the role (this.attachInternals().role), with no role attribute naming another, is in scope too: that is its default role, and no other rule checks it.
Expectation. The element has a non-empty accessible name from aria-label, from an aria-labelledby that resolves to non-empty text, or from title. role="meter" is name-from-author-only, so subtree text is never accepted: text sitting inside a custom meter widget is not reliably exposed as its name.
Examples
<div role="meter" aria-valuenow="80" aria-label="Disk usage"></div>
aria-label names the meter.
<div role="meter" aria-valuenow="80"></div>
No accessible name from any supported mechanism.
How to check
When this rule can’t decide, it reports cantTell and leaves the question to a person. Each question it can ask is listed here under its reason code, with the steps to answer it. A finding carries the same steps as howToCheck, in the scan’s language. See Output schema.
name_internals
- Inspect the meter the report names, a custom element, and note its role.
- Open the Accessibility pane in the browser's developer tools and read the element's accessible name.
- With a screen reader, move to the element and listen to the name announced.
Pass. The accessibility tree shows a name for the meter, set through its internals or otherwise, and the screen reader announces it.
Fail. The meter has no name in the accessibility tree and the screen reader announces only its role, which fails WCAG 1.1.1.