Dialog has no accessible name (role=dialog/alertdialog)

What it means

A dialog is an interactive overlay (modal, popup, or panel) that lacks an accessible name. The name can come from an explicit aria-label or aria-labelledby attribute, or from visible text content inside the dialog. Without it, screen readers announce the dialog as an unnamed region and crawlers can't identify its purpose.

Why it matters

An unnamed dialog breaks the DOM tree that Googlebot and screen readers both consume. This can cause the dialog's content to be treated as boilerplate or duplicate rather than main content, reducing its indexing weight. For AI retrieval, unnamed dialogs are harder to extract and cite because the system can't determine what the overlay is actually about.

How to fix it

1. Add an aria-label attribute with a descriptive name: <div role="dialog" aria-label="Newsletter signup">...
2. Or use aria-labelledby pointing to the heading that names the dialog: <div role="dialog" aria-labelledby="dialog-title">
3. Ensure the dialog has visible text (not just an icon) so the accessible name is also visible to users.
4. Verify the dialog is focusable and keyboard-operable (tab to enter, Escape to dismiss).

When it's not a problem

If the dialog is purely decorative (e.g., a loading spinner or a full-screen background overlay with no interactive content), you can use aria-hidden="true" or role="presentation" and the warning becomes a false alarm. Also fine when the dialog is triggered by a button and the button itself carries the accessible name via aria-label or visible text.

How common is it?

1 audited site in our corpus currently show this issue. The breakdowns below show which platforms, gatekeepers, verticals and countries are most exposed.