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.
More helpUsually 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.8% done
How close this website is to fixing this issue.
HTML | Found on page | Issues |
---|---|---|
<input class="hex-form flatpickr flatpickr-input form-control input" placeholder="common_now" tabindex="0" type="text" readonly="readonly">
|
126 | |
<input data-v-47faed28 id="pika-datepicker-departure" type="text">
|
2 | |
<input data-v-71cc98be class="hex-form">
|
2 | |
<input data-v-47faed28 id="pika-datepicker-return" type="text">
|
2 | |
<input name="password" type="password" maxlength="100" autocomplete="new-password" placeholder="Password" aria-describedby="password" data-vv-as="password" class="hex-form" aria-required="true" aria-invalid="false">
|
1 | |
<button data-v-4c864561 type="button" name="button" disabled="disabled" class="single-flight">
|
1 | |
<input name="confirmPassword" type="password" maxlength="100" autocomplete="new-password" placeholder="Confirm Password" aria-describedby="confirmPassword" data-vv-as="Confirm password" class="hex-form" aria-required="true" aria-invalid="false">
|
1 |