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 type="button" class="m-site_navigation__listtoggle js-toggle-dropdown">...</button> 154
<input class="selectric-input" tabindex="0"> 5
<select id="wc-audiooutputselector" class="wc-devicedropdown"> 4
<input id="wc-name" type="text" class="wc-name-input" maxlength="64" placeholder="Your Name"> 4
<select id="wc-audioinputselector" class="wc-devicedropdown"> </select> 4
<select id="wc-videoselector" class="wc-devicedropdown"> </select> 4
<input id="wc-email" type="email" class="wc-email-input wc-show" maxlength="128" placeholder="Email Address"> 4
<input type="radio" name="facingmode" id="wc-environmentfacing" value="Environment"> 4
<input type="radio" name="facingmode" id="wc-userfacing" value="User" checked> 4
<textarea class="wc-message" maxlength="1024"></textarea> 4
192 distinct issues were found in the sample of 77 web pages. Only the first 10 issues are shown here.
More results from Richmond Housing Partnership Limited