<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=454436&amp;fmt=gif">

WCAG 2.1 Check Point 1.3.5 - Identify Input Purpose

Summary:

Check that input fields can be programmatically identified.

Details:

For content created with markup languages, the purpose of specific input fields needs to be communicated programmatically such as via the autocomplete attribute in HTML. The purpose can then be transformed by personalization tools to communicate this in different ways, such as via icons or symbols to assist users who have cognitive and learning disabilities.

Using techniques such as the autocomplete attribute (from HTML) will make completing forms easier for everyone, by reducing the overhead of typing in common information such as address and credit card numbers. This benefits all users, but has a much greater impact on people with cognitive impairments.

Note: The autocomplete attribute works with the following <input> types: <em>text</em>, <em>search</em>, <em>url</em>, <em>tel</em>, <em>email</em>, <em>password</em>, <em>datepickers</em>, <em>range</em>, and <em>color</em>.

Examples of success:

The example of a form below enables autocomplete for all fields except it is disabled for the email field.

<div>

<code>

<form action="/action_page.php" autocomplete="on">

   First name:<input type="text" name="fname" id="fname">

   Last name: <input type="text" name="lname" id="lname">

   E-mail: <input type="email" name="email" autocomplete="off">

   <input type="submit">

</form>

</code>

</div>

Not sure where to start?

Start with a free analysis of your website's accessibility.

Get Started