Category: WCAG Principles and Conformance

Error Prevention

Also known as: Mistake Proofing, Error Prevention (Legal, Financial, Data)

Simply put

Error prevention refers to designing forms and interactive processes so that people are less likely to make costly mistakes, and can catch or undo mistakes before they cause harm. This is especially important for actions with significant consequences, such as submitting legal, financial, or personal data. The goal is to help all users, including people with disabilities, avoid the negative outcomes of an accidental or mistaken submission.

Formal definition

In the WCAG context, Error Prevention is addressed by success criteria in the 3.3 (Input Assistance) family. Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data) is a Level AA requirement, while Success Criterion 3.3.6 Error Prevention (All), which extends the requirement to all pages that require the user to submit information, is a Level AAA criterion. Both are intended to help users avoid consequences resulting from mistakes when submitting data, and are generally satisfied by making submissions reversible, checking user input for errors and providing an opportunity to correct them, and/or providing a mechanism to review, confirm, and correct information before finalizing the submission. More broadly, in usability and UX practice, error prevention encompasses design strategies (sometimes called mistake proofing) that reduce the likelihood of user error before it occurs. Meeting these criteria does not by itself guarantee an accessible or usable experience for all users, and manual and assistive technology testing remain necessary.

Why it matters

Error prevention directly affects whether people can complete high-stakes tasks online without suffering avoidable harm. When a form submission commits a user to a legal agreement, moves money, or updates personal records, an accidental or mistaken entry can carry real consequences. The intent behind WCAG's error prevention success criteria is to help users with disabilities avoid the consequences that may result from making a mistake when submitting form data, but well-designed error prevention benefits all users who may be rushed, distracted, or working with an interface that does not clearly signal what a submission will do.

For people with disabilities, the stakes can be higher. Someone using a screen reader, voice control, or a switch device may find it harder to notice a small entry error, and undoing an unintended action can be more difficult than for a sighted mouse user. Building in the ability to reverse a submission, to check input for errors, or to review and confirm information before finalizing gives users a meaningful chance to catch problems before they cause damage.

Beyond the accessibility context, error prevention is a long-established principle in usability and process design. The concept of mistake proofing, for example, uses changes in the design of processes to reduce human error rather than relying on users to be perfectly careful. Applying these ideas to legal, financial, and data-entry workflows helps reduce costly errors while also supporting a more robust and predictable user experience. Meeting these criteria does not by itself guarantee an accessible or usable experience, and manual and assistive technology testing remain necessary.

Who it's relevant to

UX and Interaction Designers

Designers are responsible for building forms and interactive processes that reduce the likelihood of mistakes and give users a clear opportunity to catch or undo them. Applying error prevention strategies, such as review-and-confirm steps, reversible actions, and input checks, supports both the WCAG 3.3 success criteria and broader usability goals.

Front-End Developers and Engineers

Developers implement the mechanisms that satisfy Success Criteria 3.3.4 (Level AA) and 3.3.6 (Level AAA), including reversibility, input validation with correction opportunities, and confirmation screens. These implementations should be verified with manual and assistive technology testing, since meeting the criteria does not by itself guarantee an accessible experience.

Accessibility and Compliance Teams

Teams evaluating conformance need to distinguish the Level AA scope of 3.3.4 (legal, financial, and data-related actions) from the broader Level AAA scope of 3.3.6 (all information submissions). They should confirm that at least one qualifying mechanism is present for in-scope processes and document how it was tested.

Product and Business Owners

Owners of workflows involving legal commitments, financial transactions, or user data changes benefit from error prevention because it reduces the risk of costly mistaken submissions for all users. Decisions about which conformance level to target and how to handle high-stakes flows should account for both user impact and applicable requirements.

Legal and Risk Counsel

Counsel advising on digital accessibility should understand that error prevention is addressed through WCAG success criteria commonly cited as benchmarks, not through a single codified technical rule in the ADA itself. Requirements evolve through regulation and case law, and this entry is not legal advice; consult qualified counsel and current agency guidance for specific obligations.

Inside Error Prevention

WCAG Success Criterion 3.3.4 (Error Prevention - Legal, Financial, Data)

A Level AA success criterion introduced in WCAG 2.0 that applies to web pages causing legal commitments, financial transactions, data modifications or deletions in user-controllable data storage, or the submission of test responses. It requires that at least one of the following be provided: submissions are reversible, data is checked for input errors with an opportunity to correct them, or a mechanism is available to review, confirm, and correct information before finalizing.

WCAG Success Criterion 3.3.6 (Error Prevention - All)

