Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when reviewing templates, rendered HTML, or shared components related to Use semantic input type attributes. Validate the final browser-facing markup, not just the source framework abstraction.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-02 | ✓→✓ | = Same ✓ | 0% | 0% |
| case-03 | ✓→✓ | = Same ✓ | -31% | 0% |
| case-04 | ✓→✓ | = Same ✓ | -15% | 0% |
| case-05 | ✓→✓ | = Same ✓ | 92% | 0% |
| case-06 | ✓→✓ | = Same ✓ | 6% | 0% |
Using type=text for every input forces mobile users to switch keyboards manually for email, phone, and number entry. The correct type also enables browser autofill to correctly identify fields for name, address, and payment data. Combined with autocomplete attributes, semantic types can make form completion 40% faster for returning users.
Audit all input elements in this HTML file. Check whether each uses the most appropriate type attribute and autocomplete value.
Update input type attributes to semantic values and add appropriate autocomplete attributes for autofill support.
Explain the different HTML input types, what each one does on mobile keyboards, and how to combine them with autocomplete attributes.
Review templates, server-rendered HTML, and shared components that output markup related to Use semantic input type attributes. Flag exact elements, attributes, and routes where the rendered HTML violates the rule.
For full implementation details, code examples, and framework-specific guidance, see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/html/input-types
Other measured skills in the registry, with their headline benchmark lift.