Writing Accessible Directory Labels
Writing Accessible Directory Labels records a distinct W3C-supported accessible-naming task and keeps implementation mechanics outside the writing guidance.
If a directory needs an accessible name, describe the directory’s purpose or contents concisely instead of repeating “directory.”
Key details
Important caveats
Scope Boundary
This page covers optional directory-name wording; it does not require every directory role to have a name.
Further guidance
Content
Use wording that helps distinguish what the directory contains or is for; omit a name when it would add no useful distinction.
Practical Application
If a directory needs an accessible name, label it by the purpose or contents that distinguish it; do not repeat the generic word “directory” unless that wording adds meaning.
Purpose
A concise purpose-oriented name can help users identify the directory when a label adds useful navigation context.
Reader Check
Does the name help users tell this directory from another region, or is it redundant enough that no accessible name is needed?
Worked Example
Example: Use “Department contacts” for a directory of staff contacts rather than “Directory.”
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.