Writing Accessible Descriptions That Add Information
Writing Accessible Descriptions That Add Information records a distinct W3C-supported accessibility writing task while keeping implementation mechanics outside the writing guidance.
Use an accessible description to add useful information beyond the accessible name, such as context, instructions, or constraints.
Key details
Important caveats
Scope Boundary
Do not turn the description into a second label or a dump of unrelated detail; use it only when additional information is genuinely useful.
Further guidance
Content
Write description text that contributes useful instructions, constraints, context, or other information that the accessible name alone does not provide.
Practical Application
Use an accessible description only to add useful context, instructions, constraints, or other information beyond the accessible name.
Purpose
Supplemental descriptions help users understand information that would otherwise be missing when they encounter the named object.
Reader Check
If the description were removed, would useful information be lost? If it only repeats the name, omit or rewrite it.
Worked Example
Example: Name a field “Password” and use a separate description such as “At least 12 characters,” rather than repeating “Password field.”
Sources and evidence
Sources are shown with the role they play in this guide. Historical or style-sensitive claims are kept within the evidence boundary described above.
- Providing Accessible Names and Descriptions — W3C WAI ARIA APG (opens in a new tab)W3C Web Accessibility Initiative · W3C WAI-ARIA Authoring Practices guidance for descriptive accessible names, visible labels, and button/control naming.