ARIA progressbar nodes must have an accessible name

Rule ID: aria-progressbar-name
Ruleset: axe-core 4.9
User Impact: Serious
Guidelines: WCAG 2.1 (A), WCAG 2.0 (A), WCAG 2.2 (A), EN 301 549
 

Start building more accessible experiences

Axe DevTools Pro helps dev teams find and fix up to 80% of accessibility issues while coding. No experience required. Get started with your free trial today.

Compliance Data & Impact

User Impact

Serious
▼
Minor
Critical

Disabilities Affected

  • Blind
  • Low Vision
  • Mobility

Standard(s)

  • WCAG 2.1 (A)
  • WCAG 2.0 (A)
  • WCAG 2.2 (A)
  • EN 301 549

WCAG Success Criteria [WCAG 2.1 (A)]

  • 1.1.1: MUST: Non-text Content

WCAG Success Criteria [WCAG 2.0 (A)]

  • 1.1.1: MUST: Non-text Content

WCAG Success Criteria [WCAG 2.2 (A)]

  • 1.1.1: MUST: Non-text Content

    How to Fix the Problem

    Correct markup solutions

    The aria-progressbar-name rule has three markup patterns that pass test criteria: 

    <div role="progressbar" id="alb" aria-labelledby="labeldiv"></div>

<div role="progressbar" id="combo" aria-label="Aria Name">Name</div>

<div role="progressbar" id="title" title="Title"></div>

    1. Ensure that each element with role="progressbar" has one of the following characteristics:

      • Non-empty aria-label attribute.
      • aria-labelledby pointing to element with text which is discernible to screen reader users.

    Incorrect markup solutions

    The aria-progressbar-name rule has four markup patterns that fail testing criteria: 

    <div role="progressbar" id="empty"></div>

<div role="progressbar" id="alempty" aria-label=""></div>

<div role="progressbar" id="albmissing" aria-labelledby="nonexistent"></div>

<div role="progressbar" id="albempty" aria-labelledby="emptydiv"></div>
<div id="emptydiv"></div>

    Why it Matters

    Screen reader users are not able to discern the purpose of elements with role="progressbar" that do not have an accessible name.

    Rule Description

    Aria progressbar elements must have discernible text that clearly describes the destination, purpose, function, or action for screen reader users.

    The Algorithm (in simple terms)

    Checks all elements with role="progressbar" to ensure that they have a discernable, accessible name.

    Resources

    Deque University Course Pages (subscription required)

    No related course information available.

    Contribute to axe-core on GitHub

    Refer to the complete list of axe 4.9 rules.

    Was this information helpful?

    You have already given your feedback, thank you..

    Your response was as follows:

    Was this information helpful?
    Date/Time feedback was submitted: