Success Criteria

WCAG 3.3.4 Error Prevention (Legal, Financial, Data)

Success Criterion 3.3.4 requires that for pages causing legal commitments or financial transactions, submissions the user controls that modify or delete stored data, or submissions to a testing mechanism, at least one of three safeguards is in place: reversibility, verification, or confirmation. It's a Level AA criterion under Guideline 3.3 (Input Assistance).

Why this specific category of action gets extra protection

Most form errors are annoying but recoverable — you fix a typo and resubmit. Legal agreements, financial transactions, and data deletion are different: a mistake here can have real, sometimes irreversible consequences (money sent to the wrong account, a contract accepted by accident, important data permanently deleted). This criterion exists to give users a final safety check specifically before consequential, hard-to-undo actions — a higher bar than ordinary form validation.

The three accepted safeguards (at least one required)

Reversible — the action can be undone afterward (a cancellable order within a return window, an "undo" option after deletion).

Checked for errors — submitted data is automatically validated and the user is given an opportunity to correct identified errors before final submission.

Confirmed — a review step shows the user what they're about to submit, requiring an explicit confirmation before it's finalized (a checkout order summary with a "Confirm order" button, rather than the initial "Submit" already being final).

Where this applies concretely

• E-commerce checkout — an order review/confirmation screen before payment finalizes
• Account or subscription cancellation — a confirmation dialog before an irreversible cancellation
• Bulk delete actions in a dashboard — a confirmation step, or an undo window after deletion
• Signing a legal agreement or terms acceptance — a clear review step rather than an accidental single click

Practical guidance

This is one of the few WCAG criteria that maps directly onto product/UX best practice already followed by most well-built e-commerce and SaaS platforms — a confirmation step before checkout, an "are you sure?" dialog before deleting an account. Sites that already follow standard, careful UX conventions for consequential actions typically satisfy this criterion without dedicated extra accessibility work; the risk is mainly in newer, fast-shipped features that skip the confirmation step in the name of a "frictionless" flow.

Common questions

What is WCAG 3.3.4?

A Level AA criterion: for pages causing legal commitments, financial transactions, or data changes/deletions, submissions must be reversible, validated, or subject to a confirmation step.

Which pages does it apply to?

Checkouts, legal agreements, test submissions, and anything that deletes or modifies user data — not ordinary forms like a newsletter signup.

How do I comply?

Offer at least one of: the ability to undo the submission, error checking with a chance to correct, or a review-and-confirm step before it is final.