Writing & StyleStyle guide

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.

Quick answer

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

Core IssueWCAG 2.2 says important legal, financial, data-changing, or test submissions need a way to be reversed, checked, or reviewed and confirmed before finalization.
Registerweb accessibility and interface content

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.

Purpose

Confirmation wording helps users recognize consequential actions before they become final.

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.

  1. 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.

Explore the topic