Newsletter Form

Canonical email-signup pattern: title + (optional) description + email field + consent checkbox + submit. Composition of the auth primitive set (Form / Field / Input / Button + Checkbox + Typography). The block owns *structure*; consumers wire `action` and…

marketingserver320pxuiv1.2.0

Preview

Newsletter Form — live renderblocks-newsletterform--default

Rendered from the story the storybook (a11y) CI gate runs axe against — the preview can't show something that hasn't been verified.

Install

Two equivalent paths — the URL works in any shadcn-CLI setup; the alias works once you've registered @interlace in your components.json.

Via shadcn URL
npx shadcn@latest add https://ds.interlace.tools/r/newsletter-form.json
With the @interlace alias
npx shadcn@latest add @interlace/newsletter-form

Behavior

What this component does — the keyboard path, the measured colour, the text equivalent and the states it can be in. Every figure below is read out of the test or the source that enforces it by scripts/build-behavior-map.mjs, so nothing here can outlive the gate that keeps it true.

Every semantic colour pair this component's own source uses, measured against the shipped hexes in all 4 theme × scheme combinations. The tightest is muted-foreground on background at 7.82:1 (harbor · light), against a floor of 4.5:1.

Measured WCAG contrast ratios per token pair and theme
PairinterlacelightinterlacedarkharborlightharbordarkFloor
muted-foreground on backgroundsecondary copy9.41:111.32:17.82:19.52:14.5:1SC 1.4.3
muted-foreground on cardsecondary copy in a card9.41:110.48:18.25:18.64:14.5:1SC 1.4.3

Text pairs are held to 4.5:1 (WCAG 2.2 SC 1.4.3); borders, rings and chart axes to 3:1 (SC 1.4.11 non-text). Bold is the worst cell in the row — the one a brand fork has to keep an eye on.

A chart's alt text is not a sentence about the chart — the equivalent of the data is the data. This is what a screen reader gets, read out of the source the install writes into your tree.

Label, not a data equivalentShips sr-only copy

Ships sr-only copy for what the visual carries by position, colour or icon alone — a label, not a full data equivalent.

Where it renders, how narrow it survives, and whether its lines are inside the coverage gate — three answers a consumer needs before the paste, not after the bug.

Render boundary
server component

Renders during SSR / RSC with no hydration cost. It can be imported from a server component without pulling the page into the client.

Minimum viewport
MIN_VIEWPORT = 320

Declared, not assumed. Below 320 CSS px the preflight contract draws a dev-mode outline — how to switch it on.

Coverage gate
not in the gate

The 100% gate currently covers src/charts/**/*.{ts,tsx} and src/lib/**/*.{ts,tsx} and src/primitives/{button-variants,data-state-model,meter-scale,skeleton-variants}.ts and src/primitives/{alert,aspect-ratio,avatar,badge,box,breadcrumb,button,callout,card,checkbox,container,data-state,focus-ring,grade-badge,grid,input,label,meter,pagination,published-date,reading-time,section,section-boundary,separator,skip-link,stack,stat-strip,tag,textarea,typography,visually-hidden}.tsx. This file is outside it — the glob widens in phase 7.2.

History

This component is at v1.2.0, first shipped in @interlace/ui 1.0.0. The version is stamped as a banner into the file the install writes, so the copy in your tree says which one you have — compare it with the number above before deciding whether to re-run the install.

@interlace/ui 1.1.01 entry

Import

2 named exports — pull the parts you need.

Public API
import { MIN_VIEWPORT, NewsletterForm } from '@/components/ui/patterns/newsletter-form';

Anatomy

Extracted from the primitive's JSDoc header. The source is the only documentation that can't drift.

NewsletterForm                    (block — data-min-viewport=320)
    ├─ Typography variant=h3        (title)
    ├─ Typography variant=body      (description — optional)
    ├─ Form                         (the <form> element from primitives/form.tsx)
    │   ├─ Field name="email"
    │   │   ├─ FieldLabel
    │   │   └─ FieldControl render={<Input type="email" />}
    │   ├─ <label> Checkbox + consentLabel
    │   ├─ <input type="text" name="website" /> (honeypot — sr-only, aria-hidden)
    │   └─ Button type="submit"
    └─ <slot for footer>

API reference

Parsed from the type declarations in the source — the same file the install writes into your tree, so this table can't drift from the component you get.

