3.3.4 Error Prevention (Legal, Financial, Data)

1. What is the goal of this criterion?

One click too many – and you’ve bought the wrong shares, booked a flight for the wrong date or deleted important data for good. In the digital world, small slips can have big consequences, especially when money or important information is at stake.

So the goal of WCAG Success Criterion 3.3.4 is clear: for critical actions – financial transactions, legal commitments, or changing and deleting data – people must be protected from serious mistakes. The system has to offer at least one safeguard: undo, check or confirm.

2. What exactly does it require?

Specifically, it applies to pages and applications that do something in one of three critical areas:

Financial and legal transactions: as soon as real money changes hands or legal commitments arise (purchases, contracts, tax returns).

Changing or deleting data: when you modify or delete data under your control in a storage system – such as profile data, saved documents or entire accounts.

Submitting test responses: in online exams and tests where answers are submitted.

In these cases, at least one of three safeguards must be in place:

• Reversible: the submission can be undone (e.g. cancellation within a certain period)
• Checked: the system checks the input for errors and gives you a chance to correct them
• Confirmed: before final submission, there’s a way to review, confirm and correct all the information

Important: you only need to implement one of these three mechanisms – not all three at once.

3. Why does it matter for accessibility?

Imagine booking a flight and mistyping the date – and only noticing when you’re standing at the airport. Or accidentally deleting your entire email archive because the “Delete” button sat too close to “Archive”.

Error prevention provides crucial safety because it:

• protects people with motor impairments from the consequences of mis-clicks
• helps people with reading difficulties spot transposed numbers and letters
• gives people with cognitive disabilities extra time and orientation
• lets screen reader users listen to all their details again calmly before submitting
• takes the edge off stressful situations in which mistakes happen especially easily

And last but not least: it makes digital services more trustworthy for everyone – nobody wants to accidentally sink their savings into the wrong shares.

4. How to meet the criterion

The good news: you don’t have to implement all three approaches at once – one is enough. Here are proven strategies for each mechanism:

Reversible actions:

• Allow a cancellation window after orders (e.g. 24 hours)
• Offer “Undo” for data deletion
• Use a trash folder with a restore option instead of deleting immediately
• Clearly communicate how long and under what conditions cancellation is possible

Checked input:

• Validate critical fields as people type (email format, IBAN, phone number)
• Plausibility checks for unusual values (“Really buy 10,000 shares?”)
• Completeness check before submission
• Understandable error messages with concrete suggestions (see Error Identification and Error Suggestion)

Confirmation before submission:

• A summary page before final submission
• A prompt like “Do you really want to delete your account?” for critical actions
• An overview of all the data entered
• Editing options directly on the confirmation page

Technical implementation:

• Validate in the browser for fast feedback
• Validate on the server as well, not just as a fallback
• Use live regions such as role="alert" for important status messages
• Mark critical actions clearly in the design and keep them physically apart from harmless ones

Pro tip: combine several approaches for especially critical areas – e.g. error checking plus a confirmation page for financial transactions. If you extend at least one of the three mechanisms to all forms, you also meet Error Prevention (All).

5. Why this criterion matters for businesses

With Success Criterion 3.3.4, too, accessibility isn’t an end in itself – it brings tangible benefits for your business.

1. More satisfaction and trust

Nothing drives customers away faster than accidental purchases or lost data. Error prevention builds trust and reduces support requests. People who feel safe are more likely to buy – and to stay.

2. Fewer cancellations and refunds

Every wrong booking costs money: cancellation, refund, follow-up questions to support. A review page before submission or a plausibility check catches many of these errors before they happen.

3. More confidence at checkout

Uncertainty is a common reason for not completing a purchase. Confirmation pages and error checks give people the reassurance of being able to check everything one more time – especially for high-priced products.

And then there’s the legal side: since 28 June 2025, the European Accessibility Act (Directive (EU) 2019/882) has applied to many consumer-facing digital services, such as online shops and banking services – exactly where orders and payments happen. Germany implements it through the Barrierefreiheitsstärkungsgesetz (BFSG). The technical benchmark is the harmonised standard EN 301 549, which refers to WCAG 2.1 Level AA for web content – and 3.3.4 is part of that. Public sector bodies are covered separately by the Web Accessibility Directive (EU) 2016/2102. This section is general information, not legal advice.

6. The success criterion in the W3C’s words

Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)

For web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true:

• Reversible: Submissions are reversible.
• Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
• Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.

In short: for legally binding actions, payments, changing or deleting your own data and submitting tests, the submission must be reversible, checked or confirmed beforehand.