This is Inputs declare their type and autocomplete purpose as plain markdown, the version AI agents read. Same facts as the page, without the layout.
--- title: Inputs declare their type and autocomplete purpose · Rubric description: 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… url: https://rubric.design/ux/forms.autofill-and-input-type format: agent view of this page updated: 2026-11-16 --- [UX guides](https://rubric.design/ux/) / [Forms](https://rubric.design/ux/topic/forms) / Inputs declare their type and autocomplete purpose # Inputs declare their type and autocomplete purpose Usually high · How 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. [Use demo account](https://rubric.design/demo) · [Use it from your coding agent (MCP)](https://rubric.design/#agents) ## Related guides - [Entered checkout data survives errors and back-navigation](https://rubric.design/ux/checkout.entered-data-persists-through-errors) · Usually high · Preserve every non-sensitive field — name, address, phone, email — across validation errors, session-level failures, and backward or forward navigation within… - [Slow checkout actions show a status, not a frozen screen](https://rubric.design/ux/checkout.loading-state-feedback) · Usually high · Show a spinner or progress indicator within a fraction of a second of any checkout action that can take more than a couple of seconds — payment submission… - [Selecting an option applies it immediately, without a separate Apply step](https://rubric.design/ux/forms.changes-apply-without-a-button) · Usually high · Apply the result of a selection — a radio button, a dropdown, a quantity stepper — as soon as it is made, updating totals, delivery estimates and stock… - [CTA label matches the page it leads to](https://rubric.design/ux/forms.cta-label-matches-destination) · Usually high · Word the CTA to describe exactly what the destination page is, using the same or closely matching terms — a button labelled "See Plans" leads to a page whose… - [Required and optional fields are both marked, consistently](https://rubric.design/ux/forms.required-optional-marking) · Usually high · Mark every field's required/optional status explicitly and visibly — not only the required ones, since a form with asterisks on some fields leaves every…