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
<button class="sidebar__close-button--sign"> 125
<input class="olapic-report__input olapic-report-email" name="olapic-report-email" type="email" placeholder="Enter Email Address" required> 102
<input class="olapic-report__input olapic-report-reason" name="olapic-report-reason" type="text" placeholder="reason" required> 102
<div class="olapic-lightbox-share-button cat-link" role="button" tabindex="0"> 102
<button type="submit" class="out-of-stock-modal__top-exit-button" role="button" tabindex="0" aria-pressed="false">...</button> 100
<div id="next-olapic" role="button" data-label="Button click"> 100
<input type="text" name="contact" placeholder="Enter Email Address" class="out-of-stock-modal__form-input" value> 100
<div id="prev-olapic" role="button" data-label="Button click"> 100
831 distinct issues were found in the sample of 125 web pages.
More results from All Saints