Support through the system
People with disabilities tend to trigger false actions more often than users without disabilities. It is therefore helpful to plan the system in such a way that mistakes can be avoided in the initial phase.
Error prevention
Help users recognize, diagnose, and recover from errors
Table of contents
- What is the problem if the system does not provide support?
- Error avoidance through restrictions
- Error avoidance through support
- Error avoidance through repetition
- Not all options are always available
What is the problem if the system does not provide support?
When users are disabled, they can often inadvertently trigger wrong actions. If this is the case, this should not be a problem for the user. The system should support the user and prevent errors from the beginning.
A system without support can be a problem for the following users:
- Inexperienced or older users feel insecure
- People with physical impairments feel insecure if they accidentally click something wrong
Error avoidance through restrictions
One possible way to avoid errors is to limit the user’s options. By limiting the input possibilities, the error rate of a system is reduced. For users with limitations, it is more clear what is required of them.
In this example ottonova with a date, the format of the input is already predefined and only the input of numbers is allowed.
Error avoidance through support
Errors can occur when entering information, not only for disabled users. This should not be a problem for the user. As a good example the live search should be considered. Suggestions are often made during the input. These suggestions also correct input errors. This avoids empty search results.
The automatic live search completion reduces the chance of errors during input. google
Error avoidance through repetition
Repeated requests for information force the user to check the information entered. In addition, by comparing the information, the system can detect errors and warn the user. A good example of this is setting a password. The user is forced to repeat this in order to avoid making errors. For actions with consequences, such as deleting a file, the system should always ask the user first whether this action is actually desired.
The system asks the user if they really want to delete the file.
Not all options are always available
Certain actions are dependent on other factors. For example, as a private user I need different input fields like an organization. Therefore, it makes sense not to display them for both users. It is better to separate both input variants. For example, with a radio button. This way, the user is not overwhelmed with too much information. Another example are inactive elements that only become active once everything has been entered. In this way, the user knows that he or she can now proceed to the next step. See processes for more information on processes and user guidance.
The system determines when it is possible to switch to the next step.
Links
W3C – Input Assistance
W3C – Error Identification
W3C – Error Prevention