# Error Prevention

Error prevention designs risky choices, inputs, defaults, and constraints so common mistakes are avoided before users need an error message.

- Type: principle
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/error-prevention/>)

## What it means

Error prevention removes or reduces conditions that produce mistakes. It combines clear language, sensible defaults, constraints, previews, validation, confirmation for consequential actions, and system rules that preserve valid work. The aim is to make the safer path easier, not to blame people more efficiently.

## Why it matters

Preventing an error is usually cheaper than explaining and repairing it. It protects data, reduces support demand, lowers anxiety, and matters most for payment, deletion, permission changes, and legal submission. Accessible prevention also avoids repeated correction for people using assistive technology.

## When to use it

Use it wherever input is structured, actions are destructive, choices have dependencies, or failure has financial, safety, privacy, or data-loss consequences. Apply safeguards in proportion to impact while keeping frequent, low-risk actions fast and reversible.

## How it works

1. Study real failures and distinguish slips, misunderstandings, invalid data, and system faults.
2. Remove impossible choices, constrain formats, preserve valid data, and supply safe defaults.
3. Give requirements before input; validate when it helps instead of interrupting every keystroke.
4. For consequential actions, show a specific preview or confirmation and offer reversal when possible.
5. Measure prevented failures alongside abandonment, false positives, accessibility, and completion time.

## A practical example

Before publishing a campaign, the product checks recipients, links, and scheduling conflicts. A review shows audience size, sender, time zone, and consequences. The action says “Schedule 12,430 emails,” and the system permits cancellation during a short grace period.

## Where it breaks

Every safeguard adds friction and can create mistakes. Overvalidation rejects legitimate input, confirmation dialogs become habitual, and disabled controls conceal requirements. Prevention cannot cover every case, so products still need recovery, resilient storage, monitoring, and support.

## Common mistakes

- Using generic confirmations until users stop reading
- Disabling submit without explaining what remains unmet
- Discarding valid input when one field fails validation

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/error-prevention/#visualization-error-prevention>)

## Sources

1. [Understanding SC 3.3.4: Error Prevention](<https://www.w3.org/WAI/WCAG22/Understanding/error-prevention-legal-financial-data.html>) — W3C Web Accessibility Initiative · Accessibility guidance
2. [10 Usability Heuristics for User Interface Design](<https://www.nngroup.com/articles/ten-usability-heuristics/>) — Nielsen Norman Group · Professional guideline

## Related topics

- [Error Recovery](<https://wiki.soroush.uk/topic/error-recovery/>)
- [Progressive Disclosure](<https://wiki.soroush.uk/topic/progressive-disclosure/>)
- [Cognitive Load](<https://wiki.soroush.uk/topic/cognitive-load/>)
