Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when reviewing rendered HTML, interactive components, or design-system patterns related to Provide accessible names for progress bars. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 23% | 0% |
| case-02 | ✗→✓ | ▲ Improved | 25% | 0% |
| case-15 | ✗→✓ | ▲ Improved | 14% | 0% |
| case-19 | ✗→✓ | ▲ Improved | -6% | 0% |
| case-22 | ✗→✓ | ▲ Improved | 32% | 0% |
Without an accessible name, screen reader users will only hear that a progress bar exists but won't know what task or process it represents.
aria-label or aria-labelledby to name progress barsaria-valuenow, aria-valuemin, and aria-valuemax when the value is knownCheck if all progress bar elements (role="progressbar") have an accessible name via aria-label or aria-labelledby.
Add an aria-label or aria-labelledby attribute to the progress bar to describe what it is measuring.
Explain why progress bars need accessible names for screen reader users to understand the context of the loading state.
Review the rendered markup and interactive states that affect Provide accessible names for progress bars. 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-progressbar-name
Other measured skills in the registry, with their headline benchmark lift.