What does this mean?
To comply with WCAG 2.1, fields must identify what their purpose is programmatically. If done correctly, this allows browsers to help users fill in forms with known information, such as their name and email address.
More helpThis is accomplished via the autocomplete attribute, which should be set to a
supported value wherever
appropriate, e.g.
<label for="name">First Name</label>
<input id="name" type="text" autocomplete="given-name">For fields where autocomplete is not appropriate, e.g. due to security, or the field not matching the specification, the specific field should be ignored.
See how to use HTML 5.2 attributes for more information.
80.2% done
How close this website is to fixing this issue.
This issue is quite technical.
To understand what is going on, you may need some familiarity with
HTML,
the language used to create web pages. Ask a web developer if you need help.
| HTML | Found on page | Issues |
|---|---|---|
<input type="text" size="20" name="hdcaptcha_cp_contactformtoemail_post" id="hdcaptcha_cp_contactformtoemail_post_1" value>
|
3 | |
<input name="cftecontrolmessage" type="text" value>
|
3 | |
<input id="subject_1" name="subject_1" minlength maxlength class="field medium required" type="text" value>
|
3 | |
<input id="email_1" name="email_1" class="field email medium required" type="email" value>
|
3 | |
<input type="text" placeholder="Search" class="s field" name="s">
|
1 |
13
distinct issues were
found in the sample of 76 web pages.