Level
AA
Since
WCAG 2.0
/ WCAG criterion

3.3.4 Error Prevention (Legal, Financial, Data)

Before a submission that commits a person legally or financially, changes or deletes their stored data, or sends test answers, it must be reversible, checked for errors, or open to review and confirmation.

/ What it requires

Some submissions cannot be taken back without cost: a non-refundable ticket, a stock order, a signed contract, a deleted account, the answers to an exam. People with reading disabilities may swap two digits, and people with motor disabilities may press a key they did not mean to press. This criterion applies to web pages that cause legal commitments or financial transactions for the user, that modify or delete user-controllable data in data storage systems, or that submit user test responses. Those are the pages where a slip turns into a real loss.

On such pages at least one of three things must be true. Reversible: the submission can be undone. Checked: the data the user entered is checked for input errors and they get a chance to correct them. Confirmed: a mechanism lets them review, confirm and correct the information before the submission becomes final. One of the three is enough, and the criterion names no other exceptions. Forms outside this scope are not covered at level AA; the AAA criterion 3.3.6 Error Prevention (All) applies the same options to every page that asks the user to submit information.

/ How pages fail it

  • A checkout charges the card the moment Pay is pressed, with no summary, no check of the details and no way to cancel the order afterwards.
  • A Delete account button removes the account and its data at once, with no confirmation step and no period in which it can be restored.
  • An online exam sends the answers on the first click of Submit, with no review of unanswered questions and no way to change an answer.
  • A contract form submits the signed agreement without checking the entered details and without a step to review them, and the agreement cannot be withdrawn online.
  • A transfer form executes the payment with no screen that shows the recipient and the amount for confirmation.

/ How to check it yourself

  1. List the actions on the site that fall within scope: purchases, payments, bookings, contracts, changes to or deletion of stored user data, and submitted tests.
  2. Complete each one in a test environment or with a test account, and note whether a review step shows what will be submitted, with a way back to correct it.
  3. If there is no review step, check whether the action can be reversed afterwards, for example by cancelling the order or restoring a deleted item.
  4. If neither applies, check whether the data is validated and the user can correct it before anything is final.
  5. Go through the review step with the keyboard alone and with a screen reader such as NVDA, so that the summary and the confirm and edit buttons are reachable and named.

/ How to fix it

  • Add a review page before the final submission that lists the entered details, with an Edit link back to each step and a clearly labelled confirm button such as "Pay 49.00 EUR".
  • For destructive actions such as deleting an account or a record, open a confirmation dialog built with the dialog element or role="dialog" that names what will be deleted.
  • Offer undo or a grace period: move deleted items to a bin, or let an order be cancelled for a while after it is placed.
  • Validate input on the client and on the server, and return the user to the form with the errors described before anything is charged or saved.
  • For tests, show a summary of the answers, mark unanswered questions, and ask for a final confirmation before submitting.

/ What our scanner checks

Our scan has no check for this criterion and cannot have one. It never submits a form, places an order or deletes anything, and whether a step can be reversed or reviewed only shows when a transaction is carried through to the end. HTML_CodeSniffer reports only a reminder, which is dropped. In a manual audit a person walks the purchase, deletion and test flows on a test account.

/ Who fails it, in our own measurements

The weekly index has no figures for this criterion, because none of the checks the site scan runs can test it. A person judges it, which is what a manual audit is for.

One page per body, measured by automated checks on a weekly schedule. Any body that has fixed something since the last sweep will show it at the next one, and every entity page carries a right of reply.

/ Questions about this criterion

Does every form need a confirmation page?

No. 3.3.4 covers pages that cause legal commitments or financial transactions, that change or delete user-controllable stored data, or that submit test responses. Even there a confirmation page is only one of three options. A reversible submission, or a check for errors with a chance to correct them, also meets the criterion.

Is the option to cancel an order after purchase enough?

It can be, because Reversible is one of the three ways to meet the criterion. The reversal has to actually undo the submission. A non-refundable purchase is not reversible, so it needs a check of the entered data or a review step before it becomes final.

What level is 3.3.4 Error Prevention (Legal, Financial, Data)?

Level AA, part of WCAG since 2.0. The AAA criterion 3.3.6 Error Prevention (All) asks for the same three options on every page that requires the user to submit information, not only on legal, financial and data pages.