Navigation
Subnavigation
Displays a compact horizontal set of related destinations.
Overview
Displays a compact horizontal set of related destinations. Its semantic foundation is Labelled navigation landmark. Source scope: Reference catalog.
This element maps to the existing tabs component contract.
Visual Example
When to Use
Use Subnavigation when its semantic purpose matches the user task. Prefer native platform behavior, concise labels, predictable placement, and content that remains understandable without visual styling.
Do
- Use the canonical element ID and semantic role.
- Keep labels and state programmatically available.
- Test the element with real content and every supported input modality.
Don't
- Do not substitute a visually similar element with different semantics.
- Do not add focusable descendants without a documented keyboard model.
- Do not communicate state through color or motion alone.
Anatomy
Variants
Variants preserve the same semantics and accessible name. Density changes never reduce the minimum interactive target.
States
Focus-visible takes precedence over hover and selected styling. Loading and disabled behavior never silently remove essential information or recovery paths.
Behavior
Tab follows document order; composite navigation uses documented arrow-key behavior only when required. Web targets are at least 44 × 44 CSS pixels and Flutter targets are at least 48 × 48 dp.
Accessibility
Labelled navigation landmark. The element exposes an accessible name, role, state, value, and result where applicable; retains visible 3:1 focus indication; supports 200% text scaling and 320 CSS pixel reflow; and preserves structure in forced-colors and reduced-motion modes.
Tokens
color.* semantic roles→component.tabs.*→.he-tabsSpacing, sizing, typography, border, radius, icon, motion, focus, and color decisions resolve from canonical tokens. Element code does not contain arbitrary visual literals.
Web and Flutter API
Web
<div class="he-tabs">Subnavigation</div>Flutter
HeTabs(
child: const Text('Subnavigation'),
)ds-subnavigation is a registry identifier only; this library does not register an autonomous custom element under that name. Use the mapped component or native semantic composition shown above.
When an element includes an icon, use the exact Tabler name and semantic size from Foundations · Iconography.
Status
implemented. The contract is registered, visually represented, and included in automated documentation and accessibility validation. This status describes contract coverage, not independent production certification.