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:


Error Identification:
Understanding SC 3.3.1

3.3.1 Error Identification: If an input error is [begin delete]automatically [2235] [end delete] detected, the item that is in error is identified and [begin add]the error is [2012] [end add] described to the user in text. (Level A)

Intent of this Success Criterion

The intent of this success criterion is to ensure that users are aware that an error has occurred and can determine what is wrong. The error message should be as specific as possible. In the case of an unsuccessful form submission, re-displaying the form and indicating the fields in error is insufficient for some users to perceive that an error has occurred. Screen reader users, for example, will not know there was an error until they encounter one of the indicators. They may abandon the form altogether before encountering the error indicator, thinking that the page simply is not functional.

The identification and description of an error can be combined with programmatic information that user agents or assistive technologies can use to identify an error and provide error information to the user. For example, certain technologies can specify that the user's input must not fall outside a specific range, or that a form field is required. Currently, few technologies support this kind of programmatic information, but the success criterion does not require, nor prevent it.

[begin add]

It is perfectly acceptable to indicate the error in other ways such as image, color etc, in addition to the text description. [2216]

[end add]

Specific Benefits of Success Criterion 3.3.1:

  • Providing information about input errors in text allows users who are blind or colorblind to perceive the fact that an error occurred.

  • This success criterion may help people with cognitive, language, and learning disabilities who have difficulty understanding the meaning represented by icons and other visual cues.

Examples of Success Criterion 3.3.1

Related Resources

Resources are for information purposes only, no endorsement implied.

Techniques and Failures for Success Criterion 3.3.1 [Error Identification]

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

Instructions: Select the situation below that matches your content. Each situation includes numbered techniques (or combinations of techniques) that the Working Group deems to be sufficient for that situation.

Situation A: If a form contains fields for which information from the user is mandatory.
  1. G83: Providing text descriptions to identify required fields that were not completed

Situation B: If information provided by the user is required to be in a specific data format or of certain values.
  1. G85: Providing a text description when user input falls outside the required format or values

  2. SCR18: Providing client-side validation and alert (Scripting)

  3. Providing client-side validation and adding error text via the DOM (future link)

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.1 by the WCAG Working Group.

(No failures currently documented)

Key Terms

input error

information provided by the user that is not accepted

Note: This includes:

  1. Information that is required by the Web page but omitted by the user

  2. Information that is provided by the user but that falls outside the required data format or values