Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-04 | ✗→✓ | ▲ Improved | -31% | 0% |
| case-10 | ✗→✓ | ▲ Improved | -12% | 0% |
| case-21 | ✗→✓ | ▲ Improved | -3% | 0% |
| case-01 | ✓→✓ | ＝ Same ✓ | -12% | 0% |
| case-02 | ✓→✓ | ＝ Same ✓ | 39% | 0% |
When a dialog opens, screen readers should announce its purpose immediately so users know why their focus has shifted and what information is required.
aria-labelledby to point to a title or aria-label for a direct stringVerify that every element with role="dialog" or role="alertdialog" has an accessible name.
Provide an accessible name for the dialog using aria-labelledby (pointing to the header) or aria-label.
Explain why naming dialogs is crucial for orienting screen reader users when modals appear.
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
Other measured skills in the registry, with their headline benchmark lift.