ARIA dialog and alertdialog must have an accessible name
Accessibility testing for dev teams - No experience required
Compliance Data & Impact
How to Fix the Problem
Correct markup solutions
The aria-dialog-name rule has three markup patterns that pass
test criteria:
<div role="dialog" id="alb" aria-labelledby="labeldiv"></div>
<div role="alertdialog" id="combo" aria-label="Aria Name">Name</div>
<div role="dialog" id="title" title="Title"></div>
-
Ensure that each element with
role="dialog"orrole="alertdialog"has one of the following characteristics:- Non-empty
aria-labelattribute. -
aria-labelledbypointing to element with text which is discernible to screen reader users.
- Non-empty
Incorrect markup solutions
The aria-dialog-name rule has four markup patterns that fail
testing criteria:
<div role="dialog" id="empty"></div>
<div role="alertdialog" id="alempty" aria-label=""></div>
<div role="dialog" id="albmissing" aria-labelledby="nonexistent"></div>
<div role="dialog" id="albempty" aria-labelledby="emptydiv"></div>
<div id="emptydiv"></div>Why it Matters
Screen reader users are not able to discern the purpose of elements with
role="dialog" or role="alertdialog" that do not have
an accessible name.
Rule Description
Aria dialog elements must have discernible text that clearly describes the destination, purpose, function, or action for screen reader users.
The Algorithm (in simple terms)
Checks all elements with role="dialog" or
role="alertdialog" to ensure that they have a discernable,
accessible name.
Resources
Deque University Course Pages (subscription required)
No related course information available.
Was this information helpful?
Your response was as follows:
Date/Time feedback was submitted: