Back to Learn
Pulseaccessibility

Elements Use Only Permitted ARIA Attributes

What This Audit Checks

This audit flags elements that use ARIA attributes explicitly prohibited for their role. Unlike merely unsupported attributes, prohibited attributes directly conflict with the element's semantics.

Why It Matters

Prohibited attributes create contradictions in the accessibility tree. For instance, aria-label on a generic <div> with no role adds a name to an element that has no semantic meaning, confusing assistive technologies about the element's purpose.

How to Fix It

  • Remove the prohibited attribute. If the attribute conflicts with the role, it should not be there.
  • Add an appropriate role if the attribute is intentional. Give the element a semantic role that permits the attribute.
  • Use native HTML instead of layering ARIA onto generic elements.
<!-- Bad: aria-label is prohibited on elements with no role -->
<span aria-label="Status indicator">Active</span>

<!-- Good: add a role that supports aria-label -->
<span role="status" aria-label="Status indicator">Active</span>

How Pulse Tracks This

Pulse flags this audit in your Lighthouse accessibility score. When the audit fails, Pulse shows which elements triggered it so you can fix them directly.

Resources