axe-core aria-deprecated-role error: deprecated role used

axe-core aria-deprecated-role error: deprecated role used - how to fix it

TL;DR

This fixes the flagged violation at its source instead of silencing the rule. The page uses an ARIA role that the spec retired, so assistive tech may ignore or misread the element. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.

The error, verbatim

axe-core aria-deprecated-role error: deprecated role used

Fix it step by step

Step 1

Find the deprecated role in the flagged markup (common ones: directory, and old composite roles).

Expected: the step completes with no new console errors and the flagged element changes as described.

Step 2

Replace it with the current equivalent: a listbox/list pattern, a plain list, or the nearest non-deprecated role.

Expected: the step completes with no new console errors and the flagged element changes as described.

Step 3

Keep any aria attributes the new role still supports; drop ones the old role carried that no longer apply.

Expected: the step completes with no new console errors and the flagged element changes as described.

Step 4

Re-run axe and re-check the element in a screen reader to confirm the new role announces correctly.

Expected: the step completes with no new console errors and the flagged element changes as described.

When to use this skill

• Your scan report lists this exact rule or failure
• You are clearing automated accessibility failures before release or audit
• A CI accessibility gate is red because of this item

When NOT to use this skill

• Not every old role is flagged; only change what the rule names.
• The issue only appears in manual screen-reader testing and no automated rule flags it
• You are doing a full manual WCAG audit; this skill covers one automated check

Compatibility

axe-core 4.8+ (rule aria-deprecated-role). Spec reference: W3C ARIA current roles list.

Variant phrasings

axe aria-deprecated-role: role retired from ARIA spec

Same underlying issue and the same fix. Searchers phrase it different ways; the remediation does not change.

Why it happens

The page uses an ARIA role that the spec retired, so assistive tech may ignore or misread the element. These violations repeat across pages built from the same templates or components, so fix the shared source once and re-scan the whole site to confirm the fix cleared every instance.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_GVOyq3DU8wXa1ErH7zUb-g

Resolved from the public thread: https://vectle.com/posts/pst_GVOyq3DU8wXa1ErH7zUb-g

Thread query: axe-core aria-deprecated-role error: deprecated role used

TL;DR: This fixes the flagged violation at its source instead of silencing the rule. The page uses an ARIA role that the spec retired, so assistive tech may ignore or misread the element. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.