WCAG 3.3.5 — Help

What this requires

Context-sensitive help is available. Specifically, for items requiring user input, descriptive labels (covered by 3.3.2) plus additional explanation as needed: instructions, examples, format hints, or detailed help that explains what to do and why.

How AI coding tools fail this

When asked to "build the form", AI tools generate field labels and nothing else. Format expectations ("date as MM/DD/YYYY"), reasons ("we use your phone number for two-factor authentication"), and worked examples are missing. The user has to guess.

The second pattern: help only on hover. The icon is there; the help appears only to users who can hover and who notice the tiny button.

The third: help that lives behind a "?" link to a separate FAQ page. Context is broken; the user has to navigate away, find the answer, and return.

Passing examples

Inline help that explains format and purpose:

<label htmlFor="phone">
  Phone
  <span className="block text-sm text-muted-foreground">
    Used only for two-factor authentication. Format: country code +
    number, e.g. +1 555 123 4567.
  </span>
</label>
<input
  id="phone"
  type="tel"
  aria-describedby="phone-help"
/>
<p id="phone-help" className="sr-only">
  Used only for two-factor authentication. Format: country code +
  number, for example plus one five five five one two three four
  five six seven.
</p>

A help popover discoverable by click for longer explanations:

<label htmlFor="tax-id">
  Tax ID
  <Popover>
    <Popover.Trigger asChild>
      <button
        type="button"
        aria-label="What is a tax ID?"
        className="ml-1 text-link"
      >
        ?
      </button>
    </Popover.Trigger>
    <Popover.Content>
      Your tax ID is the number your government issues to identify
      you for tax purposes. In the US this is your SSN or EIN; in
      the UK it's your UTR.
    </Popover.Content>
  </Popover>
</label>
<input id="tax-id" />

Edge cases

AAA target. AA covers labels and instructions (3.3.2); AAA pushes for context-sensitive help.
Format hints belong adjacent to the field, not in a separate legend.
Worked examples are powerful and underused.
Help link to a FAQ doesn't satisfy AAA on its own; the help must be reachable in context.
Plain language in help text matters at least as much as in body copy.

How Jeikin handles this

This is a manual review item. The dashboard records each input field and asks the reviewer to confirm whether help is provided in context. The scanner can flag fields with no aria-describedby and no helper text as leading indicators.

References

W3C — Understanding 3.3.5 Help (opens in new tab)