This translation has not been editorially reviewed yet. The German version is authoritative. Deutsche Fassung
Accessibility
Mark mandatory field: is one asterisk enough?
An asterisk is sufficient if it is in the label of the field and is declared at the beginning of the form, for example with "fields with * are mandatory fields". This is how the W3C describes it in its technique H90: the meaning of a symbol is before its first use. The word written out comes without explanation: "Last name (mandatory field)". In addition, the field in the code needs the attribute required so that the browser also knows.
So the asterisk is right
The asterisk belongs in the element label; so it is connected to the field in the code. If it stands next to it in its own paragraph, this connection is missing. The explanation is above the first field. The W3C also enlarges the asterisk in its example by style sheet, because it is difficult for people with visual impairment to recognize. The Nielsen Norman Group, a research group on usability, cites red as a common color on the web and advises against pale gray. Color remains the complement: To a blind visitor, a red-colored field without signs or words says nothing.
The experts disagree on the asterisk
The W3C shows both ways as examples: the word in the label and the declared starlet. It advises against the abbreviation "req." because it is confused according to hints. For the German this means: "mandatory field" to tender. The Nielsen Norman Group prefers the asterisk because it takes little space and is familiar to most people. The British GOV.UK Design System prescribes the opposite: mandatory fields never get an asterisk there, and voluntary fields are called "(optional)". Choose a spelling and stick to it throughout the website, because whoever has learned it once relies on it.
If almost everything is mandatory, cross out first
Many forms consist almost only of mandatory fields. GOV.UK advises to ask only what is really needed: every field painted no longer has to be marked and no one has to fill in. What remains, still mark individually. The Nielsen Norman Group explains this: Notes at the beginning of the form are often overlooked or forgotten, and if you only mark the voluntary fields, the visitor must open the mandatory fields himself. Completion is easiest if both species are marked.
The required attribute tells the program
With the required attribute, the browser does not send an empty field, and utilities such as read-out programs should report the field as a mandatory field. It shows nothing on the screen. The developer documentation MDN therefore requires a visible indication close to the field. The aria-required attribute only states that the field is mandatory and does not prevent anyone from submitting. Visible mark and attribute therefore belong together: one for the eyes, the other for the program.
For selection groups, the label belongs to the group
For selection buttons and tick boxes, not the individual option is mandatory, but the answer to the question. The W3C therefore places the mark in the element placing the heading of the group. GOV.UK does the same with "(optional)".
Examples
Stars without explanation and without connection
<p>Nachname *</p>
<input name="nachname"><p>Felder mit * sind Pflichtfelder.</p>
<label for="nachname">Nachname <span class="pflicht">*</span></label>
<input id="nachname" name="nachname" required>The asterisk is in the label, its meaning is in front of the first field, and required tells it to the browser.
- Open your most important form and see if it says what the asterisk means above the first field.
- Determine which spelling applies throughout the website and give your agency’s sentence.
- Delete each field that you do not need to specify for editing.




