The WCAG Explained

Simplified and actionable explanations of every WCAG 2.2 criteria

Labels or Instructions

Summary:
WCAG 3.3.2, "Labels or Instructions," focuses on ensuring that users receive clear guidance when entering data. This is especially important for those with cognitive disabilities, visual impairments, or anyone unfamiliar with the specific format or requirements of the input fields.

What:
The guideline mandates providing labels or instructions for user input to facilitate accurate data entry. This means that wherever a user needs to input data, they should have clear, easy-to-understand directions on what and how to enter it.

Why:
Clear labels and instructions help prevent errors by guiding users on how to complete forms or other input fields, making web content more accessible and user-friendly.

Examples and Scenarios:

  1. Contact Forms: Including a label or instructions on what to enter in each field (e.g., 'Enter your full name').
  2. Account Registration: Providing specific instructions for password creation requirements (like minimum length or required characters).
  3. Search Bars: Labeling the search input field with text like 'Search by keyword or item number'.

How to Comply:

  • Websites: Ensure that each input field has a descriptive label or instructions nearby. Use HTML label elements for form fields and provide additional instructions where needed.
  • Mobile Apps: Labels and instructions should be clearly associated with corresponding input fields in the app interface.
  • Software Applications: Similar to websites, include clear labels and instructions for any data entry points in the application.

Exceptions:

  • Self-explanatory Fields: If the purpose of the field is obvious from its context, additional labels or instructions may not be necessary (like a search field in a search engine).
  • User Familiarity: In applications or contexts where users are expected to be familiar with the type of input required, detailed instructions might be redundant.