Checkpoint 1.3.5 Identify Input Purpose

The purpose of each input field that collects information about the user can be programmatically determined when the field serves a common purpose. (Level AA)

Rationale

Objective: Make the meaning of common inputs available via technology

The key beneficiaries of this checkpoint are users with some cognitive disabilities. In situations where users are asked to provide information about themselves, if the purpose of each input can be programmatically determined, then the prompts may be customized through Assistive Technologies or user agents to make them more understandable to a specific user, and potentially easier to complete.

Not all inputs must meet this. The requirement is restricted to common ones identified in WCAG's Input Purposes for User Interface Components section, such as name, address and contact information. As well, this only needs to be implemented when a technology can programmatically indicate the meaning. The most common usage will be employing the autocomplete attributes in HTML.

IBM has simplified the normative language of this checkpoint. Refer to Understanding 1.3.5 (external link to WCAG) for more information.

Development Techniques

This paragraph appears generically in all checkpoints. Review the General techniques as well as other tabs applicable to your technology.  Prioritize the use of technology-specific techniques, and implement the General techniques as needed. You are always required to find, understand and implement accessible code techniques to meet the checkpoint. The documented techniques and supplements are not exhaustive; they illustrate acceptable ways to achieve the spirit of the checkpoint. If numbered, techniques are in order of preference, with recommended techniques listed first. Where used, IBM information that complements the WCAG techniques is indicated as supplemental.

General techniques

There are currently no General techniques. Ensure you review WCAG Common Failures to avoid development mistakes.

Web (HTML, ARIA, CSS) techniques

In addition to the General techniques, any item in this section represents a technique deemed sufficient.

Mobile Native (iOS) techniques

In addition to the General techniques, any item in this section represents a technique deemed sufficient where appropriate. Links are to Apple. Where used, IBM information that complements the iOS techniques is indicated as supplemental.

Hybrid supplement

Apple provides Password Autofill Guidance for both native and hybrid development, which complements the HTML 5.2 autocomplete attributes covered in the Web techniques section of this checkpoint. In addition to covering username, new-password and current-password values for the autocomplete attribute, Apple supports the one-time-code value, which is not covered for 1.3.5

Eclipse techniques

There are no specific Eclipse techniques for this checkpoint. Refer to the General techniques section.

Windows-based (MSAA+IA2) techniques

There are no specific Windows-based (MSAA+IA2) techniques for this checkpoint. Refer to the General techniques section.


Many links in this checklist reside outside ibm.com at the Web Content Accessibility Guidelines (WCAG) 2.1. W3C Recommendation 05 June 2018: http://www.w3.org/TR/WCAG21/

Copyright © 1994-2019 World Wide Web Consortium, ( Massachusetts Institute of Technology, European Research Consortium for Informatics and Mathematics, Keio University, Beihang University). All Rights Reserved.

Copyright © 2019 IBM Corporation