Reduce the risk of input errors for sensitive data
All users make mistakes when inputting data (for example, into forms and checkouts). You should try to prevent errors occurring, especially when users are committing to legal or financial agreements, or otherwise sharing their data.
Users can make costly mistakes if they don’t fully understand the implications of their actions or can’t rectify their errors. Error prevention is all about reducing risk to your users by adding in confirmation stages to processes that pose a legal or financial risk.
What to do
To pass this guideline, you need to make sure that:
- Legal commitments, financial transactions, test responses and changes to user controlled data are reversible; or
- Legal commitments, financial transactions, test responses and changes to user controlled data are checked for input errors and the user is given a chance to correct any mistakes; or
- Add a confirmation page to the data input submission process that summarises the input and the outcome, with an option to correct or discontinue. This page has an input field (for example, a confirm button or checkbox) that acts as confirmation of the submission.
- Guideline 3.3.6 widens this guideline to include all types of data transfer, not just these high-cost transactions.
- This guideline applies to deletion of data as well as submission.
- Legal commitments are transactions where the user incurs a legally binding obligation or benefit.
User controlled datameans things like name and address fields for a user’s account.
- Provide a confirmation webpage that gives the user a chance to read a summary of everything they have input and positively confirm their actions (especially if inputs were spread over several pages in the process).
- Validate forms inline and add an error message if input is incorrect. Be specific in explaining how to fix mistakes.
- Guideline 3.3.1 – Error Identification
- Guideline 3.3.3 – Error Suggestion
- Guideline 3.3.6 – Error Prevention (All)
Free Developer Resources
Join over 2,000 accessibility fans and get free developer resources like WCAG 2.0 Checklists and a sample from my book.
Over 250 people just like you have learned more about WCAG 2.0 with my guidebook.