Writing Accessible Progressbar Value Text
Writing Accessible Progressbar Value Text records a distinct W3C-supported interface-content task while keeping implementation mechanics outside the writing guidance.
Use user-friendly progressbar value text only when the numeric progress value by itself is not sufficiently meaningful.
Key details
Important caveats
Scope Boundary
This page covers progressbar value wording; determining whether progress is determinate, setting ranges, and updating ARIA properties remain implementation concerns.
Further guidance
Content
Write progress value text as a human-readable interpretation of the current state when the number or percentage alone would not convey enough meaning.
Practical Application
Provide value text only when the numeric progress value lacks important context; phrase it as a concise interpretation of the same state rather than as a second, unrelated status message.
Purpose
Meaningful value text gives assistive-technology users the context the raw numeric progress value cannot provide by itself.
Reader Check
Does the percentage or numeric position already tell users enough, or do they need context such as items completed or the current phase?
Worked Example
Example: If the numeric value is 60 on a five-file process, value text such as “3 of 5 files uploaded” can add useful context without replacing the underlying numeric progress.
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.
- Communicating Value and Limits for Range Widgets — WAI-ARIA Authoring Practices Guide (opens in a new tab)World Wide Web Consortium (W3C) · W3C APG guidance for user-friendly aria-valuetext across range widgets, including progress bars when a numeric value is not sufficiently meaningful.