Writing Accessible Application Descriptions
Writing Accessible Application Descriptions records a distinct W3C-supported interface-writing task while keeping implementation mechanics outside the writing guidance.
Write an application description only when users need extra operating context or instructions beyond the short application name, and keep it focused on that additional information.
Key details
Important caveats
Scope Boundary
This page covers descriptive wording only; deciding whether role=application is appropriate and implementing the relationship are technical design concerns.
Further guidance
Content
Use the description for concise instructions or contextual information needed to operate the application region, not for a second version of its accessible name.
Practical Application
Add an application description only when users need operating context or instructions that the short accessible name cannot carry. Keep the description supplementary and action-focused.
Purpose
A useful application description can provide operating context after the short identifying name without making the name excessively long.
Reader Check
Does the accessible name already identify the application region? If yes, add a description only when extra guidance is necessary to understand or operate it.
Worked Example
Example: Name: “Chart editor.” Description: “Use the toolbar to change chart type, labels, and data range.” The description adds operating context instead of repeating “Chart editor.”
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 — application role (opens in a new tab)World Wide Web Consortium (W3C) · WAI-ARIA 1.2 role specification support for application semantics and author-provided descriptive relationships.
- 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.