WCAG 2.1 Help Blog
ARIA: when to use it (and when not to)
ARIA can solve hard problems, but it can also break accessibility if used incorrectly. Start with native HTML.
Rule one: use native elements first
Buttons, links, inputs, and details elements already expose the right semantics. ARIA should enhance, not replace them.
When ARIA is appropriate
Use ARIA for custom widgets or complex interactions that cannot be expressed with native HTML alone.
- Custom tabs, menus, or sliders
- Live regions for dynamic updates
- Labeling or describing elements when no visible label exists
Common mistakes
Overuse leads to confusion for assistive tech users. Avoid redundant roles, conflicting attributes, and hiding focusable elements.