Writing Accessible List Labels
Writing Accessible List Labels records a distinct W3C-supported accessible-naming task and keeps implementation mechanics outside the writing guidance.
Name a list only when a concise purpose label helps users distinguish it; otherwise let the surrounding heading or context do the work.
Key details
Important caveats
Scope Boundary
This page covers optional list-name wording, not list markup, list-item labels, or a requirement to name every list.
Further guidance
Content
When a label is useful, describe the list’s purpose or contents briefly and avoid adding generic wording that merely says “list.”
Practical Application
Add a list name only when it helps users identify or distinguish the list from other content; use a concise purpose label and avoid adding names that merely repeat an immediately adjacent heading.
Purpose
Selective naming can distinguish important lists without making every list announcement more verbose.
Reader Check
Does naming the list improve navigation or disambiguation enough to justify the extra announcement?
Worked Example
Example: If two independent lists appear without clear headings, labels such as “Required documents” and “Optional documents” can distinguish them; a single list already under the heading “Required documents” may need no extra name.
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.