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.

75.2% done

How close this website is to fixing this issue.

HTML Found on page Issues
<input class="selectric-input" tabindex="0"> 24
<input type="text" name="756b283695fb40dd90c4b8074afcc91d"> 13
<input class="m-form__input js-location_search_input m-property_search__filter_input pac-target-input" id="Location_LocationName" name="Location.LocationName" placeholder="Search an area..." type="text" value autocomplete="off"> 8
<input class="m-form__icon-field-input" data-val="true" data-val-date="The field Articles to: must be a date." id="datepicker-to" name="Filter.ToDate" type="text" value> 7
<input class="m-form__icon-field-input" data-val="true" data-val-date="The field Articles from: must be a date." id="datepicker-from" name="Filter.FromDate" type="text" value> 7
<input type="text" name="79c5bc127a9740fbb6fb599044d63a73"> 1
<input type="text" name="b4b3a8e7ed0f4c9c9ecff2ddfbaf9dbc"> 1
<input type="text" name="a29212b3c1d346deb18316d7f4ebbc13"> 1
62 distinct issues were found in the sample of 125 web pages.
More results from Orwell Housing Association Limited