ARIA roles tell assistive technologies what an element is and how it should behave.
When a deprecated ARIA role is used, that meaning becomes unreliable over time and inconsistent across platforms.
Deprecated roles may still work in some browser and assistive technology combinations, but they are no longer recommended for authoring and may be removed or changed in future specifications. Using them introduces an avoidable accessibility risk.
WCAG Success Criterion
4.1.2 — Name, Role, Value
User interface components must have a role that can be programmatically determined and communicated to assistive technologies.
WCAG does not explicitly forbid deprecated ARIA roles. However, if a deprecated role is not correctly exposed, conflicts with native semantics, or is no longer mapped consistently, it may result in a failure of this criterion.
What “Deprecated ARIA Role” Means
In WAI-ARIA, roles fall into different categories:
- Current — recommended for use
- Deprecated — discouraged; may be removed in future versions
- Obsolete — removed from the specification and must not be used
A deprecated role:
- Still exists in the specification (for now)
- Is no longer recommended for new content
- May be inconsistently supported across browsers and assistive technologies
- Has a preferred modern alternative
Deprecated does not mean “broken today.” It means unstable and not future-safe.
Why This Matters
Assistive technologies do not read HTML directly. Browsers map HTML and valid ARIA semantics into accessibility APIs (such as UIA, AXAPI, ATK), which screen readers rely on. These mappings are based on current specifications.
When a deprecated role is used:
- The browser may map it inconsistently
- Different assistive technologies may expose it differently
- Future browser updates may drop or alter support
- Users may receive incorrect or incomplete semantic information
Accessibility depends on predictable semantics, not just what works today.
Example of a Deprecated Role
role="directory" ❌
The directory role was historically used to represent a list of references or navigation items. It is deprecated in modern WAI-ARIA.
<ul role="directory">
<li>Item 1</li>
<li>Item 2</li>
</ul>What’s the Problem?
- The role is deprecated in ARIA 1.2
- Browsers may still expose it as a list for backward compatibility
- That behaviour is not guaranteed across platforms or future versions
This makes it an unnecessary risk when better options exist.
Recommended Alternatives
Use native HTML semantics (preferred)
<ul>
<li>Item 1</li>
<li>Item 2</li>
</ul>Native elements already expose correct roles to assistive technologies.
No ARIA is required.
Use a current ARIA role only when necessary
<div role="list">
<div role="listitem">Item 1</div>
<div role="listitem">Item 2</div>
</div>Choose roles based on actual behaviour and interaction, not appearance.
Native HTML vs ARIA
If native HTML provides the correct semantics, do not add ARIA. Using ARIA is optional. Using deprecated ARIA is a liability.
This is why accessibility guidance emphasises:
No ARIA is better than an invalid or outdated ARIA.
Native elements:
- Follow evolving platform standards
- Are consistently mapped to accessibility APIs
- Require no manual maintenance
How This Is Evaluated
Accessibility tools and audits typically check that:
rolevalues are defined in the current WAI-ARIA specification- Deprecated or obsolete roles are not used
- Roles do not conflict with native semantics
Using a deprecated role does not automatically fail WCAG. It becomes a failure when the role is not programmatically exposed, misrepresents semantics, or creates ambiguity for assistive technologies.
Rule of Thumb
If a role is deprecated:
- Do not use it in new content
- Replace it with native HTML or a current ARIA role
- Avoid relying on backward-compatibility behavior
Accessibility should be predictable today and reliable tomorrow.
Wrapping Up
Deprecated ARIA roles are not immediately broken, but they are unstable by design.
Using them:
- Reduces long-term accessibility reliability
- Depends on inconsistent browser and AT behaviour
- Introduces avoidable risk
To build robust, future-proof accessibility:
- Prefer native HTML
- Use only current ARIA roles
- Avoid deprecated and obsolete semantics
If a role is no longer recommended by the specification, it should not be part of modern markup.
