Writing Context-Sensitive Help Text for Accessibility
Writing Context-Sensitive Help Text for Accessibility records WCAG 2.2 help guidance as a bounded content-writing intent, rather than expanding generic instructions into another duplicate page.
When a form or process needs assistance beyond its labels and instructions, provide help that is relevant to the user’s current task and makes the expected input or action clearer.
Key details
Important caveats
Scope Boundary
Not every control needs extra help; labels or instructions may already provide sufficient information.
Further guidance
Content
Keep help text specific to the current field, step, or task and explain what users need to know to proceed.
Practical Application
Place help where the user needs it and make it answer the immediate task: what to enter, why it is needed, or how to recover when the label alone is insufficient.
Purpose
Context-sensitive help reduces uncertainty when labels or general instructions are not enough.
Reader Check
Does the help resolve a real uncertainty for this field or step, or is it generic advice that adds reading without helping the current task?
Worked Example
Beside a username field, “Use 6–20 letters or numbers; spaces are not allowed” is context-sensitive help. A generic “Need help? Contact support” message does not explain the field requirement.
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.
- Understanding Success Criterion 3.3.5: Help — WCAG 2.2 (opens in a new tab)World Wide Web Consortium (W3C) · W3C WCAG 2.2 Understanding guidance on consistent help and context-sensitive help for forms and processes.