Skip to main content

Back to Guidelines

What is Error Prevention (Legal, Financial, Data)?

For important submissions, provide confirmation, review, or reversibility.

Users can review important details before committing the action.
High-risk tasks need a confirm or cancel step.
Undo or reversal options protect people from costly mistakes.

Good vs Bad Examples

Use the tabs to compare the accessible pattern with the example to avoid.

Good Example 1 – Confirmation Before Submission

Transfer flow with a review step and a confirm button before the final submission.

html

<button type="button">Review details</button>
<button type="button">Confirm & Send</button>

Why this is correct (developer logic):

Users can review details before the final action.
The confirm step reduces costly mistakes.
The process is safe for legal and financial tasks.

Good Example 2 – Reversibility Provided

Delete record flow that includes cancel and undo options so the action can be reversed.

html

<button type="button">Delete</button>
<button type="button">Cancel</button>
<p>Undo is available in the activity log for 30 days.</p>

Why this is correct (developer logic):

Users can cancel or undo the action.
The workflow protects important data.
Reversibility improves confidence and control.

Implementation Checklist

Progress0 / 5 completed (0%)

Keep the interaction predictable and easy to understand.
Test with keyboard and screen reader navigation.
Make sure focus is visible and easy to track.
Avoid hidden, unexpected, or unnecessary repetition.
Confirm the example meets the intended accessibility requirement.

Knowledge Check

Answer Yes or No to test your understanding of error prevention (legal, financial, data).

Score: 0 / 3 · Answered: 0 / 3

Does the good example demonstrate error prevention (legal, financial, data) correctly?

Is the bad example acceptable for error prevention (legal, financial, data)?

Should this pattern be checked with keyboard and screen reader testing?