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
<button type="button" class="ot-floating-button__close">...</button> 125
<input id="vendor-search-handler" type="text" name="vendor-search-handler"> 125
<button class="ot-host-box" aria-expanded="false"> 125
<button type="submit" class="c-community-search-box__btn">...</button> 2
<select class="c-community-search-box__search-dropdown">...</select> 2
<button class="c-incidents-slider__control">...</button> 1
<button class=" c-incidents-slider__control c-incidents-slider__control--expand ">...</button> 1
<input placeholder="Find a project" type="search" id="community-search-box" class="c-community-search-box__input"> 1
<button class="c-incidents-slider__control c-incidents-slider__control--disabled">...</button> 1
<input aria-describedby="postcodeError" type="text" name="postcode" id="postcode" class="c-form-input__control"> 1
387 distinct issues were found in the sample of 125 web pages. Only the first 10 issues are shown here.
More results from Wessex Water