Choosing Visible Text for Accessible Descriptions
Choosing Visible Text for Accessible Descriptions records a distinct W3C-supported accessibility writing task while keeping implementation mechanics outside the writing guidance.
Prefer useful visible help text as the accessible description when the same information benefits both visual and assistive-technology users.
Key details
Important caveats
Scope Boundary
Hidden descriptive text can still be appropriate when visible text would be redundant or impractical; this is a preference, not a universal ban.
Further guidance
Content
When helpful descriptive text can serve everyone, write it visibly and let the accessible description reuse that same useful wording.
Practical Application
When explanatory help benefits everyone, put the useful wording visibly near the control and reuse it as the accessible description instead of maintaining a different hidden explanation.
Purpose
Visible descriptive text supports people who need the information but do not use a screen reader and reduces divergence between visible and announced help.
Reader Check
Would sighted users also benefit from this information, and can one visible description serve both audiences accurately?
Worked Example
Under a password field, show “Use at least 12 characters” visibly and associate that same text as the accessible description rather than hiding an alternate version for screen readers only.
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.