3.3.6 Error Prevention (All)
For web pages that require the user to submit information, submissions are reversible, checked, or confirmed.
What this rule means
WCAG 3.3.6 extends 3.3.4 to ALL forms, not just those with legal/financial/data consequences. Every form submission should be reversible, checked for errors, or include a confirmation step.
This is the AAA enhancement — while 3.3.4 requires this only for high-stakes forms, 3.3.6 applies it universally.
Why it matters
Any form submission can cause problems for users with disabilities. A contact form, a search, a feedback submission — all benefit from error prevention safeguards. This criterion ensures the highest level of protection against user errors.
Related axe-core rules
There are no automated axe-core rules for this criterion.
How to test
- Identify all forms that submit user data.
- Verify at least one safeguard exists for each: reversibility, validation, or confirmation.
How to fix
Apply the same techniques as 3.3.4 to all forms: confirmation pages, undo mechanisms, client-side validation before submission, and review steps.
Common mistakes
- Simple forms (contact, feedback) that submit without any confirmation.
- Search forms that navigate away without the ability to refine or go back.