A form can accept every field and still carry the wrong information. An address may be valid but belong to an old office; a request may describe the wrong service. A review step gives people a chance to inspect the meaning of their answers, not merely their format. Its value depends on what they can see and change before the final action.
1. Match the pause to the consequence
Do not add a separate confirmation screen to every newsletter form. First ask what a mistaken submission could do and whether it can genuinely be undone. WCAG 2.2 criterion 3.3.4 concerns legal commitments, financial transactions, relevant changes or deletion of user-controlled stored data, and test responses. Within that scope, it offers alternatives: reversible submissions, checking with a correction opportunity, or review, confirmation and correction before completion. It does not prescribe the same review page for all forms.
For a substantial project enquiry, review can be a useful editorial choice even when this criterion is not the reason. Keep the effort proportionate; a summary should earn its place rather than become another obstacle.
2. Summarize what the person is deciding
Group answers under familiar headings such as contact details, requested work and attachments. Show readable values rather than internal codes. Preserve meaningful line breaks in the message, and distinguish an unanswered optional field from a deliberate choice of “none”. If money or a commitment is involved, explain its relevant conditions before the final control, not only in a later receipt.
A summary cannot repair ambiguous questions. Start with fields with a clear purpose, then check that the review uses the same language. Do not repeat sensitive secrets merely to make the summary look complete.
3. Make correction a short, safe round trip
Put a descriptive edit link beside each group: “Edit contact details” is clearer than several identical “Change” links. Return the person to the relevant fields without clearing the rest. After editing, rebuild the summary from the current answers so that an old value cannot survive on the review screen.
Keep correction separate from submission. Keyboard users should reach the edit controls and understand where focus goes after a transition. If a revised answer fails validation, explain the problem near the field and preserve valid input; our guide to helpful form errors covers that earlier part of the journey.
4. Name the final action honestly
“Continue” should not secretly send a binding request. Choose wording that describes the actual action, such as “Send enquiry”, and make the difference between editing and sending visible. In a multi-step flow, indicate the current stage and repeat essential instructions. WAI recommends logical stages and clear progress, not splitting a short form merely to create a progress bar.
After activation, distinguish sending from confirmed success. If the result is uncertain, do not label it successful or invite repeated submissions without explaining the risk of duplication.
5. Test the correction journey, not just the happy path
Try the flow with a long message, missing optional details and a changed attachment. Read it on a narrow screen, enlarge the text and complete it using a keyboard. The review should stay understandable without relying on colour or a tiny pencil icon.
- Can people identify exactly what will be sent?
- Can each important answer be corrected without starting again?
- Does the summary show the corrected values?
- Is the final action distinct from navigation?
- Does the result describe what actually happened?
A useful review is not a decorative “Are you sure?”. It is a working opportunity to notice a mistake and resolve it before it matters.