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:

<label>
    Full name <input type="name">
</label>

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.



96% done

How close this website is to fixing this issue.

HTML Found on page Issues
<button role="button" class="owl-dot">...</button> 5
<input type="checkbox" value="1" name="privacy-policy"> 2
<select name="department_ward" class="no-search search-field">...</select> 2
<select name="service_location" class="no-search search-field">...</select> 2
<input type="text" name="keywords" class="search-field" placeholder="Type a keyword..." value> 2
<select name="service_type" class="no-search search-field">...</select> 2
<button role="button" class="owl-dot active">...</button> 1
<input type="text" name="keywords" class="search-field" placeholder="Type search keywords (e.g. 'Outpatients')..." value> 1
<input type="text" id="akID_136_value_pub" class="form-control ccm-input-date hasDatepicker"> 1
<select class="ui-datepicker-year" data-handler="selectYear" data-event="change">...</select> 1
21 distinct issues were found in the sample of 125 web pages. Only the first 10 issues are shown here.
More results from Hampshire Hospitals NHS Foundation Trust