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.

0% done

How close this website is to fixing this issue.

HTML Found on page Issues
<input class="with-btn" type="text" id="searchbar-input" placeholder="Search Cranfield"> 98
<input name="Keyword" type="text" placeholder="Enter search term" value onchange="searchFilter.checkTerm(this.value)"> 88
<input class="with-btn" type="text" id="searchbar-input" placeholder="Search School of Management"> 27
<input type="text" placeholder="End date" class="datepicker hasDatepicker" name="EndDate" id="txtEndDate"> 7
<input type="text" placeholder="Start date" class="datepicker hasDatepicker" name="StartDate" id="txtStartDate"> 7
<button class="iframe__button js-modal">...</button> 1
<select class="select" id="cfYear" name="Year">...</select> 1
<select class="select" id="cfLevel" name="Level">...</select> 1
<input class="with-btn" name="query" type="search" id="searchbar-input" placeholder="Search Cranfield"> 1
<select class="select theme-filter">...</select> 1
235 distinct issues were found in the sample of 125 web pages. Only the first 10 issues are shown here.
More results from Cranfield University