NewsletterFormProps

Also accepts every <form> attribute.

PropTypeDescription
titleReact.ReactNodeHeadline above the form. Defaults to "Subscribe to the newsletter".
descriptionReact.ReactNodeOptional supporting copy under the title.
submitLabelReact.ReactNodeLabel on the submit button. Defaults to "Subscribe".
consentLabelReact.ReactNodeConsent text rendered next to the consent checkbox.
footerReact.ReactNodeSlot below the form — typically a privacy-policy link or unsubscribe note.
loadingbooleanWhen true, render a `<Skeleton variant="newsletter-form" />` placeholder (title + input + submit silhouette). Useful when the form's i18n strings stream in from a CMS.

Skeleton

Pass loading and the component renders a shape-matched <Skeleton /> in its own place — same box, so nothing reflows when the data lands. Below is the same story with loading={true}.

Newsletter Form — loading stateblocks-newsletterform--loading
Usage
<MIN_VIEWPORT loading={isPending} />

Accessibility

Every story for this component is rendered headlessly and checked with axe-core (wcag2aa, wcag22aa, best-practice, ACT) on every PR. That gate has no continue-on-error, so what ships has zero known violations.

What follows is what static analysis can see. Axe cannot press a key and never sees an overlay open, so the operable-without-a-mouse claim lives in Behavior instead, where the keyboard path is replayed step by step.

Focus + keyboard behaviour
Native element semantics — no interaction layer to get wrong.
Focus ring (WCAG 2.2 SC 2.4.13)
Not focusable — no focus indicator required.
Reduced motion
No animation to gate.
ARIA in the source
None — semantics come from the element or the Base UI primitive rather than hand-written ARIA.

Examples

3 more states from the same story file.

R-rule compliance

Every primitive in @interlace/ui models to the portable 26-rule floor enforced by the componentApi ESLint preset. The cells below pin exactly where each rule applies in this file.

RuleConceptWhere
R4Extends React.ComponentProps`React.ComponentProps<'form'> & NewsletterFormProps`
R6data-slot on root`data-slot="newsletter-form"`
R7className merged + ...rest`cn(...) + {...props}` on the Form root
R10Composition seam`footer` prop slots consumer-supplied UI
R13Ecosystem firstBuilt on the primitives layer; no bespoke form state
R14Declares min viewport`data-min-viewport={String(MIN_VIEWPORT)}` + exported const
R18Tailwind onlyZero inline style; classes only
R19Tokens onlySpacing/typography from existing primitives
R25Server componentNo hooks → no `'use client'`
R26A11y from primitivesBase UI Field owns label association + aria-describedby

Minimum viewport

This primitive declares MIN_VIEWPORT = 320 CSS px (DESIGN_PRINCIPLES #14). When mounted in a container narrower than this, the preflight contract draws a dev-mode outline so the regression is visible during local development.

Opt-in to the dev-mode warning
<body data-interlace-dev>...</body>

Add the data-interlace-dev attribute to the body in development builds only — preflight then outlines any primitive whose container is below its declared data-min-viewport.

Dependencies

Base UI primitive
Native / no Base UI dependency
Lucide icons
none
NPM dependencies
none

Source

The full implementation — components/ui/patterns/newsletter-form.tsx once installed.

171 lines · TypeScript
import * as React from 'react';

// @interlace/newsletter-form v1.2.0 — Interlace design system.
// Docs, props and live preview: https://ds.interlace.tools/c/newsletter-form
// What changed since: https://ds.interlace.tools/c/newsletter-form#history
// Generated banner — keep it, the upgrade diff reads this version.

/**
 * @interlace/ui — NewsletterForm
 *
 * Canonical email-signup pattern: title + (optional) description + email
 * field + consent checkbox + submit. Composition of the auth primitive set
 * (Form / Field / Input / Button + Checkbox + Typography). The block owns
 * *structure*; consumers wire `action` and pass brand copy via props.
 *
 * Includes a honeypot `<input type="text" name="website">` rendered with
 * `tabIndex={-1}`, `aria-hidden`, and `.sr-only` — invisible + unreachable
 * to humans + assistive tech, but auto-filled by naive form-spam bots. The
 * server handler should reject any submission where `website` is non-empty.
 *

…151 more lines…

Registry JSON

The raw registry record — what the shadcn CLI fetches.