Skip to content

UX guides / Forms / Inputs declare their type and autocomplete purpose

Inputs declare their type and autocomplete purpose

Usually highHow serious this usually is when it goes wrong. Not a score.

The guideline

Set the type attribute to match the data a field collects (email, tel, number with inputmode, and so on) and add the matching autocomplete token from the HTML Autofill specification — email, tel, cc-number, postal-code, shipping address-line1, and similar — to every field that collects information a browser could reasonably fill in. Disable autocapitalize and autocorrect on fields where they corrupt the value, such as email addresses, usernames and codes, rather than leaving platform defaults on. Verify the result on an actual mobile device: the correct keyboard should appear without the user switching layouts, and browser or password-manager autofill should offer a match.

Common failures

  • Forms default to a standard text keyboard for every field, forcing mobile users to manually switch keyboard layouts when entering phone numbers, postal codes, card details, and email addresses—adding friction and increasing typo risk.

Where it applies

Pages

  • Forms

Disciplines

  • Conversion

Devices

  • Desktop web
  • Mobile app
  • Mobile web

Why it matters, how to fix it, and the research behind it

Rubric's full guide adds the reasoning, the fix and the sources for this check, and checks your pages against it and the rest of the checklist, the way a visitor would meet them. Findings come back worst first.