Table of Contents
    Understanding WCAG Success Criterion Identify Input purpose (AA)

    In an text input form the purpose of each input field that collects information about the user can be understood by Assistive Technologies and browsers, when: The input field serves a purpose that relates to the user of the content. The content is created using HTML or supported by a language which can identify the expected meaning.

    Why is this a problem?

    • People with language and memory problems or disabilities benefit from the browser auto-filling their information.
    • People with motor impairments also benefit from not having to fill in forms with the same information when the browser can do it for them.

    Accessibility requirements for 1.3.5 Identify Input Purpose (AA)

    • A form may be written in a way where its purpose or the purpose of some of the components is not clear. This can be passed by using the HTML 5.2 autocomplete attributes, on fields that collect information about the user.

    NOTE: Remember that you only need to add Autocomplete attributes to inputs that collect information about the user.

    Common mistakes for 1.3.5 Identify Input Purpose (AA)

    • Building a form that collects information about the user without the autocomplete (or other semantic that identifies the purpose of the input)

    Techniques for 1.3.5 Identify Input Purpose (AA)

    Each numbered item in this section represents a technique or combination of techniques that the WCAG Working Group deems sufficient for meeting this Success Criterion. However, it is not necessary to use these particular techniques. For information on using other techniques, see Understanding Techniques for WCAG Success Criteria, particularly the “Other Techniques” section.

    Common Failures for 1.3.5 Identify Input Purpose (AA)

    The following are common mistakes that are considered failures of this Success Criterion by the WCAG Working Group.

    FAQs about Identify Input Purpose

    How the users are impacted by forms?

    Certain group of cognitive disability users find it very difficult to understand the purpose of the form fields with the help of text labels and these results difficult in filling the form
    Low dexterity users find it difficulty in filling the form by typing the same data across the different websites
    People who are having language and memory issues find it difficult to fill the form by remembering data of few form fields such as address, phone number and so on.
    Dyslexia users find it difficult to fill the form by getting the spellings and numbers right

    Solution to this overcome the difficulty in filling forms?

    purpose of each input field collecting information about the user can be programmatically determined. To satisfy this success criterion, authors must use HTML autocomplete attribute in order to programmatically determine the input fields.

    Examples of token values of autocomplete attribute.

    For the name input field, autocomplete=”name”
    for the first name, autocomplete=”given-name”
    for the last name, autocomplete=”family-name”
    for the email , autocomplete=”email”

    Useful resources for 1.3.5 Identify Input Purpose (AA)

    Leave a Reply

    Your email address will not be published.