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
<input type="text" name="query" id="search_field" value class="form-control"> 125
<input type="text" name="query" id="query" value class="search-bar-text-field"> 125
<input type="text" name="user_name" id="user_name"> 55
<input autocomplete="off" type="text" name="contact[user_name]" id="contact_user_name"> 2
<div class="slick-track" style="opacity: 1; width: 5940px; transform: translate3d(0px, 0px, 0px);" role="listbox">...</div> 2
<select name="contact[contact_relation]" id="contact_contact_relation" required="required">...</select> 2
<div class="slick-track" style="opacity: 1; width: 12650px;" role="listbox">...</div> 1
<div class="slick-track" style="opacity: 1; width: 11385px;" role="listbox">...</div> 1
313 distinct issues were found in the sample of 125 web pages.
More results from TUI Group