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.

93.6% done

How close this website is to fixing this issue.

HTML Found on page Issues
<input placeholder="Enter email address" name="e" type="email" required id="prefix-emailInput" title="Enter email address"> 5
<select name="mStartDate" id="mStartDate">...</select> 1
<select name="eventfilter" id="eventfilter">...</select> 1
<select name="dStartDate" id="dStartDate">...</select> 1
<select onchange="changeCategory(this.value);">...</select> 1
<input type="text" value id="skdfFNC_SInput" onkeyup="skdfFNC_docSearch();"> 1
<select name="dEndDate" id="dEndDate">...</select> 1
<select name="mEndDate" id="mEndDate">...</select> 1
<input id="searchChoicesQuery" name="q" type="text" value> 1
<input type="text" name="CURDATE_YEAR" id="CURDATE_YEAR" value="2018" size="6"> 1
15 distinct issues were found in the sample of 125 web pages. Only the first 10 issues are shown here.
More results from Isle of Wight NHS Trust