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.8% done

How close this website is to fixing this issue.

HTML Found on page Issues
<input type="checkbox" class="ot-host-box" role="button" aria-expanded="false"> 67
<input type="checkbox" class="ot-ven-box" role="button" aria-expanded="false"> 67
<button class="ot-host-box" aria-expanded="false"> 57
<button class="fullscreen" type="button">...</button> 11
<button class="play" type="button">...</button> 11
<button class="mute" type="button">...</button> 11
<button type="button">...</button> 3
<input class="form_field form_field_radio" type="radio" id="radioid_3_Hungarian (HU)_mobile" name="language" value="/content/whnlhub/hungarian/we-blog/solarcloud.html"> 1
<input class="form_field form_field_radio" type="radio" id="radioid_2_German (eon.com)_mobile" name="language" value="/content/whnlhub/de/we-blog.html"> 1
<input class="form_field form_field_radio" type="radio" id="radioid_3_English - UK_mobile" name="language" value="/content/whnlhub/en1/we-blog.html"> 1
247 distinct issues were found in the sample of 125 web pages. Only the first 10 issues are shown here.
More results from E.ON