VOCABULARY / ENTRY

Modal Dialog

modal-dialog

Interaction patternsScope: Componentmodal-dialog · v0.1.0

A dialog layered over the main content that moves the system into a special mode: the main content is disabled and cannot be used until the person explicitly deals with the dialog.

A fictional FIELDNOTES app screen dimmed by a backdrop, with a centered dialog card showing a title, one line of body text, primary and secondary buttons, and a close control.

Recognizing it

Content outside the dialog is obscured and cannot be operated
Focus moves into the dialog on open, and Tab cycles only inside it
A clear way to close, with focus returning to the trigger afterwards

Concept boundary

Not every overlay is modal. Nonmodal dialogs, popovers, and progressive-disclosure expansions let people keep working on the page. The test is whether the rest of the page stays inert until the dialog is dismissed; if the background can still be clicked or focused, do not call it modal.

When to consider it

A critical error must be prevented before an irreversible action
A user-initiated flow cannot continue without one essential piece of information
A complex flow needs to be broken into small steps that must be completed in order

When to be cautious

The content is unrelated to the person's current goal, such as newsletter promotions or nonessential notices
People need to consult information outside the dialog to decide
The task can be completed in place or alongside without interrupting

Tradeoff

Buys concentrated attention and error prevention at the cost of interrupting the current task; interruptions unrelated to the goal read as annoying and erode trust.

Conditional rules · Editorial advice

When The dialog opensMustMove focus into the dialog and keep the Tab cycle inside it; return focus to the triggering element on close.

When People want to abandon the current dialogMustProvide an explicit close or cancel control and support closing with Escape.

When The dialog holds unsubmitted inputRecommendedClicking the backdrop should not silently discard the input; confirm first or close only through buttons.

Related entries

Progressive Disclosure ↗Related, but different · Only expanding secondary content without needing to block the page

Progressive disclosure lets people keep working on the page, while a modal demands handling first; secondary content is not a reason to make it modal.

Inline Edit ↗Conditional alternative · Editing a short field where nearby content is useful context

Editing in place keeps the context visible, whereas a modal covers information people may need to consult.

Confirmshaming ↗Can be misused as · Blocking people from leaving with a shaming decline option

The blocking power of a modal must not be used to pressure people; the decline option must be as clear and neutral as the confirm option.

Sources and what they support

NN/g · Modal & Nonmodal Dialogs: When (& When Not) to Use Them ↗

Modal dialogs sit over the main content and put the system into a special mode that requires interaction first; they suit preventing critical errors and collecting information needed to continue, while modals unrelated to the person's goal are perceived as annoying and diminish trust.

Retrieved: 2026-09-15

WAI-ARIA APG · Dialog (Modal) Pattern ↗

Windows under a modal dialog are inert; focus moves into the dialog on open, Tab cycles inside it, Escape closes it, and focus returns to the invoking element on close; the container uses the dialog role with aria-modal.

Retrieved: 2026-09-15

MDN · <dialog>: The Dialog element ↗

A dialog opened with showModal() makes the rest of the page inert and closes on Esc, whereas a nonmodal dialog opened with show() does not; an explicit close button should be provided.

Retrieved: 2026-09-15

Definitions reference these sources. Digital specimens, selection advice, relationships, and recipes are editorial work and have not been validated through user research.

Type extensions and implementation notes

This entry has no operable specimen yet; the illustration is an editorial sketch, and focus management and keyboard access must be verified when applied to a product.

{
  "states": [
    "closed",
    "open",
    "confirmed",
    "dismissed"
  ],
  "a11y": [
    "The container uses the dialog role, is marked modal, and has an accessible title",
    "Focus enters the dialog on open and returns to the trigger on close",
    "Both Escape and an explicit close control can close it"
  ],
  "motion": "Backdrop and entrance animation can be omitted; show immediately under reduced-motion preference"
}

Open the Agent JSON file for this entryThis file repeats every field of this entry verbatim and adds its sources, archive status, and editorial scope.