Marcelo Paiva

All criteriaPresent as slides

A man in a striped jacket and scarf rests his head on one hand at a laptop.Meant to show: A stocky man with Down syndrome in a striped football scarf

Success criterion 1.3.5

Identify Input Purpose

The purpose of each input field collecting information about the user can be programmatically determined when the input field serves a purpose identified in the Input Purposes for User Interface Components section.

  • Level AA
  • Principle 1: Perceivable
  • Guideline 1.3: Adaptable

In a user’s words

“Filling out forms feels like a quiz I didn't study for. But with fields that recognize me, it's more like a friendly chat.”

Who this helps: Cognitive Impairment

What each role can do

Product manager
Ensure all input fields in forms have clear and understandable labels.
Designer
Use placeholders, tooltips, or helper text to guide the user on what information is required.
Developer
Utilize autocomplete attributes where applicable to assist with form filling.
Tester
Verify that all input fields are easily identifiable and functional.

Once it is fixed

“You’ve cleared up the fog! Forms aren't a maze anymore.”

The quotes are written to illustrate the criterion. They are not testimonials from real people. For the official wording, find 1.3.5 in the W3C quick reference for WCAG 2.2 (opens in a new tab).

Or press the left arrow and the right arrow.

A success criterion

This is one page of a phrase book. It takes one success criterion and tells it from the side of the person it helps.

From top to bottom

  1. At the top, the site header: my name, which goes home, then links to Writing, Work, Signal, Tools and Resume, then Settings, where you choose the drawings, light or dark, and movement.
  2. Links back to all the criteria, and to present this one as slides.
  3. A drawing, the criterion’s number and name, what it requires in one sentence, and its level.
  4. In a user’s words: a quote from the person who meets the barrier.
  5. What each role can do: one task each for the product manager, the designer, the developer and the tester.
  6. Once it is fixed: the same person again.
  7. Share this with your team: post to LinkedIn, download the slides as a PDF, or copy a link.
  8. Some criteria then have a t-shirt to order.
  9. Links to the previous and next criterion. The left and right arrow keys go there too.
  10. At the bottom, the footer: a note on how this site is built, links to Illustrations, Pens, Concepts and Accessibility, this Describe this page button, then GitHub, LinkedIn and email.

What you can do here

Learn what this criterion asks, and what your part of the fix is.

Also here

The quotes are written to illustrate the criterion. They are not from real people.