Deprecated ARIA roles must not be used

Rule ID: aria-deprecated-role
Ruleset: axe-core 4.8
User Impact: Minor
Guidelines: WCAG 2.1 (A), WCAG 2.0 (A), ,

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


Disabilities Affected

  • Blind
  • Deafblind
  • Mobility


  • WCAG 2.1 (A)
  • WCAG 2.0 (A)

WCAG Success Criteria [WCAG 2.1 (A)]

  • 4.1.2: MUST: Name, Role, Value

WCAG Success Criteria [WCAG 2.0 (A)]

  • 4.1.2: MUST: Name, Role, Value
  • 4.1.2: MUST: Name, Role, Value
  • Not specified, or not applicable

How to Fix the Problem

Ensure all values assigned to role="" correspond to WAI-ARIA roles that are not deprecated, or abstract. The following list indicates for each deprecated role a potential alternative that is better supported by assistive technologies:

  • directory: Consider using section, list, or tree instead. Which is most appropriate depends on how directory was used.

Why it Matters

Using deprecated WAI-ARIA roles is bad for accessibility. They will not be recognized or correctly processed by screen readers and other assistive technologies. Using these means not everyone will be able to access essential information.

Rule Description

Values assigned to ARIA role values must not be deprecated.

The Algorithm (in simple terms)

Check all elements containing WAI-ARIA role attribute to ensure that the role is not deprecated in the latest version of the WAI-ARIA specification.


Other Resources

You may also want to check out these other resources.

Refer to the complete list of axe 4.8 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: