CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

58

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/aria-meter-name/SKILL.md
SKILL.md
Quality
Evals
Security

Provide accessible names for meter elements

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.

Quick Reference

  • The <meter> element or role="meter" must have an accessible label
  • Use aria-label or aria-labelledby to provide context
  • Helps users understand what measurement is being displayed

Check

Check for <meter> elements or elements with role="meter" that lack an accessible name.

Fix

Add an aria-label or aria-labelledby to the meter element to describe the measurement.

Explain

Explain why measurements need context through accessible names for screen reader users.

Code Review

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/en/rules/accessibility/aria-meter-name

Repository
thedaviddias/Front-End-Checklist
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.