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.

Usually 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="query" class="header__search__input ui-autocomplete-input" type="text" name="query" value placeholder="Search website…" autocomplete="off"> 125
<select name="level">...</select> 3
<span role="checkbox" style="vertical-align: middle;">...</span> 2
<input type="text" accesskey="q" name="query" class="search-form__query" id="search-query" placeholder="Enter last or first name, job title, room or department" value> 1
<input id="map-search" class="controls ui-autocomplete-input" type="text" placeholder="Search building" autocomplete="off"> 1
<input type="text" id="tfa_24" name="tfa_24" value readonly title class="formula=ENQUIRY readonly" aria-invalid="false" aria-describedby> 1
<select title="Select entry year">...</select> 1
134 distinct issues were found in the sample of 125 web pages.
More results from University of London