Published November 1, 2026
WCAG 3.3.2 Labels or Instructions, Level A
Does WCAG require labels on form fields?
Yes at Level A. Success criterion 3.3.2 Labels or Instructions requires that labels or instructions are provided when content requires user input. An unlabeled field, or a field that relies only on placeholder text, fails. The text is in the W3C WCAG 2.2 Recommendation.
What counts as a label or instruction?
A visible label that stays on screen while the field is filled, such as a label element tied with for and id, or a fieldset legend for a group. Instructions cover required formats, expected units, or password rules that are not obvious from the label alone. The W3C explanation is in Understanding Success Criterion 3.3.2. How those labels become accessible names is on the accessible names page. Broader form patterns are on the accessible forms page.
Does a placeholder meet 3.3.2?
No. Placeholder text vanishes once the user starts typing, and it is often styled below the contrast needed for body text. It can hint at a format, but it does not replace a persistent label. Keep format hints visible next to the field, and do not use color alone to mark required fields, as covered on the use of color page.
How do labels relate to errors and status?
3.3.2 is about naming and instructing before and during input. Identifying which field failed is 3.3.1 Error Identification, covered on the error identification page. Suggesting a known fix is 3.3.3 Error Suggestion, covered on the error suggestion page. Announcing a success or error toast without moving focus is 4.1.3, covered on the status messages page. A name, email, or telephone field that already has a visible label still needs a programmatically determined purpose under 1.3.5, covered on the identify input purpose page. A field can have a correct label and still fail those other criteria.
Does the Title II web rule include labels or instructions?
Yes. The Department of Justice rule for state and local government websites names WCAG 2.1 Level AA. That level includes 3.3.2 at Level A. Governments with a population of 50,000 or more have until April 26, 2027. Smaller governments and special districts have until April 26, 2028. Who must comply is on the Title II web rule page. A scanner can flag a missing label. It often cannot tell that a placeholder was treated as the only instruction. A person checks that, which is why a passing score is not conformance, as covered on the scanner page. The fix belongs in the form templates, which is remediation.
Questions and answers
Does WCAG require labels on form fields?
Yes at Level A. Success criterion 3.3.2 Labels or Instructions requires that labels or instructions are provided when content requires user input. A field with only a placeholder, or with no name at all, fails. Specification: https://www.w3.org/TR/WCAG22/#labels-or-instructions
Does a placeholder count as a label?
No. A placeholder disappears when the user types and is often low contrast. 3.3.2 expects a persistent label or instruction. Pair the label with a programmatic accessible name, covered on the accessible names page: https://www.adasupport.org/aria-labels
Do instructions replace the label?
No. Instructions such as a date format or password rules can sit next to the field, often via aria-describedby. The control still needs a label that names what the field is for. Form patterns are on the accessible forms page: https://www.adasupport.org/accessible-forms
Does the Title II web rule include labels or instructions?
Yes. The DOJ rule names WCAG 2.1 Level AA, which includes 3.3.2 at Level A. Governments of 50,000 or more have until April 26, 2027. Smaller governments and special districts have until April 26, 2028. Deadlines: https://www.adasupport.org/title-ii-web-rule
Related guides
Ask for a review of a specific page
Send the URL and the template you care about. The reply names the highest-risk WCAG failures and the order to fix them.
Request an audit