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:

    Full name <input type="name">

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.

88% done

How close this website is to fixing this issue.

HTML Found on page Issues
<span class="select2-selection__rendered" id="select2-subject-level-links-container" role="textbox" aria-readonly="true">...</span> 7
<input id="search-queryinput" type="text" value name="query" placeholder="Search"> 5
<input class="ual-checkbox people" type="checkbox" value="people"> 1
<input class="ual-checkbox" type="checkbox" value="courses"> 1
<input class="ual-checkbox research" type="checkbox" value="research"> 1
<select data-function="sorting" selected="relevance">...</select> 1
<input class="ual-checkbox" type="checkbox" value="people"> 1
<input class="ual-checkbox events" type="checkbox" value="events" checked> 1
<input class="ual-checkbox" type="checkbox" value="website"> 1
<input class="ual-checkbox" type="checkbox" value="stories" checked> 1
25 distinct issues were found in the sample of 125 web pages. Only the first 10 issues are shown here.
More results from University of the Arts London