Layout primitives

Landmark region

<forma-landmark-region>

Creates a labeled semantic region for orientation and task ownership.

Authoring tag
<forma-landmark-region>
Behavior owner
Native HTML
Canonical source
patterns/landmark-region.html

Purpose

A landmark region is a named band of orientation content (where am I, what can I reach, what state is the system in) that stays at the top of its scroll container while the user works below it. Its semantics come entirely from native elements: an aside, nav, section or header with an accessible name becomes a landmark screen-reader users can jump to. Forma lays the band out as a wrapping row with its items spread across the width, gives it an opaque background, and makes it sticky on screens wider than 48rem. The application supplies the content and keeps any status text current.

Use when

  • A workspace needs a persistent, named band with local navigation and a short system status.
  • Users should be able to jump to the orientation region with landmark navigation.
  • The band should stay visible while a long task region scrolls, on screens with room for it.

Avoid when

Behavior to know

  • Sticky at the block start with z-index 1 above 48rem; static at 48rem and below so it never eats small-screen height.
  • Opaque surface background, so content scrolling underneath does not show through.
  • Items and nested nav links wrap, so long labels never force horizontal scrolling.

Basic example

The smallest correct markup: the canonical pattern from patterns/landmark-region.html inside its public tag. Copy this first, then adapt labels, names and state.

Canonical

Minimal landmark region

Rendered from the canonical pattern file.

Static specimen. Its links point to placeholder destinations that do not exist on this site. Its controls are shown for their markup and appearance and cannot be operated here.

HTML · Minimal landmark region Raw HTML for HTML · Minimal landmark region
<forma-landmark-region class="forma-component-tag">
<aside class="forma-landmark-region" aria-label="Workspace context">
  <nav aria-label="Primary"><a href="#overview" aria-current="page">Overview</a><a href="#activity">Activity</a></nav>
  <p class="forma-landmark-region__status" role="status">System ready</p>
</aside>
</forma-landmark-region>

Click or tap the code once to select all of it, then copy.

Examples

Scenario

Project context band

A named section with the project name, local navigation and a live status message. The section is a region landmark because it has an accessible name; the nav is a second, separately named landmark.

Static specimen. Its links point to placeholder destinations that do not exist on this site. Its controls are shown for their markup and appearance and cannot be operated here.

Payments API

All checks passing

HTML · Project context band Raw HTML for HTML · Project context band
<forma-landmark-region class="forma-component-tag">
  <section class="forma-landmark-region" aria-labelledby="landmark-region-project-context-title">
    <h2 id="landmark-region-project-context-title">Payments API</h2>
    <nav aria-label="Project sections">
      <a href="#landmark-region-project-context-title" aria-current="page">Overview</a>
      <a href="#deployments">Deployments</a>
      <a href="#settings">Settings</a>
    </nav>
    <p role="status">All checks passing</p>
  </section>
</forma-landmark-region>

Click or tap the code once to select all of it, then copy.

Scenario

Review status aside

A complementary landmark summarising a document review: who owns it, the due date and a status message. It uses --forma-landmark-space for a tighter band in a dense workspace.

HTML · Review status aside Raw HTML for HTML · Review status aside
<forma-landmark-region class="forma-component-tag">
  <aside class="forma-landmark-region" style="--forma-landmark-space: 0.5rem" aria-label="Review status">
    <p>Owner: Legal operations</p>
    <p>Due <time datetime="2026-10-03">3 Oct 2026</time></p>
    <p role="status"><span class="forma-status-lozenge" data-state="attention">2 comments unresolved</span></p>
  </aside>
</forma-landmark-region>

Click or tap the code once to select all of it, then copy.

Mobile

Each mobile example renders in its own document inside a real narrow viewport, so Forma's media and container queries run exactly as they would on a phone. Choose a width to compare.

Mobile example

Mobile wrapped band

The project band at phone width. It stops being sticky, and the heading, navigation links and status wrap onto separate lines.

Static specimen. Its links point to placeholder destinations that do not exist on this site. Its controls are shown for their markup and appearance and cannot be operated here.

Viewport width

Frames narrower than the selected width show the component at the width available.

What changes at narrow widths

  • At 48rem and below the region becomes position: static, so it scrolls away instead of permanently covering part of a short screen.
  • Items wrap; the space-between distribution puts wrapped items at the start of each new line.
  • Navigation links wrap with the same gap, keeping each link a separate target.
  • In landscape on a tablet wider than 48rem the band becomes sticky again.
