Writing Visible Input-Format Examples
Writing Visible Input-Format Examples records a distinct W3C-supported accessibility writing task while keeping implementation mechanics outside the writing guidance.
When a field expects a specific format, show a visible example such as “MM/YYYY” or “21/07/2013” alongside the instruction or label.
Key details
Important caveats
Scope Boundary
Keep the real field label and any essential requirement visible; an example supports the instruction but does not replace labeling, validation, or error handling.
Further guidance
Content
Show the expected format in visible instructions or the control label, using a concrete example when that makes the required pattern easier to understand.
Practical Application
Put the expected format where users can see it before entering data, preferably in the label or persistent instruction, and use a concrete example when the pattern is not obvious; do not rely on placeholder text as the only instruction.
Purpose
A visible example lets users review the expected pattern before and during input instead of relying on disappearing placeholder text.
Reader Check
Can the user still review the required format after typing begins, and is the example clearly an example rather than a prefilled value?
Worked Example
Label a field “Expiry date (MM/YYYY)” or place that persistent instruction next to it; do not rely solely on a disappearing “08/2030” placeholder.
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.
- Form Instructions — W3C WAI (opens in a new tab)World Wide Web Consortium (W3C) · W3C WAI guidance to provide form instructions including requirements, formats and timing limitations.