Marcelo Paiva

All criteriaPresent as slides

A woman in glasses leans on one hand at her laptop, the other hand resting on the keys, and gives a knowing sideways smile.Meant to show: A woman with a hand tremor, who wants to confirm before anything is final

Success criterion 3.3.4

Error Prevention (Legal, Financial, Data)

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, actions are reversible, checked for input errors, and confirmed before final submission.

  • Level AA
  • Principle 3: Understandable
  • Guideline 3.3: Input Assistance

In a user’s words

“Before we seal the deal, let's double-check. No regrets, right?”

Who this helps: All users, especially those with Cognitive Impairments

What each role can do

Product manager
Incorporate review, confirmation, and correction steps before finalizing sensitive transactions.
Designer
Design clear review pages that summarize user actions and decisions before final confirmation.
Developer
Implement mechanisms for reviewing, confirming, and correcting information prior to submission.
Tester
Test the process to ensure users can easily review, correct, and confirm actions without confusion.

Once it is fixed

“Knowing I can review and confirm my actions gives me peace of mind. No surprises!”

The quotes are written to illustrate the criterion. They are not testimonials from real people. For the official wording, find 3.3.4 in the W3C quick reference for WCAG 2.2 (opens in a new tab).

Or press the left arrow and the right arrow.

A success criterion

This is one page of a phrase book. It takes one success criterion and tells it from the side of the person it helps.

From top to bottom

  1. At the top, the site header: my name, which goes home, then links to Writing, Work, Signal, Tools and Resume, then Settings, where you choose the drawings, light or dark, and movement.
  2. Links back to all the criteria, and to present this one as slides.
  3. A drawing, the criterion’s number and name, what it requires in one sentence, and its level.
  4. In a user’s words: a quote from the person who meets the barrier.
  5. What each role can do: one task each for the product manager, the designer, the developer and the tester.
  6. Once it is fixed: the same person again.
  7. Share this with your team: post to LinkedIn, download the slides as a PDF, or copy a link.
  8. Some criteria then have a t-shirt to order.
  9. Links to the previous and next criterion. The left and right arrow keys go there too.
  10. At the bottom, the footer: a note on how this site is built, links to Illustrations, Pens, Concepts and Accessibility, this Describe this page button, then GitHub, LinkedIn and email.

What you can do here

Learn what this criterion asks, and what your part of the fix is.

Also here

The quotes are written to illustrate the criterion. They are not from real people.