3.3.2 Labels or Instructions

1. What is the goal of this criterion?

Forms are at the heart of the modern web – from newsletter sign-ups and online banking to contact forms. But what if you’re looking at an input field and have no idea what’s expected? People with cognitive disabilities, learning difficulties or simply anyone under stress can quickly feel overwhelmed.

The goal of WCAG Success Criterion 3.3.2 is clear: every input field needs an understandable label or instruction. You should know immediately what information is expected – before you start typing and before mistakes happen.

2. What exactly does it require?

Specifically, it covers every place on a website where input is required. That means:

Every input field is labelled or explained: text fields, select menus, checkboxes, radio buttons – all of them need a clear label that says what should be entered.

Special formats are explained: if a date is expected as DD.MM.YYYY or a phone number with a country code, this must be communicated up front.

Required fields are recognisable: you need to know which fields you must fill in and which are optional.

Options have understandable labels: for radio buttons or checkboxes, it must be clear what each option stands for.

Important: this isn’t about technically associating labels with fields (that’s covered by Info and Relationships) or about programmatic names for screen readers (that’s Name, Role, Value) – it’s about everyone getting the information they need, visibly.

The criterion doesn’t ask you to overload every field with long explanations, either. Too much text can be just as much of a barrier as too little.

3. Why does it matter for accessibility?

Imagine filling in a form where you have to guess what every field means. That’s frustrating for everyone – for people with disabilities it can make the form impossible to complete.

Clear labels and instructions support accessibility because they:

• help people with cognitive disabilities or learning difficulties complete forms successfully
• reduce language barriers through clear descriptions and examples
• cut down the stress and confusion that lead to input errors
• spare people frustrating error messages
• save time because fewer corrections are needed
• build trust in the website through clear communication

And last but not least: they improve usability for everyone – including people without disabilities who just want to get through a form quickly and without mistakes.

4. How to meet the criterion

The good news: good labels and instructions are mostly a matter of writing, not technology. Here’s your roadmap to user-friendly forms:

Ground rules for labels:

• Use short, concise labels that make it immediately clear what’s being asked
• Place labels directly above or next to the related input field
• Avoid jargon – write the way your audience talks
• Mark required fields clearly, e.g. with the word “required” or with an asterisk that’s explained at the start of the form

Instructions and examples:

• Specify the expected format: “Date (DD.MM.YYYY)” rather than just “Date”
• Use examples: “Phone number (e.g. +49 30 1234567)”
• Explain special requirements: “Password (at least 8 characters, including 1 capital letter)”
• Use placeholder text only as a supplement, never as a replacement for labels – it disappears as you type and often has too little contrast

Proven tips from practice:

• Group related fields with fieldset and legend (e.g. address details)
• For more complex forms, explain the process up front in an introductory text
• Reveal additional fields step by step as they become relevant
• Test your forms with real users – ideally including people with disabilities

Tools and techniques:

• Associate label elements via the for attribute or by wrapping the input inside the label
• Use aria-describedby for longer explanations that are also visible
• Always combine the required attribute with a visible indicator
• Make sure the visible text is part of the accessible name (see Label in Name)

5. Why this criterion matters for businesses

With Success Criterion 3.3.2, too, accessibility isn’t an end in itself – it brings tangible benefits for your business.

1. Fewer drop-offs

Poor labels lead to abandonment. People who don’t understand what’s expected leave in frustration. Clear instructions reduce form abandonment and increase the success rate of sign-ups, orders and enquiries.

2. Less support effort

Confusing forms create support requests. When people don’t know how to fill in a field, they contact your customer service. Good labels and instructions reduce these requests and take pressure off your team.

3. Better data quality

Clear guidance leads to better data. When people know the expected format from the start, they make fewer input errors. That means fewer faulty records, less rework and more reliable customer data.

And then there’s the legal side: since 28 June 2025, the European Accessibility Act (Directive (EU) 2019/882) has applied to many consumer-facing digital services, such as online shops and banking services. Germany implements it through the Barrierefreiheitsstärkungsgesetz (BFSG). The technical benchmark is the harmonised standard EN 301 549, which refers to WCAG 2.1 Level AA for web content – and 3.3.2 is part of that. Public sector bodies are covered separately by the Web Accessibility Directive (EU) 2016/2102. This section is general information, not legal advice.

6. The success criterion in the W3C’s words

Success Criterion 3.3.2 Labels or Instructions (Level A)

Labels or instructions are provided when content requires user input.

In short: wherever content asks for input, there are labels or instructions that explain what to enter.