Goal
Ensure users know what information is required and how to provide it.
Success Criterion · WCAG 3.3.2
Labels or Instructions
Labels or instructions are provided when content requires user input.
Level AWCAG 2.0Understandable3.3 · Input Assistance
Copy button ready
What to do
Provide clear labels and instructions for form controls, including required fields and formats.
Why it matters
Without instructions, users may not know what data is expected, leading to errors and abandonment.
Success criterion
What WCAG 3.3.2 requires
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
Labels or instructions are provided when content requires user input.
Intent
Why WCAG created this requirement
- Labels provide the purpose of inputs; instructions provide requirements and constraints.
- Placeholder text is not a substitute for labels.
- Clear instructions reduce errors and improve completion rates.
Benefits
Who gains when you pass
- Screen reader users can understand what each input is for.
- Users with cognitive disabilities benefit from explicit guidance.
- All users reduce mistakes when formats and requirements are clear.
Why it matters
User impact when this criterion fails
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Users may provide wrong formats (date/phone) without guidance.
Users may not realize fields are required until submission fails.
Overview
All user input must have labels and/or instructions that help users understand what to do. This includes required indicators, constraints (password rules), and format hints (date format).
- Use `<label>` with `for/id` (or nesting) for all inputs.
- Provide format hints in helper text and associate via `aria-describedby`.
- Mark required fields with text (e.g., “(required)”) and programmatic indication (`required`, `aria-required`).
Reference: All summaries and highlights originate from Understanding WCAG 3.3.2 and the W3C quick reference.
Fast facts
- Conformance level
- Level A
- WCAG version introduced
- WCAG 2.0
- Principle
- Understandable
- Guideline
- 3.3 · Input Assistance
Examples
Make success tangible for teams
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Date field
Pass
Label “Date of birth” with helper “Format: YYYY-MM-DD” linked via `aria-describedby`.
Fail
No label and only placeholder “YYYY-MM-DD”.
Required indicator
Pass
Label includes “(required)” and input uses `required` attribute.
Fail
Required fields are only highlighted in red.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Document form patterns for labels, helper text, and required indicators.
- Create a consistent set of format hints for common fields.
Official resources
Deep dives and supporting material
Keep these links handy when writing acceptance criteria or responding to audits.
Implementation checklist
Capture progress and blockers
- Ensure every input has a visible label or accessible name.
- Provide instructions for required fields and formatting constraints.
- Associate helper text with inputs (`aria-describedby`).
- Avoid placeholder-only labels; keep labels visible.
Testing ideas
Prove conformance with evidence
- Tab through all fields and verify labels are present and announced.
- Verify required fields are indicated before submission.
- Check format instructions are readable and programmatically associated.
Related success criteria
More from Input Assistance (3.3)
WCAG 3.3.1Error IdentificationLevel AWCAG 3.3.3Error SuggestionLevel AAWCAG 3.3.4Error Prevention (Legal, Financial, Data)Level AAWCAG 3.3.5HelpLevel AAAWCAG 3.3.6Error Prevention (All)Level AAAWCAG 3.3.7Redundant EntryLevel AWCAG 3.3.8Accessible Authentication (Minimum)Level AAWCAG 3.3.9Accessible Authentication (Enhanced)Level AAA