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 class="sub-nav-dropdown-icon">...</button> 2000
<button id="mobile_menu_toggle">...</button> 125
<input type="submit" class="submit-icon"> 125
<input id="search-input-mobile" type="text" name="search" placeholder="Enter search term"> 125
<input id="search-input" type="text" name="search"> 125
<input type="text" name="searchTerm" placeholder="Search"> 56
<div class="slick-track" style="opacity: 1; width: 1275px;" role="listbox">...</div> 10
<button class="m-banner__button left-c slick-arrow slick-hidden" aria-disabled="true" tabindex="0"> 9
<button class="m-banner__button right-c slick-arrow slick-hidden" aria-disabled="true" tabindex="0"> 9
<button class="slide-prev-button slide-nav slick-arrow" style="display: block;">...</button> 8
2624 distinct issues were found in the sample of 125 web pages. Only the first 10 issues are shown here.
More results from Notting Hill Genesis