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.



0% done

How close this website is to fixing this issue.

HTML Found on page Issues
<input type="checkbox" class="vendor-box" role="button" aria-expanded="false"> 124
<input type="checkbox" class="host-box" role="button" aria-expanded="false"> 124
<button aria-labelledby="labelSearchButon" class="search-submit">...</button> 122
<button class="search-submit" type="submit">...</button> 29
<input id="searchQuery" type="text" name="searchQuery" placeholder="Search" class="search-text" value data-url="true"> 25
<select name="business-area" id="business-area" class="js-business-area"> </select> 7
<input type="radio" name="domain" value="otherEnquiries"> 7
<input type="radio" name="domain"> 7
<input type="radio" name="domain" value="Services"> 6
<input type="radio" name="domain" value="Cyber defence"> 6
514 distinct issues were found in the sample of 125 web pages. Only the first 10 issues are shown here.
More results from BAE Systems