Skip to Content (Press Enter)

This document is a draft, and is designed to show changes from a previous version. It is presently showing added text,changed text,deleted text,[start]/[end] markers,and Issue Numbers.

Hide All Edits   |   Toggle Deletions  |   Toggle Issue Numbers   |   Toggle [start]/[end] Markers   |   Show All Edits

Changes are displayed as follows:


Labels or Instructions:
Understanding SC 3.3.2

3.3.2 Labels or Instructions: Labels or instructions are provided when content requires user input. (Level A)


Intent of this Success Criterion

The intent of this success criterion is to help users avoid making mistakes when their input is required. To help avoid mistakes it is good user interface design to provide simple instructions and cues for entering information. Some users with disabilities may be more likely to make mistakes than users without disabilities or recovery from mistakes may be more difficult, making mistake avoidance an important strategy for users with disabilities. People with disabilities rely on well documented forms and procedures to interact with a page. Blind users need to know exactly what information should be entered into form fields and what the available choices are. Simple instructions visually connected to form controls can assist users with cognitive disabilities or those accessing a page using a screen magnifier.

The intent of this success criterion is not to clutter the page with unnecessary information but to provide important cues and instructions that will benefit people with disabilities. Too much information or instruction can be just as much of a hindrance as too little. The goal is to make certain that enough information is provided for the user to accomplish the task without undue confusion or navigation.

Specific Benefits of Success Criterion 3.3.2:

  • Label elements associated with input elements insure that information about the input field is spoken by screen readers when the field receives focus.

  • Field labels located in close proximity to the associated field assist users of screen magnifiers because the field and label are more likely to visible within the magnified area of the page.

  • Providing examples of expected data formats help users with cognitive, language and learning disabilities to enter information correctly.

  • Clearly identifying required fields prevents a keyboard only user from submitting an incomplete form and having to navigate the redisplayed form to find the uncompleted field and provide the missing information.

Examples of Success Criterion 3.3.2

Related Resources

Resources are for information purposes only, no endorsement implied.

(none currently documented)

Techniques and Failures for Success Criterion 3.3.2 [Labels or Instructions]

Each numbered item in this section represents a technique or combination of techniques that the WCAG Working Group deems sufficient for meeting this success criterion. The techniques listed only satisfy the success criterion if all of the WCAG 2.0 conformance requirements have been met.

Sufficient Techniques

  1. G131: Providing descriptive labels AND one of the following:

  2. H44: Using label elements to associate text labels with form controls (HTML)

  3. H71: Providing a description for groups of form controls using fieldset and legend elements (HTML)

  4. H65: Using the title attribute to identify form controls when the label element cannot be used (HTML)

  5. [begin add]

    Using adjacent button to label the purpose of a field (future link) [2107]

    [end add]
[begin add]

Note: The techniques at the end of the above list should be considered "last resort" and only used when the other techniques cannot be applied to the page. The earlier techniques are preferred because they increase accessibility to a wider user group. [2107]

[end add]

Additional Techniques (Advisory)

Although not required for conformance, the following additional techniques should be considered in order to make content more accessible. Not all techniques can be used or would be effective in all situations.


The following are common mistakes that are considered failures of Success Criterion 3.3.2 by the WCAG Working Group.

(No failures currently documented)

Key Terms


text or other component with a text alternative that is presented to a user to identify a component within Web content

[begin change]

Note 1: A label is presented to all users whereas the name may be hidden and only exposed by assistive technology. In many (but not all) cases the name and the label are the same. [2200]

[end change]
[begin add]

Note 2: The term label is not limited to the label element in HTML. [2107]

[end add]