Writing Error-Prevention Confirmation Text
Writing Error-Prevention Confirmation Text turns the WCAG review-and-confirm requirement into a focused content pattern without claiming that wording alone satisfies the full success criterion.
Before an important submission becomes final, use clear review-and-confirmation wording that tells users what will happen and makes correction possible in the workflow.
Key details
Important caveats
Scope Boundary
This page covers confirmation and review wording; whether a workflow is reversible or technically validates input is an implementation decision.
Further guidance
Content
Tell users what they are about to finalize and make the opportunity to review, confirm, or correct the information explicit.
Practical Application
Before a consequential action becomes final, name the action, summarize what will be submitted or changed, and make the available review, edit, or confirm choice explicit.
Purpose
Confirmation wording helps users recognize consequential actions before they become final.
Reader Check
Does the confirmation tell users exactly what becomes final and how to correct information before committing?
Worked Example
Use “Review your transfer details. You are sending ₹5,000 to Arun Kumar. Choose Edit to change the details or Confirm transfer to continue” rather than a vague “Are you sure?”
Sources and evidence
Sources are shown with the role they play in this guide. Historical or style-sensitive claims are kept within the evidence boundary described above.
- Understanding SC 3.3.4: Error Prevention (Legal, Financial, Data) — WCAG 2.2 (opens in a new tab)World Wide Web Consortium (W3C) · WCAG 2.2 guidance on reviewing, confirming and correcting important submissions before finalization.