# Display

> Display-sized heading for marketing hero copy. Larger than the `Title` scale; used sparingly on landing/about/contact heroes where the type itself is the visual.

- Status: beta
- Group: display
- Page: https://www.digitaltableteur.com/design-system/components/display
- Contract: https://www.digitaltableteur.com/contracts/v1/Display.contract.json

## When to use

Display is the hero-scale text voice; one deliberate step above the Title ladder, for the handful of moments a page leads with type: heroes, campaign taglines, big numbers. The scale is fixed; `as` picks the semantics (`h1` default; use `p`/`span` when the text is decorative rather than the document heading). If you are choosing between sizes, you want Title; Display has exactly one job.

## When not to use

- Do not use `Display` for in-page section headings; that is `Title`.
- Do not stack two `Display` headings in the same viewport; the marketing visual collapses.
- Do not use Display for section headings; that is the Title ladder (levels decoupled from sizes).

## Look-alikes

- Text: Do not stack Display lines to fake a type ladder; hierarchy below the hero belongs to Title and Text.
- Title: Do not use Display for section headings; that is the Title ladder (levels decoupled from sizes).

## Props

| Prop | Type | Default | Description | Required |
| --- | --- | --- | --- | --- |
| `as` | `"div" \| "h1" \| "h2" \| "p" \| "span"` | `h1` | Element to render, defaults to h1. | No |
| `children` | `React.ReactNode` | none | Content to display. | Yes |

## Variants

- Allowed `as` values: `div`, `h1`, `h2`, `p`, `span` (default `h1`).

## Invalid combinations

The contract records no invalid combinations.

## Keyboard

The contract records no keyboard interaction.

## Rules

Every item under When not to use is a MUST NOT. MUST and SHOULD follow RFC 2119.

| Level | Rule | How it is checked |
| --- | --- | --- |
| MUST | ARIA: Renders an h1/h2/h3 by default; semantic heading. Override the level via `as` when nesting inside a section that already owns the page h1. | Not yet verified: no evidence record. WCAG 4.1.2. |
| MUST | Required stories produce no axe violations at the configured severity. | Automated by `npm run test:stories:matrix:ci`. WCAG 2.5.8. |
| MUST | The accessibility tree (role, name, state) matches the committed snapshot for every required story. | Automated by `npm run test:stories:matrix:ci`. WCAG 1.3.1, 4.1.2. |
| MUST | The component remains legible and operable under a real browser forced-colors: active pass. | Automated by `npm run test:stories:hc`. |
| MUST | A human completed an end-to-end accessibility review of this component. | Manual review, last on 2026-05-28. |
| SHOULD | Reserve it for one display moment per page; the hero; a page of Displays has no hero. | Not stated in the contract. |
| SHOULD | Match as to the document outline: h1 in the page hero, p or span for decorative taglines near an existing heading. | Not stated in the contract. |
| SHOULD | Constrain the measure (max-width); display type past ~15 words per line collapses its impact. | Not stated in the contract. |
| SHOULD | Let it wrap naturally; never force line breaks for shape at one viewport. | Not stated in the contract. |
| SHOULD NOT | Do not stack Display lines to fake a type ladder; hierarchy below the hero belongs to Title and Text. | Not stated in the contract. |

## Install and import

- Install: `npm install @digitaltableteur/react` (version 0.9.1, restricted access on npm).
- Import: `import { Display } from "@digitaltableteur/react";`
- Entry point: `@digitaltableteur/react/typography` exports it too.
- Styles: import `@digitaltableteur/react/style.css` once at the app boundary.
- Also available as the custom element `<dt-display>`; see the custom elements manifest.

## Links

- Machine-readable contract (Design System Contract 1.0): https://www.digitaltableteur.com/contracts/v1/Display.contract.json
- Markdown version of this page: https://www.digitaltableteur.com/design-system/components/display.md
- Component index as JSON: https://www.digitaltableteur.com/design-system/components.json
- All components: https://www.digitaltableteur.com/design-system/components
- Source: The implementation lives in a private repository. This page, its Markdown twin and the contract are generated from it at build time and are the public source of truth.