Skip to main content
All rules

A11Y-012

Invalid ARIA role

MediumDefault severity · Accessibility · Accessibility (WCAG 2.2 AA)

Last reviewed

What it checks

role attribute values against the WAI-ARIA 1.2 role list (including DPUB and graphics roles).

Why it matters

Assistive technology ignores unknown roles, so a custom control is announced as plain text or a generic element.

Recommended fix

Use a valid role (for example role="button") or a native element.

How to verify

Run axe and confirm no aria-roles issues.

Example fix prompt

Generic prompt (your report adds the evidence)
Please fix this production issue in my app.

Issue A11Y-012: Invalid ARIA role
Site: https://your-app.example

First confirm the issue in the code or live config. If it is not present, say so and change nothing.
Task: Fix the role attributes in the evidence: replace each misspelled or invented role with the correct WAI-ARIA role, or use the native HTML element instead.

Constraints: make the smallest change that fixes this, keep the current design and behaviour, never paste secret values into code or chat, and tell me which files you changed.
Done when: Run axe and confirm no aria-roles issues.

References