Return to list of success criteria
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
Note: Other techniques may also be sufficient if they meet the success criterion.
G83: Providing text descriptions to identify required fields that were not completed
ARIA21: Using Aria-Invalid to Indicate An Error Field (ARIA)
SCR18: Providing client-side validation and alert (Scripting)
SL35: Using the Validation and ValidationSummary APIs to Implement Client Side Forms Validation in Silverlight (Silverlight)
ARIA19: Using ARIA role=alert or Live Regions to Identify Errors (ARIA)
ARIA21: Using Aria-Invalid to Indicate An Error Field (ARIA)
G85: Providing a text description when user input falls outside the required format or values
SCR18: Providing client-side validation and alert (Scripting)
SCR32: Providing client-side validation and adding error text via the DOM (Scripting)
FLASH12: Providing client-side validation and adding error text via the accessible description (Flash)
PDF22: Indicating when user input falls outside the required format or values in PDF forms (PDF)
SL35: Using the Validation and ValidationSummary APIs to Implement Client Side Forms Validation in Silverlight (Silverlight)
G139: Creating a mechanism that allows users to jump to errors
Validating form submissions on the server (future link)
Re-displaying a form with a summary of errors (future link)
Providing error notification as the user enters information (future link)
Including error notification information in the page title (future link)
Highlighting or visually emphasizing errors where they occur (future link)
Supplementing text with non-text content when reporting errors (future link)
G199: Providing success feedback when data is submitted successfully
Using sounds to focus user's attention (future link)