Building Blocks
Menu
SystemFoundationComponentsPatternsThemesIncluded
CatalogsLive catalogsHow catalogs work
GuidesDocs
Component

Tabs

In-page modes

may defer
ContractTabs
Job
In-page modes
Requirement
may defer
States / rules
Selected, overflow
Specified means
Not separately stated in this row.
Hardest context
sm wrap
Example

Settings groups

Counter-example

Tabs as primary nav of 16

Preview

Preview — not a published component API.

Usage

Job: In-page modes.

A consuming product should document the job, its rules, and the hardest context before treating the component as specified.

When not to use

Do not use for unrelated destinations or as a replacement for a stepper in a required sequence.

Variants

The checklist row does not authorize this page to invent a final component API. Where the source rule names a variant, preserve it; otherwise keep the implemented variant set minimal and job-driven.

States & behavior

Selected, overflow

Universal interactive baseline

Default, Hover, Focus, Active/Pressed, and Disabled apply to interactive controls. Error, Loading, Empty, and Success apply where the component takes or reports data.

Accessibility

  • Use native semantics whenever they match the job.
  • Keep keyboard focus visible and distinct from hover.
  • Do not rely on color alone for state.
  • Maintain touch-operable targets and no hover-only actions.
  • For composite/overlay controls, document focus movement, Escape, and return focus as applicable.

Responsive behavior

Allow reflow/scroll only when it preserves labels and current state; do not silently hide tabs without an alternate path.

Theme comparison

The component job and interaction contract stay stable while product expression changes.

Base
Editorial
Native

Tokens

Bind the implementation to semantic roles for surface, text, border, focus, spacing, shape, and motion as needed. Actual token names must come from the implemented Foundation; this demo deliberately does not mint package-level token names.

Code / Storybook

No shared Building Blocks implementation is claimed here.

When this component exists in code, this section should link to its source and Storybook stories for executable states, Controls, viewport, accessibility checks, and interaction tests. The documentation page remains responsible for job, guidance, source contract, product decisions, themes, and Catalog lineage.