Alert Dialog

A modal confirmation dialog for *destructive or otherwise consequential* actions ("Delete project", "Sign out everywhere"). Distinct from `Dialog`: the underlying Base UI primitive disables outside-click and Escape-only dismissal so the user MUST…

overlayclient320pxuiv1.1.0

Preview

Alert Dialog — live renderprimitives-alertdialog--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/alert-dialog.json
With the @interlace alias
npx shadcn@latest add @interlace/alert-dialog

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.

3 steps, 2 key presses — replayed on every PR by the play function of KeyboardFlow. Axe cannot press a key, so this — not the a11y scan — is what proves the component is operable without a mouse.

  1. 1Enter on the trigger opens the alert dialogEnter
  2. 2It is labelled + described and traps focus
  3. 3Escape cancels — nothing is confirmedEscape

Escape is locked, not merely exercised. This primitive is in KEYBOARD_DRIVEN + MUST_ASSERT_ESCAPE — deleting the dismissal assertion from the story fails overlay-nav-keyboard-lock, so the path above cannot quietly stop being tested.

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

Measured WCAG contrast ratios per token pair and theme
PairinterlacelightinterlacedarkharborlightharbordarkFloor
destructive on backgrounddestructive tint on the page surface8.31:110.43:17.60:110.03:13.0:1SC 1.4.11
muted-foreground on backgroundsecondary copy9.41:111.32:17.82:19.52:14.5:1SC 1.4.3
destructive-foreground on destructivecopy on a destructive face8.31:110.43:18.02:110.03:14.5:1SC 1.4.3
destructive on carddestructive tint inside a card8.31:19.66:18.02:19.09:13.0:1SC 1.4.11
muted-foreground on cardsecondary copy in a card9.41:110.48:18.25:18.64:14.5:1SC 1.4.3
primary on backgroundprimary tint on the page surface8.80:111.79:18.39:110.03:13.0:1SC 1.4.11
primary-foreground on primarycopy on a primary face8.80:111.79:18.86:110.03:14.5:1SC 1.4.3
primary on cardprimary tint inside a card8.80:110.92:18.86:19.10:13.0:1SC 1.4.11
card-foreground on cardcopy in a card19.65:115.71:118.72:114.69:14.5:1SC 1.4.3
foreground on backgroundbody copy19.65:116.97:117.74:116.19: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.

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
'use client'

Hydrates. It brings JavaScript to any route that imports it — put the boundary here, not at the page.

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,code-editor,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 and src/patterns/lint-playground.tsx. This file is outside it — the glob widens in phase 7.2.

History

This component is at v1.1.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.

Import

10 named exports — pull the parts you need.

Public API
import { AlertDialog, AlertDialogBackdrop, AlertDialogClose, AlertDialogCompose, AlertDialogDescription, AlertDialogPopup, AlertDialogPortal, AlertDialogTitle, AlertDialogTrigger, MIN_VIEWPORT } from '@/components/ui/alert-dialog';

Anatomy

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

AlertDialog (Root, controlled or uncontrolled)
    ├─ AlertDialogTrigger (the originating button)
    └─ AlertDialogPortal (escape stacking context)
        ├─ AlertDialogBackdrop (fixed scrim — bg-foreground/60)
        └─ AlertDialogPopup (centered card — data-min-viewport root)
            ├─ AlertDialogTitle ("Delete project?")
            ├─ AlertDialogDescription ("This cannot be undone.")
            └─ AlertDialogClose (Cancel + Confirm slots — consumer-composed)

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.

AlertDialogComposeProps

PropTypeDescription
trigger*React.ReactNode
openboolean
onOpenChange(open: boolean) => void
title*React.ReactNode
descriptionReact.ReactNode
confirmLabelReact.ReactNodeLabel on the confirm button. Defaults to "Confirm".
cancelLabelReact.ReactNodeLabel on the cancel button. Defaults to "Cancel".
onConfirm() => voidConfirm-click handler. The dialog closes after this fires.
confirmTone'primary' | 'destructive'Tone for the confirm button. Use `destructive` for delete / sign-out / reset actions; `primary` (default) for everything else.
classNamestring

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
Owned by @base-ui/react/alert-dialog — focus trapping, dismissal and typeahead come from the headless primitive, not from us.
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 Base UI part props`React.ComponentProps<typeof BaseAlertDialog.*>` on every part
R6data-slot on every named part`data-slot="alert-dialog"` / `"alert-dialog-trigger"` / `…-portal"` / `…-backdrop"` / `…-popup"` / `…-title"` / `…-description"` / `…-close"`
R7className merged + ...rest`cn(BASE, className)` + `{...props}` spread on every part
R8No `isXxx` prefix on booleansAll booleans inherited from Base UI use the no-`is` form
R11Composition over prop-drillingTrigger / Portal / Backdrop / Popup / Title / Description / Close compound parts
R12Reuse — don't wrapNo bespoke Cancel/Confirm buttons — consumers slot their own
R13Build with the ecosystem`@base-ui/react/alert-dialog` owns keyboard / focus / portal / ARIA
R14Controlled + uncontrolledInherited from `BaseAlertDialog.Root` — `open` + `onOpenChange` + `defaultOpen`
R17API parity with shadcnPart names mirror shadcn/ui AlertDialog
R18Tailwind only — no inline styleEvery visual class is Tailwind; zero `style={{}}`
R19Tokens only — no raw hex/rgba`bg-foreground/60`, `bg-card`, `text-card-foreground`, `p-(--spacing-lg)`, `max-w-(--container-prose)`, `text-h4`, `text-body`, `text-muted-foreground`
R20AA contrast`bg-card` + `text-card-foreground` token pair clears AA in light + dark
R23CLS=0Backdrop + popup are `fixed`; never affect document flow
R24Product-neutral vocabularyStructural names only (Title, Description, Close)
R25Client component`'use client'` — Base UI dialog needs hooks + portals
R26A11y from headless primitiveBase UI implements WAI-ARIA `alertdialog`; focus trap inherited

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

Lucide icons
none
NPM dependencies
  • @base-ui/react
Registry dependencies

Source

The full implementation — components/ui/alert-dialog.tsx once installed.

245 lines · TypeScript
'use client';

import * as React from 'react';

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

/**
 * @interlace/ui — AlertDialog
 *
 * A modal confirmation dialog for *destructive or otherwise consequential*
 * actions ("Delete project", "Sign out everywhere"). Distinct from `Dialog`:
 * the underlying Base UI primitive disables outside-click and Escape-only
 * dismissal so the user MUST acknowledge with a deliberate Cancel/Confirm
 * action (WAI-ARIA `alertdialog` pattern). All keyboard / focus / ARIA come
 * from `@base-ui/react/alert-dialog`; this file is a pure styled surface.
 *
 * ## Anatomy

…225 more lines…

Registry JSON

The raw registry record — what the shadcn CLI fetches.