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.



1.6% done

How close this website is to fixing this issue.

HTML Found on page Issues
<select id="tinynav1" class="tinynav tinynav1">...</select> 123
<button class="jw-nextup-close"> 15
<select data-native-menu="false" id="searchForm_type" name="type">...</select> 1
<input class="span5 search-query autocomplete searcher:Solr" id="searchForm_lookfor" name="lookfor" placeholder="Search SOAS Library" required value type="text"> 1
<input id="term" value type="jssearch"> 1
141 distinct issues were found in the sample of 125 web pages.
More results from SOAS University of London