Dialogs have no accessible name
Automated check aria-dialog-name, run with axe-core
- WCAG
- Best practice: a recommendation, not a WCAG success criterion
- Severity
- Moderate: a degraded experience
- Typical effort
- Quick win, under 1 hour
- Category
- Forms and controls
Who this affects
Screen reader users when something pops up, such as a cookie banner, newsletter prompt or cart drawer.
Why it matters
The dialog is announced only as "dialog", so the user does not know what has appeared or why focus jumped there.
How to fix it
Add aria-labelledby pointing at the dialog heading, or an aria-label, to the element with role="dialog" or role="alertdialog".
Check your own website
The free scan tests 3 pages against WCAG 2.2 A and AA in about 30 seconds. No sign-up.
Related checks: Forms and controls
- Custom buttons, links or menu items have no accessible name
- Custom input widgets have no accessible name
- Custom checkboxes, switches or radio buttons have no accessible name
- Form fields use invalid autocomplete values
- Buttons have no discernible text
- Form field has more than one label
- Form buttons have no accessible name
- Image buttons have no text alternative