HTML · Mobile wrapped band Raw HTML for HTML · Mobile wrapped band
<forma-landmark-region class="forma-component-tag">
  <section class="forma-landmark-region" aria-labelledby="landmark-region-mobile-wrapped-band-title">
    <h2 id="landmark-region-mobile-wrapped-band-title">Payments API</h2>
    <nav aria-label="Project sections on mobile">
      <a href="#landmark-region-mobile-wrapped-band-title" aria-current="page">Overview</a>
      <a href="#deployments-mobile">Deployments</a>
      <a href="#incidents-mobile">Incidents</a>
      <a href="#settings-mobile">Settings</a>
    </nav>
    <p role="status">Deploy in progress</p>
  </section>
</forma-landmark-region>

Click or tap the code once to select all of it, then copy.

Baseline

Mobile · 320px

The canonical pattern in a true 320px viewport, the minimum width every Forma component must support without page-level horizontal scrolling.

Static specimen. Its links point to placeholder destinations that do not exist on this site. Its controls are shown for their markup and appearance and cannot be operated here.

Viewport width

Frames narrower than the selected width show the component at the width available.

API and configuration

Forma components have no JavaScript API. Their public contract is the markup: native elements and attributes you write, and the CSS hooks below. The CSS hook table is generated from the built stylesheet, so it always matches the shipped implementation.

Native and ARIA attributes
AttributeOnValuesDefaultDescription
aria-labelaside / nav / sectionstring—Accessible name. A section only becomes a region landmark when it is named; name every nav when there is more than one.
aria-labelledbysectionid of the band heading—Names the region from its visible heading.
aria-currentnav linkpage—Marks the current location in the band's navigation.
rolestatus elementstatus—Makes status text a polite live region, so application updates are announced without moving focus.
style.forma-landmark-region--forma-landmark-space: <length>—Per-instance spacing override.
CSS hooks (derived from dist/all.css)
HookKindValues or defaultDescription
.forma-landmark-regionBlock class—Sticky (above 48rem), wrapping flex band with space-between distribution, block padding and an opaque surface background. Nested nav elements become wrapping rows.
--forma-landmark-spaceCustom property—Gap between items, gap between nav links, and block padding. Default --forma-primitive-spacing-3 (0.75rem).
Keyboard interaction
KeysResult
Tab / Shift+TabMoves through links and controls in the band in source order.
Screen-reader landmark navigationNamed aside, nav and section elements appear in the landmark list; this is native browser and assistive technology behavior.

Form behavior

Not a form control.

States

Landmark region states
StateHow it is expressedPresentation
Stickyviewport above 48remStays at the top of the nearest scroll container while content scrolls beneath.
Staticviewport at or below 48remScrolls with the page.
Current locationaria-current="page" on a linkNative state the application sets for the active section.

Accessibility

Forma provides

  • Keeps landmark semantics on native elements; the class adds layout only.
  • Opaque background prevents scrolled content from reducing text contrast behind the band.
  • Drops stickiness on small screens so the band cannot obscure focused content (WCAG 2.4.11).

Your application supplies

  • Give the region and each nav inside it a unique accessible name.
  • Keep status text short and update it in place; role="status" announces changes politely.
  • Provide scroll padding for anchors so targets are not hidden under the sticky band on wide screens.
  • Avoid more than one sticky band per scroll container.

Responsive behavior

  • Viewport breakpoint at 48rem switches between sticky and static.
  • Items wrap with flex-wrap, so the band grows taller rather than wider on narrow screens.
  • Stickiness is relative to the nearest scrolling ancestor; inside a scrollable pane it sticks to that pane.

Motion

  • No animation: the band sticks and unsticks through native sticky positioning without transitions.

Usage guidance

Do

  • Limit the band to orientation: name, local navigation and short status.
  • Use the same band position across pages of a workspace.

Avoid

  • Putting long forms or primary actions in a sticky band.
  • Relying on the forma-landmark-region__status class from the canonical pattern for styling; it has no CSS. Use role="status" for semantics.

Verification specimens

Generated fault-injection specimens expose content, spacing, color-cue, and reduced-effective-contrast risks. They screen presentation robustness as engineering screens without claiming human-subject validation.