What does this mean?
People using screen readers are not able to see the layout of a form. To make forms accessible, they must define explicit text labels for each form control.
More helpUsually the best solution is to use a <label>
element. The label may be linked to
by the form control:
<label for="name">Full name</label>
<input type="name" id="name">
or the <label>
can be wrapped around the form control:
<label>
Full name <input type="name">
</label>
Buttons are different, as their labels are specified by the code for the button, e.g.
<input type="submit" value="Send message">
<button>Send message</button>
Alternatively ARIA attributes, such as aria-label
may be used, but this information
will not be conveyed to visual users. For more information, see W3C's guide to labeling controls.
Hidden input fields (<input type="hidden">
) do not require labels.
Note that the placeholder
attribute
should not be used as an alternative to a label.
0% done
How close this website is to fixing this issue.
HTML | Found on page | Issues |
---|---|---|
<input id="findInputHeader" type="text" class="form-control" autofocus>
|
121 | |
<select class="gfc-dropdown funds-search-capabilities">...</select>
|
15 | |
<select class="gfc-dropdown funds-search-assetclass">...</select>
|
15 | |
<button class="funds-search-closeicon hide">
|
15 | |
<input type="text" id="funds-search-input" class="gfc-input funds-search-input" placeholder="Type name or ISIN" value>
|
7 | |
<input type="text" id="funds-search-input" class="gfc-input funds-search-input" placeholder="Geben Sie name oder ISIN ein" value>
|
4 | |
<a class="down control" href="#carousel-reviews" role="button" data-slide="next">...</a>
|
2 | |
<input id="r4" name="category" type="radio" value="v4" data-path>
|
2 | |
<input type="text" id="funds-search-input" class="gfc-input funds-search-input" placeholder=" Typ naam of ISIN" value>
|
2 | |
<select id="region-select" class="locale-header form-control">...</select>
|
2 |