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…
Preview
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.
npx shadcn@latest add https://ds.interlace.tools/r/alert-dialog.jsonnpx shadcn@latest add @interlace/alert-dialogBehavior
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.
- 1Enter on the trigger opens the alert dialogEnter
- 2It is labelled + described and traps focus
- 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.
Measured contrast
packages/ui/__tests__/theme-contract-lock.test.ts ↗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.
| Pair | interlacelight | interlacedark | harborlight | harbordark | Floor |
|---|---|---|---|---|---|
| destructive on backgrounddestructive tint on the page surface | 8.31:1 | 10.43:1 | 7.60:1 | 10.03:1 | 3.0:1SC 1.4.11 |
| muted-foreground on backgroundsecondary copy | 9.41:1 | 11.32:1 | 7.82:1 | 9.52:1 | 4.5:1SC 1.4.3 |
| destructive-foreground on destructivecopy on a destructive face | 8.31:1 | 10.43:1 | 8.02:1 | 10.03:1 | 4.5:1SC 1.4.3 |
| destructive on carddestructive tint inside a card | 8.31:1 | 9.66:1 | 8.02:1 | 9.09:1 | 3.0:1SC 1.4.11 |
| muted-foreground on cardsecondary copy in a card | 9.41:1 | 10.48:1 | 8.25:1 | 8.64:1 | 4.5:1SC 1.4.3 |
| primary on backgroundprimary tint on the page surface | 8.80:1 | 11.79:1 | 8.39:1 | 10.03:1 | 3.0:1SC 1.4.11 |
| primary-foreground on primarycopy on a primary face | 8.80:1 | 11.79:1 | 8.86:1 | 10.03:1 | 4.5:1SC 1.4.3 |
| primary on cardprimary tint inside a card | 8.80:1 | 10.92:1 | 8.86:1 | 9.10:1 | 3.0:1SC 1.4.11 |
| card-foreground on cardcopy in a card | 19.65:1 | 15.71:1 | 18.72:1 | 14.69:1 | 4.5:1SC 1.4.3 |
| foreground on backgroundbody copy | 19.65:1 | 16.97:1 | 17.74:1 | 16.19:1 | 4.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.
Runtime contract
packages/ui/vitest.config.ts ↗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 = 320Declared, not assumed. Below 320 CSS px the preflight contract draws a dev-mode outline — how to switch it on.
- Coverage gate
not in the gateThe 100% gate currently covers
src/charts/**/*.{ts,tsx}andsrc/lib/**/*.{ts,tsx}andsrc/primitives/{button-variants,data-state-model,meter-scale,skeleton-variants}.tsandsrc/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}.tsxandsrc/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.
@interlace/ui 1.0.01 entry
- Addedminor
The component floor reaches every tier: form, overlay, navigation and display primitives were modelled to the portable 26-rule floor with skeletons, locked breakpoints, and AA contrast measured per composite rather than eyeballed.
Components- @interlace/input
- @interlace/textarea
- @interlace/select
- @interlace/checkbox
- @interlace/radio-group
- @interlace/switch
- @interlace/slider
- @interlace/number-field
- @interlace/form
- @interlace/label
- @interlace/dialog
- @interlace/sheet
- @interlace/popover
- @interlace/tooltip
- @interlace/hover-card
- @interlace/dropdown-menu
- @interlace/context-menu
- @interlace/tabs
- @interlace/accordion
- @interlace/collapsible
- @interlace/breadcrumb
- @interlace/pagination
- @interlace/toast
- @interlace/card
- @interlace/badge
- @interlace/avatar
- @interlace/alert
- @interlace/separator
- @interlace/progress
- @interlace/skeleton
Import
10 named exports — pull the parts you need.
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
| Prop | Type | Description |
|---|---|---|
| trigger* | React.ReactNode | — |
| open | boolean | — |
| onOpenChange | (open: boolean) => void | — |
| title* | React.ReactNode | — |
| description | React.ReactNode | — |
| confirmLabel | React.ReactNode | Label on the confirm button. Defaults to "Confirm". |
| cancelLabel | React.ReactNode | Label on the cancel button. Defaults to "Cancel". |
| onConfirm | () => void | Confirm-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. |
| className | string | — |
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.
| Rule | Concept | Where |
|---|---|---|
| R4 | Extends Base UI part props | `React.ComponentProps<typeof BaseAlertDialog.*>` on every part |
| R6 | data-slot on every named part | `data-slot="alert-dialog"` / `"alert-dialog-trigger"` / `…-portal"` / `…-backdrop"` / `…-popup"` / `…-title"` / `…-description"` / `…-close"` |
| R7 | className merged + ...rest | `cn(BASE, className)` + `{...props}` spread on every part |
| R8 | No `isXxx` prefix on booleans | All booleans inherited from Base UI use the no-`is` form |
| R11 | Composition over prop-drilling | Trigger / Portal / Backdrop / Popup / Title / Description / Close compound parts |
| R12 | Reuse — don't wrap | No bespoke Cancel/Confirm buttons — consumers slot their own |
| R13 | Build with the ecosystem | `@base-ui/react/alert-dialog` owns keyboard / focus / portal / ARIA |
| R14 | Controlled + uncontrolled | Inherited from `BaseAlertDialog.Root` — `open` + `onOpenChange` + `defaultOpen` |
| R17 | API parity with shadcn | Part names mirror shadcn/ui AlertDialog |
| R18 | Tailwind only — no inline style | Every visual class is Tailwind; zero `style={{}}` |
| R19 | Tokens 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` |
| R20 | AA contrast | `bg-card` + `text-card-foreground` token pair clears AA in light + dark |
| R23 | CLS=0 | Backdrop + popup are `fixed`; never affect document flow |
| R24 | Product-neutral vocabulary | Structural names only (Title, Description, Close) |
| R25 | Client component | `'use client'` — Base UI dialog needs hooks + portals |
| R26 | A11y from headless primitive | Base 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.
<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
- @base-ui/react/alert-dialog
- Lucide icons
- none
- NPM dependencies
@base-ui/react
- Registry dependencies
Source
The full implementation — components/ui/alert-dialog.tsx once installed.
'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.