A Level AAA success criterion in WCAG 2.0 that extends the same reversible, checked, or confirmable requirements to all submissions requiring information from the user, not only legal, financial, or data-related actions. Because it is Level AAA, it is generally not cited as a common conformance target.

Reversibility

One of the acceptable methods under the criteria, where a submission can be undone or canceled after the fact, reducing the consequence of an inadvertent action.

Error checking and correction

A method where user input is validated for detectable errors and the user is given the opportunity to correct them before finalizing a submission.

Review and confirmation step

A method where a mechanism allows the user to review, confirm, and correct information prior to committing an action such as a purchase, contract, or data change.

Common questions

Answers to the questions practitioners most commonly ask about Error Prevention.

Does meeting the Error Prevention success criterion mean my forms are legally compliant with the ADA?

No. Error Prevention is a WCAG success criterion, not a legal standard in itself. The ADA is a US civil rights law that does not contain detailed web technical specifications, though courts and settlements have often referenced WCAG as a benchmark. Meeting this criterion may support an accessibility conformance goal, but conformance does not guarantee legal compliance or immunity from claims. For questions about legal obligations, consult qualified legal counsel and monitor current agency rulemaking.

If my site passes automated accessibility checks, does that confirm Error Prevention is properly implemented?

Not necessarily. Automated testing detects only a portion of accessibility issues, and much of what Error Prevention addresses, such as whether users can reverse, check, or confirm consequential submissions, generally requires manual review and testing with assistive technology. Passing automated checks does not confirm that the criterion is fully met or that the experience is usable for all users.

Which WCAG conformance level includes Error Prevention, and is it the level typically targeted?

Error Prevention appears at more than one level within WCAG, with a broader Error Prevention criterion commonly associated with Level AA for contexts involving legal, financial, or data commitments, and a more stringent version at Level AAA. Level AA is the level most commonly cited as a conformance target. When planning, confirm the specific criterion and level against the WCAG version you are following, since criteria and their placement can differ across WCAG 2.0, 2.1, and 2.2.

What kinds of transactions should Error Prevention measures be applied to?

Error Prevention is generally most relevant to submissions with significant consequences, such as those that create legal commitments, involve financial transactions, modify or delete user-controllable data, or submit test responses. For these actions, providing mechanisms to reverse the submission, check and correct information before finalizing, or confirm before completion helps reduce the impact of mistakes.

What practical mechanisms can satisfy Error Prevention requirements?

Common approaches include allowing submissions to be reversed, providing a review step where users can check and correct their entries before finalizing, and offering an explicit confirmation step before the action is completed. Which mechanisms are appropriate generally depends on the nature and consequences of the action, and more than one may be used together.

How does Error Prevention differ from error identification and error suggestion?

Error Prevention focuses on helping users avoid or recover from mistakes in consequential submissions, through reversal, checking, or confirmation, before those mistakes take effect. Error identification and error suggestion address a different concern: detecting when an input error has occurred and, where possible, helping the user correct it. These are distinct WCAG concepts, and addressing one does not automatically address the others.

Common misconceptions

Error Prevention success criteria require you to prevent users from ever making mistakes.

The criteria do not require preventing all errors. They require offering at least one safeguard, reversibility, error checking with correction, or a review/confirm/correct step, for qualifying actions so that consequential mistakes can be caught or undone.

Meeting SC 3.3.4 makes a form fully accessible and legally compliant.

Satisfying a single success criterion does not guarantee an accessible experience or immunity from legal claims. Conformance is distinct from usability and from legal compliance, and automated testing detects only a portion of issues, so manual and assistive technology testing are also generally required.

Error Prevention (SC 3.3.4) applies to every form and submission on a site.

SC 3.3.4 at Level AA is scoped to pages that create legal or financial commitments, modify or delete user-controllable data, or submit test responses. Broader coverage of all submissions is addressed by SC 3.3.6, which is Level AAA and not commonly cited as a target.

Best practices

Identify which pages involve legal commitments, financial transactions, or data modification/deletion, and prioritize applying an Error Prevention safeguard to those flows to meet SC 3.3.4 at Level AA.

Choose at least one qualifying method per the criterion, reversibility, error checking with an opportunity to correct, or a review-confirm-correct step, and implement it in a way that is exposed to assistive technology.

Provide a clear confirmation or review screen before finalizing consequential actions so users can verify and correct information prior to submission.

Pair automated validation with manual and assistive technology testing, since automated checks alone detect only a portion of accessibility issues.

Where feasible, offer an undo or cancellation path so inadvertent submissions can be reversed after the fact.

Consider extending Error Prevention safeguards to all submissions to align with the stricter Level AAA criterion (SC 3.3.6), while recognizing AAA is generally beyond common conformance targets and treating this guidance as informational rather than legal advice.