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.



51.2% done

How close this website is to fixing this issue.

HTML Found on page Issues
<select name="local-market-dropdown" id="local-market-selector" class="form__select--market placeholder_active" onchange="eol.market_selector.selectDropdownOption(this)">...</select> 57
<input type="checkbox" class="ot-host-box" role="button" aria-expanded="false"> 55
<input type="checkbox" class="ot-ven-box" role="button" aria-expanded="false"> 55
<select name="top-up__number" class="form__select js-article-filter-category" data-filter-type="cat">...</select> 22
<input type="text" aria-invalid="false" placeholder="Search" value classes="[object Object]" class="MuiInputBase-input MuiOutlinedInput-input MuiInputBase-inputMarginDense MuiOutlinedInput-inputMarginDense"> 3
<button data-nav="0" tabindex="0" aria-selected="true" aria-controls="tns2-item0" style type="button" class="tns-nav-active"> 1
<button class="cookiePolicy-accept"> 1
194 distinct issues were found in the sample of 125 web pages.
More results from Vodafone Group