Writing Extended Accessible Descriptions
Writing Extended Accessible Descriptions records a distinct W3C-supported accessibility writing task while keeping implementation mechanics outside the writing guidance.
Use a structured extended description when the explanation is too detailed or structurally rich to work well as one short description string.
Key details
Important caveats
Scope Boundary
Use a short accessible description for concise supplemental text; reserve extended structured content for cases where detail or structure is materially useful.
Further guidance
Content
For an extended description, organize the content so headings, lists, links, tables, or other meaningful structure remain understandable in their own right.
Practical Application
Use an extended description when important information needs headings, lists, tables, links, or several organized paragraphs; structure it so readers can navigate the detail instead of receiving one flattened block.
Purpose
Structured extended descriptions let users navigate detailed explanatory material instead of receiving one long flattened string.
Reader Check
Does the explanation materially benefit from structure or length beyond a concise accessible description?
Worked Example
A process diagram with six stages can use a short identifying alternative plus an extended description with a heading and numbered stage list, rather than forcing every stage into one long text string.
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.
- WAI-ARIA 1.2 (opens in a new tab)World Wide Web Consortium (W3C) · WAI-ARIA 1.2 support for accessible descriptions and structured extended descriptions including aria-details.