Return to list of success criteria

3.3.1 Error Identification [Level A]

Description

Error Identification

3.3.1 If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. (Level A)Understanding Success Criterion 3.3.1

Back to top

Sufficent Techniques

Sufficient Techniques for 3.3.1 - Error Identification

Note: Other techniques may also be sufficient if they meet the success criterion.

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

  2. ARIA21: Using Aria-Invalid to Indicate An Error Field (ARIA)

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

  4. PDF5: Indicating required form controls in PDF forms (PDF)

  5. SL35: Using the Validation and ValidationSummary APIs to Implement Client Side Forms Validation in Silverlight (Silverlight)

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

  1. ARIA18: Using aria-alertdialog to Identify Errors (ARIA)

  2. ARIA19: Using ARIA role=alert or Live Regions to Identify Errors (ARIA)

  3. ARIA21: Using Aria-Invalid to Indicate An Error Field (ARIA)

  4. G84: Providing a text description when the user provides information that is not in the list of allowed values

  5. G85: Providing a text description when user input falls outside the required format or values

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

  7. SCR32: Providing client-side validation and adding error text via the DOM (Scripting)

  8. FLASH12: Providing client-side validation and adding error text via the accessible description (Flash)

  9. PDF22: Indicating when user input falls outside the required format or values in PDF forms (PDF)

  10. SL35: Using the Validation and ValidationSummary APIs to Implement Client Side Forms Validation in Silverlight (Silverlight)

Advisory Techniques

Advisory Techniques for 3.3.1 - Error Identification

Back to top

Failures

Back to top

Notes

Back to top