Component

Dense list

Scan

may defer

This page is a reusable-component split from the source checklist row Table or dense list. The source row remains authoritative.

ContractTable or dense list
Job
Scan
Requirement
may defer
States / rules
Specified means
Not separately stated in this row.
Hardest context
Not separately stated in this row.

Preview

Preview — not a published component API.

Northstar Ready
Atlas Draft
Beacon Blocked

Usage

Job: Scan.

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 compress touch targets or essential content only to maximize row count.

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

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

At sm, keep essential labels and actions reachable with touch-sized targets even if density drops.

Theme comparison

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

Base
Northstar Ready
Atlas Draft
Beacon Blocked
Editorial
Northstar Ready
Atlas Draft
Beacon Blocked
Native
Northstar Ready
Atlas Draft
Beacon Blocked

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.