Course contentsShow
← Web Development
Lesson 1037 of 2,98218. Accessibility FundamentalsFree lesson

Common ARIA Anti-Patterns to Avoid

Recognize misuses of ARIA that break accessibility, like redundant roles or conflicting semantics.

Common ARIA Anti-Patterns to Avoid

You'll learn to identify frequent ARIA misuses that actually harm accessibility instead of improving it.

The Core Problem

Just because you can add ARIA doesn't mean you should. Misused ARIA creates conflicting signals for assistive technologies, leading to confusing or broken experiences for users with disabilities. Anti-patterns happen when developers add ARIA attributes unnecessarily, incorrectly, or in ways that contradict semantic HTML.

Common Anti-Patterns

Redundant Roles on Semantic HTML Adding role="button" to a <button> is unnecessary and can cause inconsistencies. Native elements already have built-in roles.

Conflicting Semantics Using <button role="link"> sends mixed messages—is it a button or a link? Assistive technologies won't know which behavior to follow.

Adding aria-label to Non-Interactive Elements Placing aria-label="Main content" on a <div> without a landmark role won't help—screen readers often ignore labels on generic containers.

Using aria-hidden on Focusable Elements An element with aria-hidden="true" that can still receive keyboard focus creates invisible focus traps, completely breaking navigation.

Incorrect Live Regions Making everything aria-live="assertive" overwhelms users with constant interruptions. Most dynamic updates should use polite or no announcement at all.

Think of it like this: ARIA is a patch kit, not a replacement toolkit. Using duct tape on an already-working pipe just adds mess. Only use ARIA when semantic HTML can't do the job, and always test that your additions actually improve the experience rather than breaking it.

Key Takeaway: ARIA anti-patterns—like redundant roles, conflicting semantics, and improper attribute usage—actively harm accessibility by confusing assistive technologies; always prefer native HTML and validate that ARIA additions genuinely solve problems.