Loading content...
Loading content...
Prevent serious errors by allowing reversal, checking, or confirmation.
Why it matters: Prevents costly or irreversible mistakes.
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: (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.
What This Means: This success criterion requires that for actions with serious consequences (legal commitments, financial transactions, data modifications/deletions, test submissions), at least one of three safeguards must be in place: (1) Submissions are reversible (can be undone), (2) Data is checked for errors and users can correct them, or (3) Users can review, confirm, and correct information before finalizing.
Why It's Important: Serious actions like financial transactions or legal commitments can have costly or irreversible consequences if made in error. Users with motor disabilities may accidentally click buttons, and all users can make mistakes. Providing safeguards like reversibility, error checking, or confirmation helps prevent serious errors and gives users confidence in completing important actions.
For financial transactions, provide a confirmation step before processing. For data modifications, allow users to undo changes. For form submissions, check for errors and allow corrections. Implement at least one of these safeguards for serious actions. Make confirmation steps clear and easy to understand. Provide clear information about what action will be taken.
This criterion ensures that all users can access and understand the content, improving their overall experience and ability to use the website effectively.
This criterion ensures that users with motor disabilities can access and understand the content, improving their overall experience and ability to use the website effectively.
Impact: When this criterion is properly implemented, it removes barriers for these user groups and creates a more inclusive web experience for everyone.
This success criterion benefits the following user groups:
Tip: Use this checklist during development and testing to ensure all requirements for 3.3.4 Error Prevention (Legal, Financial, Data) are met. Check off items as you complete them.
Note: These are official W3C resources for 3.3.4. For the most up-to-date information and detailed technical guidance, always refer to the official W3C documentation.
Implementing 3.3.4 Error Prevention (Legal, Financial, Data) correctly requires understanding your specific context. Code solutions vary significantly based on multiple factors:
HTML, React, Vue, Angular, PHP, Python, and other frameworks each have different patterns and best practices.
Server-side rendering, client-side rendering, static generation, and hybrid approaches require different solutions.
Your existing components, styling approach, and UI library influence how accessibility must be implemented.
Your specific user base, content type, and interaction patterns determine the most appropriate implementation.
We provide tailored implementation guidance by analyzing your specific technology stack, coding patterns, design system, and project requirements. Our team reviews your codebase and provides custom solutions that integrate seamlessly with your existing architecture.
Get Custom Implementation HelpPart of
Understandable PrincipleGuideline
3.3 Input Assistance