WCAG (Level AAA) SC 3.3.6 Error Prevention (All) (w3.org)
Issue description
WCAG 3.3.6, “Error Prevention (All)” expands upon the WCAG (Level AA) SC 3.3.4 Error Prevention (Legal, Financial, Data) by recommending error prevention mechanisms for all types of forms and input fields, not just those with legal, financial, or data-related consequences. This Level AAA criterion recognizes that errors in any form can be frustrating and create barriers for users, especially those with cognitive disabilities.
While preventing errors in sensitive forms is crucial, errors in any type of form can still cause problems for users:
- Wasted time and effort: Users might need to re-enter information or repeat steps if they make mistakes.
- Frustration and confusion: Errors can lead to frustration and confusion, especially if it’s not clear how to correct them.
- Accessibility barriers: Users with cognitive disabilities might be more prone to errors and may need additional support to avoid them.
WCAG requirements
This guideline recommends that for all forms and input fields, at least one of the following is true:
- Reversibility: Submissions are reversible, allowing users to undo actions or recover from errors.
- Checked for input errors: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them before submitting.
- Confirmed by the user: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
Benefits
- Reduced errors: Error prevention mechanisms help users avoid making mistakes in the first place.
- Improved user experience: It creates a more user-friendly and less frustrating experience for everyone.
- Increased efficiency: It helps users complete forms more quickly and efficiently.
- Enhanced accessibility: It makes forms more accessible to users with cognitive disabilities.
Essentially, this guideline encourages websites to implement error prevention mechanisms for all types of forms, not just those with critical consequences. This promotes a more inclusive and user-friendly experience for everyone, by helping users avoid errors and complete tasks more easily.
Related requirements
The following WCAG source criteria are often related to this as well. They can provide additional insights into specific challenges you may be encountering.
Who this issue impacts
Follow the links for additional information on user impairments:
Suggestions for remediation
Remediating WCAG 3.3.6, “Error Prevention (All)” involves implementing mechanisms to help users avoid and correct errors in all forms and input fields, not just those with legal, financial, or data-related consequences. Here’s how:
Reversibility
- Undo functionality: Provide a way for users to undo or reverse submissions. This could be an “Undo” button, a history of recent actions, or a way to revert to a previous state.
- Confirmation pages: Use confirmation pages or dialogs that allow users to review and confirm their submission before it is finalized.
- Reversible actions: Design the system so that actions can be reversed if necessary (e.g., allow users to cancel orders, restore deleted items, or edit submitted information).
Error checking
- Input validation: Implement robust input validation to check for errors in real-time as the user enters data. This includes:
- Data type validation: Ensure the user enters the correct type of data (e.g., numbers in a number field, email addresses in an email field).
- Format validation: Check that the data is in the correct format (e.g., dates, phone numbers).
- Range validation: Check that the data falls within an acceptable range (e.g., age, quantity).
- Clear error messages: Provide clear and specific error messages that explain the error and how to correct it.
- Highlight errors: Visually highlight fields with errors to draw the user’s attention.
Confirmation mechanisms
- Review and confirmation: Provide a mechanism for users to review and confirm the information before submitting the form. This could be a summary page or a confirmation dialog.
- “Are you sure?” prompts: For critical actions, use “Are you sure?” prompts to confirm the user’s intent before proceeding.
- Clear calls to action: Use clear and unambiguous calls to action (e.g., “Submit,” “Confirm,” “Save”) to avoid accidental submissions.
Testing
- Test different scenarios: Test the form with various input errors and scenarios to ensure that the error prevention mechanisms are effective.
- Assistive technology testing: Test with screen readers to ensure that error messages and confirmation prompts are conveyed correctly to users.
- User testing: Conduct user testing with people with cognitive disabilities to get feedback on the usability and effectiveness of the error prevention mechanisms.
Examples
- Contact form: Provide a confirmation page that shows the user’s entered information before submitting the form.
- Survey: Allow users to review and change their answers before submitting the survey.
- Account settings: Provide an “Undo” button after users update their account information.
By implementing these techniques, you can help users avoid errors, improve user confidence, and make your website more accessible to everyone, regardless of their cognitive abilities. This promotes a more inclusive and user-friendly experience for all.
