What this criterion requires
Labels or instructions are provided when content requires user input - every field must say what is expected.
Who it helps
Everyone, and especially people with cognitive disabilities and screen reader users.
Example: fails vs passes
<input placeholder="Full name"><label for="name">Full name</label>
<input id="name" autocomplete="name">Placeholders vanish on input and fail contrast. Every field needs a persistent visible label, and formats stated up front.
How to meet and fix it
- Give every input a persistent visible label; state required formats up front ("DD/MM/YYYY")
- Never rely on placeholder text as the only label - it vanishes on input
Common failures auditors find
- Placeholder-only forms
- Required fields not indicated until after submission
Automated scanning catches a share of these instantly - run a free check - and a manual audit covers the judgement calls a tool cannot make.
In PDF documents
PDF form fields need a tooltip (the field description) that carries the visible label text - an unlabeled field announces only "edit text" to a screen reader.
Check any document against this and 80+ more automated checks with the free PDF accessibility checker.
- W3C, Understanding 3.3.2: Labels or Instructions - w3.org/WAI
- W3C, How to Meet 3.3.2 (quick reference) - w3.org/WAI/quickref
Last updated . Reviewed by the EqualWeb accessibility team.
Does your site pass 3.3.2?
Run a free automated check now, or have certified IAAP/CPWA auditors test every criterion and document the result.