Alert Dialog

Usage#

import {
  AlertDialog,
  AlertDialogAction,
  AlertDialogCancel,
  AlertDialogContent,
  AlertDialogDescription,
  AlertDialogFooter,
  AlertDialogHeader,
  AlertDialogTitle,
  AlertDialogTrigger,
} from "neelam-ui";
 
<AlertDialog>
  <AlertDialogTrigger>Delete project</AlertDialogTrigger>
  <AlertDialogContent>
    <AlertDialogHeader>
      <AlertDialogTitle>Delete this project?</AlertDialogTitle>
      <AlertDialogDescription>This cannot be undone.</AlertDialogDescription>
    </AlertDialogHeader>
    <AlertDialogFooter>
      <AlertDialogCancel>Cancel</AlertDialogCancel>
      <AlertDialogAction variant="destructive">Delete</AlertDialogAction>
    </AlertDialogFooter>
  </AlertDialogContent>
</AlertDialog>

How it differs from Dialog#

Mechanically it is a Dialog — same native <dialog>, same focus trapping, same top-layer stacking. Three deliberate subtractions make it an alert dialog:

• No outside-click dismissal. Not a prop that defaults to off — simply never available. A stray click silently discarding a destructive confirmation is exactly what this component exists to prevent.
• No Escape. A native <dialog> fires a cancelable cancel event before Escape closes it, so onCancel calls preventDefault() on it. The close is stopped before it starts, rather than closing and reopening.
• No corner close button. Every way out should read as a deliberate choice between the two footer buttons, not a third, easier-to-misclick escape hatch.

AlertDialogTrigger, AlertDialogHeader, AlertDialogTitle, AlertDialogDescription, and AlertDialogFooter are the exact same components as their Dialog counterparts, re-exported under alert-flavoured names. Only AlertDialogContent, AlertDialogAction, and AlertDialogCancel are new.

Action and Cancel#

Both close the dialog. They differ only in default styling, so the pair reads as primary/secondary without either needing an explicit variant:

• AlertDialogAction defaults to variant="default".
• AlertDialogCancel defaults to variant="outline".

Both accept Button's full variant and size set, which is the whole affordance for a destructive confirmation:

<AlertDialogAction variant="destructive">Delete</AlertDialogAction>

Calling preventDefault() in your own onClick stops the dialog closing — the hook for keeping it open while an async delete is in flight.

Keyboard#

Accessibility#

• The panel carries role="alertdialog" rather than the <dialog> element's implicit dialog role, which is what tells assistive tech this one requires an immediate, explicit response.
• AlertDialogTitle supplies the accessible name via aria-labelledby and is required. AlertDialogDescription is wired up with aria-describedby.
• Focus moves into the dialog on open and returns to the trigger on close.
• Background content is made inert by the platform, so it is removed from the accessibility tree rather than merely covered.
• Transitions are dropped under prefers-reduced-motion.

API reference#

AlertDialog#

AlertDialogContent#

AlertDialogAction#

AlertDialogCancel#