Review progress bars to ensure screen reader users can tell which task they represent. Add descriptive accessible names, check progress semantics, and verify value attributes when the current progress is known.
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.
Reviews and adds names to progress bars so screen reader users can understand which task each bar represents. It checks elements with role="progressbar" for aria-label, which supplies an accessible name, or aria-labelledby, which refers to another element as the name. When the progress value is known, it also checks attributes for the current, minimum, and maximum values.
Use it when building loading indicators and wanting their meaning to be conveyed through speech as well as visually. It also helps review shared components or design systems to make progress bar naming and role assignments consistent. The review checks whether indicators that communicate status have been built only from decorative elements instead of elements with progress semantics.
aria-label that clearly identifies the task.”Names should identify the specific task being measured and avoid redundant wording such as “progress.” Set value attributes when the value is known. Verify changes with browser accessibility features or assistive technology.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
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
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.