What WCAG 3.3.2 Requires
Every form field that requires specific input needs a label or instructions describing what is expected, such as a required date format or password rules.
New to this criterion? Read our plain-English guide, WCAG 3.3.2 Labels or Instructions Explained in Plain English, with examples and code.
Can AccessBell Test This Automatically?
Yes. AccessBell's scanner runs axe-core, which includes 1 rule that catch code-level failures of this criterion:
form-field-multiple-labels— Ensure form field does not have multiple label elements (details (opens in a new tab))
This criterion is included in: WCAG 2.2 AA Checker, WCAG 2.1 AA Checker, ADA Compliance Checker, Section 508 Checker, EN 301 549 Checker.
How to Test It by Hand
Check that every form field has a visible label, and that any specific input requirements (format, length) are stated before the field is submitted.
Common Failures
- A password field lists its complexity rules only after a failed submission, not up front.
- A date field gives no example of the expected format.
Related Criteria in Input Assistance
WCAG 3.3.2 Questions
What does WCAG 3.3.2 require?
Every form field that requires specific input needs a label or instructions describing what is expected, such as a required date format or password rules.
Can AccessBell test WCAG 3.3.2 automatically?
Yes. AccessBell runs 1 automated rule that can catch failures of this criterion, including in our WCAG 2.2 AA Checker, WCAG 2.1 AA Checker, ADA Compliance Checker, Section 508 Checker, EN 301 549 Checker.
What level is WCAG 3.3.2?
Level A, added in WCAG 2.0.
Sources
- W3C: Understanding 3.3.2 Labels or Instructions (opens in a new tab)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)
This page explains a technical standard and is not legal advice. See our disclaimer.