Error Prevention: Safe Orders, Payments and Data
Also called: Error Prevention (Legal, Financial, Data), Submission safeguards, Order review step
Definition
Error prevention means that pages which create legal commitments or financial transactions, change or delete user data, or submit test answers give users a safety net: the submission is reversible, checked for errors, or can be reviewed and confirmed first. WCAG 3.3.4 requires it at Level AA.
Error prevention is the safety net for submissions that matter: a purchase, a contract, a tax return, a deleted account. Before such an action becomes final, users must be able to undo it, have their data checked, or review and confirm it. A single transposed digit in an IBAN or an accidental double tap should not cost anyone money.
What it means
WCAG 3.3.4 Error Prevention (Legal, Financial, Data) is a Level AA criterion of WCAG 2.2. It applies to web pages that cause legal commitments or financial transactions, that modify or delete user-controllable data in data storage systems, or that submit user test responses. For these pages, at least one of three safeguards must be in place:
| Option | WCAG wording | Typical solution |
|---|---|---|
| Reversible | "Submissions are reversible." | Cancel an order within a set time, restore deleted items |
| Checked | Input is "checked for input errors and the user is provided an opportunity to correct them." | Validate IBAN, dates and amounts before sending |
| Confirmed | "A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission." | A summary page with "Edit" and "Place order" |
W3C explains who benefits: people with reading disabilities may transpose numbers and letters, and people with motor disabilities may press keys by accident. For them, a mistake in a non-refundable purchase or a stock order can have serious consequences.
Examples
<h1>Review your order</h1>
<dl>
<dt>Item</dt><dd>Desk lamp, 2 × €39.00</dd>
<dt>Shipping address</dt><dd>Hauptstraße 12, 1010 Vienna</dd>
<dt>Payment</dt><dd>Card ending 4242</dd>
</dl>
<a href="/cart">Edit order</a>
<form method="post" action="/order">
<label><input type="checkbox" name="confirm" required>
I have checked my order</label>
<button type="submit">Place order</button>
</form>This combines two W3C techniques: G98 (letting users review and correct answers before submitting) and G155 (a checkbox next to the submit button). For deleting data, G168 (asking the user to confirm before continuing) or G99 (recovering deleted information) fit better.
Show a summary before payment, keep "Edit" links next to each section, offer a cancellation window (G164), validate entries with clear error identification and error suggestion, and let people restore deleted items.
Charge the card on the first click without a review step, delete an account instantly with no way back, or submit an exam the moment the last answer is chosen.
How to check error prevention
Questions
What is WCAG 3.3.4 Error Prevention?
It is a Level AA success criterion. Pages with legal commitments, financial transactions, data deletion or test submissions must be reversible, checked for errors, or offer a way to review and confirm before the submission is final.
Do I need all three options – reversible, checked and confirmed?
No. WCAG requires at least one of them. Many shops combine a review page with input checks, which is more robust than relying on one safeguard.
Is a confirmation checkbox enough?
A checkbox next to the submit button is a W3C sufficient technique (G155) for purchases and deletions. It works best when the page also shows the data being confirmed.
Does every form need a confirmation step?
No. The criterion covers pages that cause legal commitments or financial transactions, change or delete user-controllable data, or submit test answers. A contact form or a search field is not in scope, although clear error messages help there too.
Does the European Accessibility Act require error prevention?
The European Accessibility Act points to EN 301 549, which contains WCAG Level AA for web content. 3.3.4 is Level AA, so it applies to online shops and banking services in scope.
Related terms
Error Identification: Clear Form Error Messages
Error identification means that when a website detects an input error automatically, it points out the field in error and describes the problem to the user in text. It is required by WCAG 3.3.1 at Level A.
Read definition: Error Identification: Clear Form Error MessagesError Suggestion: Help Users Fix Form Errors
Error suggestion means that when a website detects an input error and knows how it could be corrected, it offers that correction to the user. WCAG 3.3.3 requires it at Level AA, unless it would jeopardize security or the purpose of the content.
Read definition: Error Suggestion: Help Users Fix Form ErrorsForm Labels: Clear Labels and Instructions
Form labels are the visible texts that name what a form field expects, such as “Email address”. WCAG 3.3.2 requires labels or instructions wherever content asks for user input, including formats and required fields.
Read definition: Form Labels: Clear Labels and InstructionsStatus Messages: Announce Updates Without Focus
Status messages are changes in content that tell users about the result of an action, a waiting state, the progress of a process or the existence of errors, without changing the context. WCAG 4.1.3 requires that they can be programmatically determined, so assistive technologies can present them without giving them focus.
Read definition: Status Messages: Announce Updates Without Focus