Synonyms: Error message, error messages, input instructions, context-specific help
See also:
Required field labeling,
,
description
,
help and support,
,
authentication
,
form
Error messages inform users about incorrect entries or incorrect operations. Error messages help with the correction of errors. Error messages can be displayed
- after submitting a form,
- when filling out a form, or
- when operating the software.
Input instructions help users to avoid errors. These can be displayed
- on the form,
- on the respective form field, or
- when operating the software.
No. | Property | Description | Classification | Reference |
---|
5 | Error message | If an error occurs, the incorrect form element must be identified and the cause of the error described in text form | Must | EN 301 549: 9.3.3.1, 11.3.3.1.1 |
---|
6 | Error message | The Submit button may not be disabled as long as the form is incomplete or filled out incorrectly. @ Note: This does not apply if there is an alternative method for displaying the error messages. -@ | Must | EN 301 549: 9.3.3.1, 11.3.3.1.1 |
---|
7 | Error message | The error message must be permanently displayed. | | |
---|
time limits.
| Must | EN 301 549:
9.2.2.1,
11.2.2.1 |
| @!8 | Error prevention | Form elements must have an expressivelabel so that their purpose is identifiable. | Must | EN 301 549:
9.2.4.6, 11.2.4.6, 9.3.3.2, 11.3.3.2 |
| @!9 | Error prevention | If the expected form field inputs cannot be derived clearly from the label of the form fields, additional input instructions must be provided (also see
Beschreibungen).
| Must | EN 301 549:
9.3.3.2, 11.3.3.2 |
| @!10 | Error prevention | If, when submitting a form,- a legal or financial commitment is made (e.g. when a contract is concluded),
- user-managed data in a database is changed or erased, or
- solutions are communicated in the context of an examination,
one of the following error prevention options must be offered:- The submission of the form can be undone.
- The data is checked by the application for its accuracy, and users can subsequently correct any errors.
- Users are asked to check their data for its accuracy and to correct incorrect inputs.
| Must | EN 301 549:
9.3.3.4, 11.3.3.4 |
| @!11 | Error prevention | When submitting information, one of the following error prevention options must be offered:- The submission of the form can be undone.
- The data is checked by the application for its accuracy and the users can subsequently correct any errors.
- The users are asked to check their data for its accuracy and are able to correct incorrect inputs.
| Should | WCAG 2.1: 3.3.6 (AAA) |
| @!12 | Error prevention | Acontext-sensitive Help option should be offered. | Should | WCAG 2.1: 3.3.5 (AAA) |
| @!13 | Error prevention | If it is necessary to enter information (such as a user name and password) when logging in, a variant must be available so that users do not have to remember this information.
| Should | WCAG 2.2 |
| @!14 | Error prevention | If it is necessary to input data in a process several times, then such data should be filled in automatically after the first input or be made available for selection.| Should | WCAG 2.2 |
| @!15 | Error correction | If the application is able to find suggestions for corrections to an incorrect input, these suggestions must be displayed.| Must | EN 301 549:
9.3.3.3, 11.3.3.3 |
| @!16 | Error correction | If an automatic error correction takes place, an error message in text form must be displayed. | Must | EN 301 549:
9.3.3.1, 11.3.3.1.1 |
No. | Property | Description | Classification | Reference |
---|
17 | Update | If the error message is displayed as a | | |
---|
status message , it must be marked so that the assistive technology is able to output it automatically.
| Must | EN 301 549: 9.4.3.1, 11.4.1.3.1 |
| @!18 | Error message | Error messages on the form field must be linked to the form field in such a way that they are communicated to the Accessibility API.Accessible Name oder der
Accessible Description . In this case, the Accessible Description should preferably be used, so that the Accessible Name is not excessively long.
| Must | EN 301 549:
9.1.3.1, 11.1.3.1 |
| @!19 | Error prevention | Input instructions which are visually assigned to a form field must be programmatically associated with the form field as input instructions.| Must | EN 301 549: 11.1.3.1 |
| @!20 | Error prevention | If the technology used is able to identify the input purpose of form fields, the purpose of the form fields must be marked for the data of the respective users (e.g. surname, date of birth, place of residence) according to https://www.w3.org/TR/WCAG21/#input-purposes. | Must | EN 301 549:
9.1.3.5, 11.1.3.5.1 |
| @!21 | Status | If it is only the case that a visual, non-textual error indicator is displayed on the incorrect field, then the error status must be communicated to theAccessibility API.
| Must | EN 301 549: 9.4.1.2, 11.4.1.2 |
- Date:
- 15.01.2024
- License:
- CC-BY-SA 4.0
- Version:
- 1.0
You are welcome to send feedback by email about our handout!