Writing Clear Instructions for Accessibility
Writing Clear Instructions for Accessibility records accessibility-focused writing guidance from the named standards body while keeping implementation and wording advice separate from unrelated general style rules.
Write instructions, guidance, and error messages in clear language, state input requirements explicitly, and tell users what needs to be corrected when an error occurs.
Key details
Important caveats
Scope Boundary
This page covers accessible wording and information requirements rather than application-specific validation code.
Further guidance
Content
Write instructions, guidance, and error messages in clear language, state input requirements explicitly, and tell users what needs to be corrected when an error occurs.
Practical Application
State the action, required input, and format before the user acts; when something is wrong, name the field or value and explain what needs to change.
Purpose
W3C WAI recommends clear, understandable instructions and error messages and explicit input requirements such as required formats.
Reader Check
Would the instruction still make sense to someone who cannot infer the required format or locate the problem from color, position, or context alone?
Worked Example
Use “Enter the date as DD/MM/YYYY. The day must be 01–31” rather than “Enter a valid date” when the format requirement is essential.
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.
- Writing for Web Accessibility — W3C WAI (opens in a new tab)W3C Web Accessibility Initiative · W3C WAI guidance for accessible page titles, headings, meaningful link text, text alternatives, transcripts/captions, clear instructions, and clear concise content.