All WCAG criteria
WCAG 3.3.2 · UnderstandableLevel A

3.3.2Labels or Instructions

Labels or instructions must be provided when content requires user input.

Common failures

Patterns that fail this criterion.

  • 01Placeholder used as label (disappears on focus, never spoken by some screen readers)
  • 02Form field with no label at all
  • 03Required-field indicator without text equivalent (just a `*`)
How to test

Testing approach: automated.

axe-core checks for `<label for>` linkage or `aria-label`/`aria-labelledby` on form fields.

axe-core rules

labelselect-nameform-field-multiple-labels
How to fix

Remediation steps.

  1. 1

    Use `<label for="id">`

    Native HTML label linkage. Clicking the label focuses the input. Screen readers announce label.

  2. 2

    Required fields

    Add `required` attribute AND a text indicator ("required" or "*" with a footnote explaining `*`).

  3. 3

    Group with fieldset/legend

    For radio/checkbox groups: `<fieldset><legend>What is your preferred contact method?</legend>...`.

Scan for WCAG 3.3.2 on your site

Find every violation in 42 seconds.

AccessProof runs axe-core 4.9.1 against your site and flags every WCAG criterion with the offending element selector. WCAG 3.3.2 is one of 49 criteria we check on every scan.

Start free auditTry free scanner — no signup
Related criteria

Often appears with…

WCAG 1.3.5 · Level AA

Identify Input Purpose

All 50 WCAG 2.1 Level A + AA success criteria explained.

View the full checklist