3.3: Input Assistance
Guideline 3.3: Help users avoid and correct mistakes.
In a web application it is important to alert users when they made a mistake and help them correct it. This guideline, however, is to prevent mistakes to the greatest possible extent, and also to help correcting mistakes when necessary. The best way of avoiding mistakes is to provide information on what kind of input is needed.
3.3.1: Error Identification (Level A)
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)
This success criteria ensures that all errors are communicated to the user. It is allowed to alert the user of an error by using visual or audio warnings, but in addition, it is required to provide a textual equivalent of the error. For example, when the user makes an error filling in a form, you can indicate it by using a different color to easily identify it visually, but you also have to describe the error no matter how small it is.
3.3.2: Labels or Instructions (Level A)
Labels or instructions are provided when content requires user input. (Level A)
When the user has to enter information, do not assume that the user knows what needs to be entered. Always provide a label which clearly identifies the field and states what needs to be filled into the field.
3.3.3: Error Suggestion (Level AA)
If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. (Level AA)
When suggestions are available to correct a mistake, always provide those suggestions to the user.
The only exception is when you would decrease the security of the system by providing a suggestion. For example, when the user types the wrong password, if you would provide suggestions, you could increase unauthorized use of the system.
3.3.4: Error Prevention (Legal, Financial, Data) (Level AA)
For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: (Level AA)
- Reversible: Submissions are reversible.
- Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
- Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
Apply extra measures when the entered information is legally binding, or requires a financial commitment. For example, when the user makes a commitment to purchase an item with a credit card, or provides personal information.
Before the user makes the final confirmation, allow a method to cancel the submission.
Check the submitted data and make sure that it is free of errors.
When errors are found, allow the user to correct the mistakes.
Provide the user with an option to review the entered information, and to withdraw a confirmation when the information is not valid, or simply if the user decides not to submit the data.
3.3.5: Help (Level AAA)
Context-sensitive help is available. (Level AAA)
Wherever available and appropriate, provide the user with additional help related to the current fields and screen. For example, when filling in a date, while the field label would only say "date", provide additional information on the required date format.
3.3.6: Error Prevention (All) (Level AAA)
For Web pages that require the user to submit information, at least one of the following is true: (Level AAA)
- Reversible: Submissions are reversible.
- Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
- Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
This success criterion is very similar to 3.3.4. The only difference is that while 3.3.4 only requires error prevention for legally binding forms or financial commitments, in order to bring your application to Level AAA conformance, provide the same measures for all forms where the user enters data.
Bookmark/Search this post with:
Post new comment