Loading...
Loading content...
Loading content...
Prevent errors on ALL forms, not just legal/financial ones.
Why it matters: Prevents mistakes on any type of form submission.
For Web pages that require the user to submit information, 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 ALL forms (not just legal or financial ones), at least one of three error prevention mechanisms 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: This is a stricter version of 3.3.4 (Error Prevention for Legal, Financial, Data), requiring error prevention for all forms, not just those with serious consequences. Preventing errors on all forms helps all users, especially those with motor disabilities who may accidentally submit forms, and reduces frustration from mistakes.
Implement at least one error prevention mechanism for all forms. Provide confirmation steps before submission. Allow users to undo submissions. Check for input errors and allow corrections. Make confirmation steps clear and easy to understand. Provide clear information about what will happen when the form is submitted.
This criterion ensures that all users 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.
A form submits immediately without confirmation or ability to undo.
<form onsubmit="submitForm()">
<input type="text" name="name">
<button type="submit">Submit</button>
</form>A form requires confirmation before submission.
<form onsubmit="return confirm('Are you sure you want to submit?')">
<input type="text" name="name">
<button type="submit">Submit</button>
</form>This success criterion benefits the following user groups:
Tip: Use this checklist during development and testing to ensure all requirements for 3.3.6 Error Prevention (All) are met. Check off items as you complete them.
Note: These are official W3C resources for 3.3.6. For the most up-to-date information and detailed technical guidance, always refer to the official W3C documentation.
Implementing 3.3.6 Error Prevention (All) 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