# Aria Dialog Name

> Use when reviewing rendered HTML, interactive components, or design-system patterns related to Ensure dialogs have an accessible name. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

- Skill: `thedaviddias/aria-dialog-name` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add thedaviddias/aria-dialog-name`
- Raw SKILL.md: https://api.skillmd.com/api/skills/thedaviddias/aria-dialog-name/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: thedaviddias (https://skillmd.com/u/thedaviddias)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/thedaviddias/aria-dialog-name

---


# Ensure dialogs have an accessible name

When a dialog opens, screen readers should announce its purpose immediately so users know why their focus has shifted and what information is required.

## Quick Reference

- All dialog and alertdialog elements must have a descriptive label
- Use `aria-labelledby` to point to a title or `aria-label` for a direct string
- Helps users understand the context and purpose of the modal

## Check

Verify that every element with `role="dialog"` or `role="alertdialog"` has an accessible name.

## Fix

Provide an accessible name for the dialog using `aria-labelledby` (pointing to the header) or `aria-label`.

## Explain

Explain why naming dialogs is crucial for orienting screen reader users when modals appear.

## Code Review

Review the rendered markup and interactive states that affect Ensure dialogs have an accessible name. Flag exact elements, roles, labels, focus behavior, or keyboard interactions that violate the rule, and note how to verify the fix with browser accessibility tooling or assistive tech.

---

For full implementation details, code examples, and framework-specific guidance,
see `references/rule.md`.

Rule page: https://frontendchecklist.io/en/rules/accessibility/aria-dialog-name