Understanding Error Identification

Intent of Error Identification

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. Per the definition in WCAG 2.0, an "input error" is information provided by the user that is not accepted. This includes:

For example:

If a user enters a value that is too high or too low, and the coding on the page automatically changes that value to fall within the allowed range, the user's error would still need to be described to them as required by the success criterion. Such an error description telling the person of the changed value would meet both this success criterion (Error Identification) and Success Criterion 3.3.3 (Error Suggestion).

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.

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

See also 3.3.1: Error Suggestion.

Benefits of Error Identification

Examples of Error Identification

Resources for Error Identification

Techniques for Error Identification

Sufficient Techniques for Error Identification

Situation A: If a form contains fields for which information from the user is mandatory.

  1. Providing a text description that identifies the field as mandatory
  2. Providing client-side validation and alert

Situation B: If information provided by the user is required to be in a specific data format or of certain values.

  1. G84: Providing a text description when the user provides information that is not in the list of allowed values
  2. Providing a text description when user input falls outside the required format or values
  3. Providing client-side validation and alert
  4. Providing client-side validation and adding error text via the DOM
  5. Providing client-side validation and adding error text via the accessible description

Additional Techniques (Advisory) for Error Identification

Failures for Error Identification