3.3.5 Help

Level AAA · added in WCAG 2.0

Context-sensitive help must be available, meaning help about the specific task or field the user is working on. This is a level AAA criterion: most laws and policies require AA, but it is still worth meeting where you can.

Who it helps

People with cognitive, language or learning disabilities may not know what a field asks for or how to complete a task. Help placed right where they need it avoids errors and saves them from searching a separate help section.

How to meet it

Add a short hint next to fields that need explanation, such as where to find an account number, and link it with aria-describedby.
Give examples of the expected format, such as "For example: GB29 NWBK 6016 1331 9268 19".
Link to a help article about the specific field or step, not to your general help home page.
Use an expandable details element for longer help, so it stays close to the field without cluttering the form.
Keep help text visible and readable; do not rely on hover-only tooltips.

Examples

Fails:A technical field with no explanation of what to enter

<label for="iban">IBAN</label>
<input id="iban" type="text">

Fails:A generic help link that does not relate to the field

<label for="iban">IBAN</label>
<input id="iban" type="text">
<a href="/help">Help center</a>

Passes:A hint, an example and expandable help for this field

<label for="iban">IBAN (international bank account number)</label>
<p id="iban-hint">Find it on your bank statement. Example: GB29 NWBK 6016 1331 9268 19</p>
<input id="iban" type="text" aria-describedby="iban-hint">
<details>
  <summary>Where else can I find my IBAN?</summary>
  <p>Most banking apps show it under account details.</p>
</details>

Can a scanner detect this?

axe-core has no rule for this criterion. Whether help is needed and whether it fits the context is a human judgment. A person must review each form and task and decide where users would need help.

No automated rule tests this criterion. Check it by hand.

Common mistakes

Linking every form to the same help home page instead of the relevant topic.
Putting help only in a tooltip that appears on hover.
Writing help in jargon that is as hard to understand as the field itself.

Official W3C explanation of 3.3.5

Check your own page

See which automated WCAG checks your page fails, with the failing elements and how to fix them.

Reviewed November 2, 2026