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 type="button" class="icon-link js-arrow"> 3375
<input type="text" maxlength="50" class="nav__search-input js-search-input" name="q" placeholder="Type here to search..."> 125
<button type="button" class="header-topbar__btn js-back"> 125
<button type="button" class="nav__link-search js-search"> 125
<input class="nav__input-search" type="search" name="q" id="search" placeholder="begin typing"> 125
<button class="nav__btn-search" type="submit">...</button> 125
<button type="button" class="header__location js-header-location"> 125
<button type="button" class="popup__btn js-popup-close"> 84
<button type="button" class="popup__btn js-people-close"> 21
<button type="button" class="popup__btn popup__btn--second js-people-close"> 21
4277 distinct issues were found in the sample of 125 web pages. Only the first 10 issues are shown here.
More results from CRH PLC