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
<ul hidden role="listbox" id="awesomplete_list_2"> 180
<ul hidden role="listbox" id="awesomplete_list_1"> 128
<ul hidden role="listbox"> 110
<ul hidden role="listbox" id="awesomplete_list_3"> 3
<select id="dropDwnID1" class="getid">...</select> 2
<input id="home-search" title="Search" class="search-btn-help" onclick="doTagElement(&quot;ehc_search&quot;);" value type="submit"> 1
<input type="checkbox" id="analytics_performance" name="Analytics and performance cookies"> 1
<input id="home-search" title="Search" class="search-btn-help" onclick="doTagElement(&quot;tpa_search&quot;);" value type="submit"> 1
<input id="home-search" title="Search" class="search-btn-help" onclick="doTagElement(&quot;mhc_search&quot;);" value type="submit"> 1
<input type="checkbox" id="functionality_customize" name="Functionality and customisation cookies"> 1
428 distinct issues were found in the sample of 125 web pages. Only the first 10 issues are shown here.
More results from National Employment Savings Trust Corporation