Rule
Payment form safeguards
A form that takes a payment must be reversible, checked or confirmed before submission.
- Rule
financial-form-confirmation- WCAG 2.2
- 3.3.4 Error Prevention (Legal, Financial, Data) (opens in a new tab) (Level AA)
- Severity
- Serious
What it checks
The rule looks at every <form> and picks out payment forms by their markup: a field whose autocomplete names card details, such as cc-number, cc-exp or cc-csc, or names transaction-amount. Other forms pass. Forms that make a legal commitment or delete stored data have no such signature, so the rule cannot pick them out.
When a person decides
A payment form is always sent for review and never failed. WCAG 3.3.4 is met when the submission can be reversed, when the entries are checked and the user can correct them, or when a step to review and confirm comes before the final submit. Those safeguards often sit on a later page or in the terms of sale, so a person needs to check which one the checkout offers.
Example
Sent to review
<form action="/pay">
<label for="card">Card number</label>
<input id="card" autocomplete="cc-number" inputmode="numeric">
<button>Pay now</button>
</form>
Passes
<form action="/search">
<label for="q">Search the shop</label>
<input id="q" type="search" name="q">
<button>Search</button>
</form>
The engine is tested against both examples.
How to fix it
Add a page that shows the order for review before the final submit, check the entries and let the user correct them, or state a period in which the order can be changed or cancelled.
Check your own pages
This rule runs in every pour audit: the browser extension, the bookmarklet, the command line and the editor. Get pour, free.