Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →thedaviddias/aria-progressbar-name
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.
Passed 21 of 24 test cases with the skill, and 15 of 24 without it.
and 3 more in the full report
6 fixed15 passed either way3 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 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
In a Vue 3 template, we have `<div class="bar" role="progressbar" :aria-valuenow="current" aria-valuemin="0" aria-valuemax="100"></div>`. How should we add dynamic accessible naming based on a `taskTitle` prop ("Exporting report")?
| Checked | Without skill | With skill |
|---|---|---|
| The output recommends binding :aria-label to the task title prop. | Passed | Passed |
| The output explicitly rejects appending the word progress to taskTitle. | Missed | Passed |
The instructions your model reads when the skill loads.
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/rules/accessibility/aria-progressbar-name
test cases passed, vs 15 / 24 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.