When Semantic HTML Doesn't Exist
You'll learn when semantic HTML falls short and ARIA becomes your necessary tool rather than an anti-pattern.
The Gap in Native HTML
You've learned that the First Rule of ARIA is "Don't use ARIA if semantic HTML exists." But what happens when you need to build something that has no native HTML equivalent?
This is the precise moment ARIA becomes essential, not optional.
Recognizing the Gaps
Native HTML gives us <button>, <nav>, <header>, and more—but it doesn't provide:
- Tabs (a tablist with multiple tab panels)
- Accordions (collapsible content sections)
- Tree views (hierarchical, expandable lists)
- Comboboxes (searchable select dropdowns)
- Carousels (image or content rotators)
- Tooltips (hover-triggered contextual information)
- Modal dialogs (though
<dialog>is emerging, it's incomplete)
These complex widgets exist in design systems everywhere, but HTML has no single element for them.
When ARIA Steps In
Think of semantic HTML as a pre-built furniture set: chairs, tables, beds. ARIA is the toolkit for building custom furniture when the store doesn't sell what you need.
When building a custom tab interface, for example, you'll need role="tablist", role="tab", role="tabpanel", aria-selected, and aria-controls because no <tabs> element exists.
The key question: "Does native HTML provide this pattern?" If no, ARIA is required to communicate the pattern's semantics to assistive technologies.
Validation Check
Before reaching for ARIA, always verify HTML can't do it. But once you've confirmed the gap, use ARIA confidently and correctly to bridge it.
Key Takeaway: ARIA becomes essential when building interactive patterns that have no native HTML equivalent—like tabs, accordions, or tree views—making it the proper tool for filling semantic gaps.