Common ARIA Mistakes to Avoid
You'll learn: How to identify and prevent the most common ARIA errors that actually make your site less accessible to assistive technology users.
The Paradox of ARIA Misuse
ARIA is powerful, but it's easy to misuse. When applied incorrectly, ARIA can override semantic HTML and create a worse experience than having no ARIA at all. Think of ARIA as a medication—it can heal when used properly, but overdosing or mixing the wrong medicines can cause serious harm.
Top Mistakes That Harm Accessibility
Redundant ARIA
Never add ARIA to elements that already have the correct semantics:
<!-- ❌ BAD: Redundant role -->
<button role="button">Click me</button>
<!-- ✅ GOOD: Native element speaks for itself -->
<button>Click me</button>
Native HTML already announces itself correctly. Adding redundant ARIA is like introducing yourself twice—it confuses screen readers.
Role Conflicts
Don't override semantic HTML with conflicting roles:
<!-- ❌ BAD: Turning a link into a button -->
<a href="#" role="button">Submit</a>
<!-- ✅ GOOD: Use the right element -->
<button type="submit">Submit</button>
This creates confusion: keyboard users expect Enter to follow links, but Space to activate buttons. The role doesn't change keyboard behavior.
Improper State Management
Always update ARIA states when the UI changes:
<!-- ❌ BAD: Expanded but still says false -->
<button aria-expanded="false">Menu</button>
<!-- (menu is now open but aria-expanded wasn't updated!) -->
<!-- ✅ GOOD: State reflects reality -->
<button aria-expanded="true">Menu</button>
Lying to assistive technology is worse than saying nothing—it creates false mental models for users.
Key Takeaway: First rule of ARIA: don't use ARIA if semantic HTML already does the job. When you do use ARIA, ensure roles match element purpose and states always reflect current UI reality.