Level AAUnderstandable
3.3.4

Error Prevention (Legal, Financial, Data)

For purchases, legal commitments, or data changes, let people review, correct, or undo before it's final.

In plain English

Some actions are hard to take back: buying something, agreeing to terms, deleting an account. A slip there costs real money or data. This rule says that for those high-stakes actions you must do at least one of three things: make it reversible, check it for errors and let people fix them, or ask them to review and confirm before it is final.

For a store, the obvious case is checkout: show an order-review step before the charge.

Who this is for

  • People with cognitive, motor, or vision differences, who are more prone to input slips.
  • Everyone, who occasionally fat-fingers a quantity or an address.

How to check and fix it yourself

Walk through your checkout and any account/data-deletion flows. Before the irreversible step, is there a review or confirmation?

Checkout → an order-review screen (items, address, total) → Confirm & pay.  ✓
Delete account → "Are you sure? This can't be undone." confirmation.        ✓
Financial action that commits instantly with no review.                     ✗

Where we can help

Most checkouts have a review step, but custom flows, one-click actions, and account changes sometimes skip it. We check your high-stakes flows for a review, confirm, or undo safeguard. It is a checkout-critical item you can spot in a self-check.

How to meet it

Techniques the W3C accepts as sufficient (summarized). Follow a link for the full method.

Frequently asked questions

What does error prevention (legal, financial, data) require?+

Success Criterion 3.3.4 (Level AA) says that for pages that create a legal commitment, a financial transaction, or that change or delete user data, submissions must be at least one of: reversible, checked for errors with a chance to correct, or confirmed (the user reviews and confirms before it's final).

How does this apply to a store's checkout?+

Checkout is a financial transaction, so it needs one of those safeguards. A review step where the customer sees their order, address, and payment and confirms before paying is the usual way stores comply, and it reduces mistaken orders for everyone.

Why does this matter for accessibility specifically?+

People with cognitive, motor, or vision differences are more likely to make an input slip, a wrong quantity, a mistyped address. A review-and-confirm step (or the ability to undo) gives everyone a chance to catch it before money changes hands or data is lost.

Reference

This is a plain-language explainer. The authoritative source is the W3C Web Content Accessibility Guidelines (WCAG) 2.2.

WCAG 2.2 © W3C. Excerpts are paraphrased; see the linked documents for the normative text.

Not sure if your store passes 3.3.4?

A human auditor checks this and every other criterion against your live store, and documents the result.

Book an audit