Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →thedaviddias/aria-meter-name
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Provide accessible names for meter elements. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
Passed 23 of 23 test cases with the skill, and 21 of 23 without it.
2 fixed21 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
An audit of a server health dashboard reveals three `<meter>` elements: memory usage, CPU load, and disk space. Currently, all three are coded simply as `<meter value="...">`. What specific defect should be recorded for each element and what is the remediation plan?
| Checked | Without skill | With skill |
|---|---|---|
| The audit report flags all three meter elements for missing accessible names. | Passed | Passed |
| The remediation plan specifies adding distinct aria-label attributes to each meter element. | Missed | Passed |
The instructions your model reads when the skill loads.
A meter represents a scalar measurement; without a label, a user might hear a value (e.g., '50%') but have no idea if it refers to battery life, storage space, or a password strength.
<meter> element or role="meter" must have an accessible labelaria-label or aria-labelledby to provide contextCheck for <meter> elements or elements with role="meter" that lack an accessible name.
Add an aria-label or aria-labelledby to the meter element to describe the measurement.
Explain why measurements need context through accessible names for screen reader users.
Review the rendered markup and interactive states that affect Provide accessible names for meter elements. Flag exact elements, roles, labels, focus behavior, or keyboard interactions that violate the rule, and note how to verify the fix with browser accessibility tooling or assistive tech.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/accessibility/aria-meter-name
test cases passed, vs 21 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.