This translation has not been editorially reviewed yet. The German version is authoritative. Deutsche Fassung
Accessibility
How do I formulate a good error message?
A good error message says in one sentence what does not fit and what the visitor should do now, with the words that are already on the field. "Invalid date" becomes "The date of issue must be in the past". The GOV.UK Design System of the British government has written down rules that can be easily transferred to German. The examples here are our transmission.
Empty field: Invitation. Wrong input: description.
GOV.UK separates two cases. If a field is empty, the message says what to do: "Enter your first name." If the input is incorrect or too long, it describes the condition: "The name must have a maximum of 35 characters." You should avoid sentences that fit each field, such as "An error occurred" or "This field is required". They are true, and the visitor still does not know afterwards what to do. For each error case of a field, there is therefore a separate message: one for empty, one for the wrong format, one for too long.
The message takes over the words of the field
If the field asks "How many hours do you work per week?", the message is "Indicate how many hours do you work per week". The visitor recognizes the question again, and who gets read the page understands the sentence even without the field next to it. If the field is called "date of birth", the message does not write "date". GOV.UK gives a simple sample: Read the message aloud. If it sounds like a sentence you would say to a customer at the counter, it fits.
These words don’t help anyone
GOV.UK deletes "valid" and "invalid" because they add nothing. Similarly, it avoids "you have forgotten", "forbidden" and "inadmissible", for the apology that does not solve the problem, and for the casual "hops". Technical specifications such as "Error 0x0000000643" do not tell the visitor anything. Also "please" deletes GOV.UK, because it sounds like there is a choice. In German, "please" is a question of tone; It is important that the instruction is thereafter and names the field.
The message is in the field and in a list about it
GOV.UK displays each message directly on the field, after caption and reference text, and repeats it word for word in a summary at the top of the page, even if there is only one error. Each entry links to its field. In its form tutorial, the W3C also recommends the list above the form and links the message in the field in the code to aria-describedby so that readers announce it there. The inputs remain, even the right ones. Anyone who has to re-type everything easily makes new mistakes.
When logging in and password, the message remains general
The WCAG criterion 3.3.3 excludes proposals if they would endanger safety. A registration form therefore does not specify the correct password or whether an account exists. Here the general message is the right choice. For all other fields: the more accurate, the better.
Examples
Empty mandatory field
Dieses Feld ist erforderlich.Geben Sie Ihren Vornamen ein.Date outside the allowed area
Ungültiges Datum.Das Ausstellungsdatum muss in der Vergangenheit liegen.Value from a fixed list
Ungültiger Wert.Meinten Sie Dezember?The W3C calls this query for a monthly field in which someone typed 12.
- Trigger each message of your form once and write the texts into a list. So you see which are only the standard text of the software.
- Read each message aloud and cross out what you wouldn’t say to a customer.
- Provide the Agency with one message per field per failure: blank, incorrect format, too long.




