7 guidance statements support this accessibility characteristic:
- Error identification - For systems with possible errors, people may need errors to be identified sensorily and programmatically.
- Error prevention - For systems with possible errors, people may need submissions to be checked, confirmable or reversible
- Error suggestion - For systems with detectable errors, people may need error messages to suggest corrections or state that the system is at fault and the user is unable to fix the error.
- Manage individualization functions - For systems with assistive technology built into the platform, people may need a way to perform, undo, and redo individualization actions.
- Redundant Entry - For systems that require data input, people may need to avoid entering data more than once.
- Safe without reliance on alerts - For systems that present alerts, people may need to use the system safely even if I miss an alert or hazard warning.
- Voice input errors - For systems with dictation and voice commands, people may need to minimize mistakes that occur because of mistaken speech (e.g. operations are tied to a single letter shortcut)