WCAG 3.3.4 — Error Prevention — Legal/Financial Form Has No Confirm/Review

Who Is Affected

Users with cognitive disabilities, motor impairments that cause input errors, vision impairments who may misread form fields, users with attention disorders, and elderly users who may need extra time to review complex forms before submission.

What This Means

When your government website collects information that creates legal obligations or financial transactions (permits, licenses, tax payments, fines, contract submissions), users must have a way to prevent costly mistakes. WCAG requires one of these error prevention mechanisms:

• Reversible submissions — User can undo the transaction after submitting
• Data checking — System validates entries and allows corrections before final submission
• Confirmation step — User reviews all data and explicitly confirms before the transaction processes

Common violations include permit applications that immediately charge fees upon "Submit," business license renewals that can't be corrected after submission, or tax payment forms that process immediately without review.

Fix: CMS / Theme

Most form builders and government CMS platforms can be configured to add confirmation steps system-wide.

Joomla

1. Go to Components → RSForm Pro (or your form component)
2. Edit each form that handles legal/financial data
3. In Form Properties, enable "Confirmation Page"
4. Configure the confirmation to show all submitted data for review
5. Add explicit "Confirm and Submit" vs "Go Back and Edit" buttons
6. Test the complete flow before publishing

WordPress

1. Install a form plugin that supports multi-step forms (Gravity Forms, WPForms Pro, Formidable Forms)
2. For existing legal/financial forms, add a "Confirmation Page" step
3. Configure the confirmation step to display all form data in read-only format
4. Add clear "Submit Final Application" and "Edit My Responses" options
5. For payment forms, ensure the actual payment processing happens only after explicit confirmation

Fix: Content Editor

If you manage individual forms through your content management system:

1. Identify affected forms — Any form that creates legal obligations, processes payments, or submits official applications
2. Add a review step — Insert a confirmation page before final submission that shows all user entries
3. Include clear options — Provide both "Confirm and Submit" and "Go Back to Edit" buttons
4. Add explanatory text — Tell users this is their final chance to review before the submission becomes official
5. Test the flow — Complete a test submission to ensure the confirmation step works properly

For forms that can't easily add confirmation steps, consider these alternatives:

• Allow users to save drafts and return later
• Send email confirmations with correction instructions
• Provide clear contact information for post-submission corrections

Standard Reference

WCAG 2.1 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: submissions are reversible, data is checked and the user can correct it, or a confirmation mechanism is available.

• W3C Understanding SC 3.3.4
• WCAG Technique G98 — Confirmation before submission
• WCAG Technique G99 — Recovery mechanism
• WCAG Technique G155 — Providing checkboxes in addition to submit button
• WCAG Technique G164 — Time limit with option to extend
• WCAG Technique G168 — Confirmation step
• WCAG Failure F36 — Submit button without confirmation
• WCAG Failure F82 — Irreversible legal/financial transaction