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 type="text" name="keywords" value placeholder="Search" class="form-control keywords">
|
147 | |
<input type="text" name="keywords">
|
125 | |
<button class="ot-host-box" aria-expanded="false">
|
85 | |
<select name="tag" class data-dropdown-class="search-filter">...</select>
|
24 | |
<select name="per_page" class="pagination-select" data-dropdown-class="pagination-dropdown" onchange="document.location.href=this.options[this.selectedIndex].value;">...</select>
|
24 | |
<select name="date" class data-dropdown-class="search-filter">...</select>
|
24 | |
<select name="region" class data-dropdown-class="search-filter">...</select>
|
23 | |
<button class="ot-sdk-show-settings">
|
21 | |
<input type="text" name="email" class="form-control" value>
|
6 | |
<input type="text" name="catcher">
|
6 |