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.

94.4% done

How close this website is to fixing this issue.

HTML Found on page Issues
<div class="fotorama__nav__frame fotorama__nav__frame--dot" tabindex="0" role="button">...</div> 20
<div class="fotorama__nav__frame fotorama__nav__frame--dot fotorama__active" tabindex="0" role="button">...</div> 3
<input type="button" href="#down" class="down" title="move down"> 1
<div class="fotorama__arr fotorama__arr--prev" tabindex="0" role="button"> 1
<input type="TEXT" name="IISearchString" size="25" value> 1
<input onkeyup="chkSrch()" maxlength="30" size="30" name="search_name" id="Text1"> 1
<input type="button" href="#up" class="up" title="Move up"> 1
<input type="button" class="fotorama-pause" title="Pause" id="start"> 1
<div class="fotorama__arr fotorama__arr--next" tabindex="0" role="button"> 1
<input type="button" href="#right" class="right" title="Move right"> 1
32 distinct issues were found in the sample of 125 web pages. Only the first 10 issues are shown here.
More results from Cumbria County Council