Site and editorial

Site footer

<forma-site-footer>

Closing identity, actions, secondary navigation, and legal note on a surface tone.

Authoring tag
<forma-site-footer>
Behavior owner
Site content
Canonical source
patterns/site-footer.html

Purpose

The site footer closes every page of a marketing site. Inside .forma-site-footer__inner it can hold a main row (identity sentence and an optional action group), a secondary nav of links such as privacy and source, and a legal note line. The footer normally carries data-forma-tone="inverse" (or another tone), which sets its background and all text, link and rule colors. In the shell it is pushed to the bottom of short pages.

Use when

  • Closing every page of a site built on Marketing shell.
  • Placing secondary destinations (privacy, source, release notes) that do not belong in the header.
  • Repeating a contact action for readers who reach the end of the page.

Avoid when

Behavior to know

  • Main row items flex around 18rem and wrap; the action group does not grow.
  • Footer navigation is a wrapping list of underlined links.
  • The note is a wrapping mono line separated by a rule, spreading its parts to both ends when there is room.
  • In print, footer actions are removed and the tone is flattened.

Basic example

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

Canonical

Minimal site footer

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 site footer Raw HTML for HTML · Minimal site footer
<forma-site-footer class="forma-component-tag">
<div class="forma-site">
  <footer class="forma-site-footer" data-forma-tone="inverse">
    <div class="forma-site-footer__inner">
      <div class="forma-site-footer__main">
        <div><p class="forma-eyebrow">Example / Product</p><p>Strategy, architecture, and delivery for consequential systems.</p></div>
        <div class="forma-actions"><a class="forma-button" href="#contact">Schedule a working session</a></div>
      </div>
      <nav class="forma-site-footer__nav" aria-label="Footer"><ul><li><a href="#privacy">Privacy</a></li><li><a href="#source">Source</a></li></ul></nav>
      <p class="forma-site-footer__note"><span>&copy; 2026 Example</span><span>Indianapolis, Indiana</span></p>
    </div>
  </footer>
</div>
</forma-site-footer>

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

Examples

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.

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-labelnav.forma-site-footer__navstring—Names the footer navigation differently from the primary navigation.
CSS hooks (derived from dist/all.css)
HookKindValues or defaultDescription
.forma-site-footerBlock class—Footer root. Takes margin-block-start: auto so it sits at the bottom of the shell on short pages.
.forma-site-footer__innerElement class—Centers content to the maximum layout width with fluid gutters and generous block padding.
.forma-site-footer__mainElement class—Wrapping row for the identity block and optional action group; items flex around 18rem, actions do not grow.
.forma-site-footer__navElement class—Secondary navigation; its ul becomes a wrapping, unstyled row of links with a 24px minimum height.
.forma-site-footer__noteElement class—Legal or location line in the mono label size, separated by a rule; its span parts wrap and spread apart.
[data-forma-tone]Attribute hook—Surface tone of the footer: normally inverse; surface and elevated also work. Sets background and all text, link and rule colors.
Keyboard interaction
KeysResult
Tab / Shift+TabMoves through the footer action and links in source order.
EnterFollows the focused link (native link behavior).

States

Site footer states
StateHow it is expressedPresentation
Inversedata-forma-tone="inverse"Inverse surface; buttons invert their action colors.
Surfacedata-forma-tone="surface"Secondary surface; links use primary text.
Forced colors@media (forced-colors: active)The toned footer gets a CanvasText border so it stays delineated.
Print@media printFooter actions are hidden and the background is removed.

Accessibility

Forma provides

  • Uses contrast-validated tone pairs for text, links and the muted note on every tone.
  • Keeps footer links underlined and at least 24px tall, and keeps the shell's focus ring visible on inverse.
  • Keeps the footer in source order after main at every width.

Your application supplies

  • Use a footer element at the page level so it is exposed as contentinfo.
  • Label the footer navigation distinctly from the primary navigation.
  • Keep footer actions secondary; do not add a second primary action.

Responsive behavior

  • Main row, navigation list and note are wrapping flex rows; no breakpoints.
  • Inner width is capped at --forma-layout-width-max with fluid gutters.
  • Main row items have an 18rem basis and shrink, so they never force overflow.

Motion

  • No animation in the footer itself. A button in the action group interpolates color on hover only, and not under reduced motion.

Usage guidance

Do

  • Repeat identity in one sentence and link legal and source pages.
  • Use the same footer on every page of a site.

Avoid

  • Duplicating the full primary navigation.
  • Putting required information only in the footer.

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.