Level AWCAG 2.0

3.3.2 Labels or Instructions

Labels or instructions are provided when content requires user input.

Last reviewed: September 9, 2026

Understanding 3.3.2

This criterion ensures that anyone filling out a form, sighted or using assistive technology, understands what information each field expects before submitting it. Without labels or instructions, screen reader users may not know a field's purpose at all, and every user benefits from format hints, such as a required date format, that prevent errors before they happen.

How to Meet It

Provide a visible, programmatically-associated <label> for every input, using label for, aria-label, or aria-labelledby. Include format instructions for fields with specific requirements (date formats, password rules) as visible text near the field, or via aria-describedby; not placeholder text alone, since placeholders disappear once the user types and are not reliably exposed to assistive technology as labels.

Code Examples

INCORRECT

<input type="text" placeholder="Full Name" />
<!-- Placeholder is not a real label; it disappears once the user types and is not consistently exposed as a label to assistive technology -->

CORRECT

<label for="fullname">Full Name</label>
<input type="text" id="fullname" placeholder="e.g. Jane Doe" />

Frequently Asked Questions

Can placeholder text replace a label?

No. A placeholder can supplement a label with an example value, but it cannot replace it: placeholders vanish once the user starts typing and are not a substitute for a programmatically associated label.

Related Success Criteria

3.3.1 Error Identification 3.3.3 Error Suggestion 3.3.4 Error Prevention (Legal, Financial, Data)3.3.5 Help

Quick Facts

Criterion3.3.2
LevelA
IntroducedWCAG 2.0

Automate Compliance

AccessiSight automatically scans and identifies 3.3.2 issues in your codebase.

Try Scanner Free