Why keyboard types matter
Touch typing in the wild is slow and error-prone (Reyal et al., 2015). Numeric keypads with large keys reduce errors (Parhi et al., 2006). One setting can transform mobile form usability.
Setting them on web and apps
Use type and inputmode (MDN, n.d.-a) and autocomplete for email, address and OTP autofill (MDN, n.d.-b). Prefer inputmode=numeric over type=number for identifiers. iOS uses textContentType (Apple, n.d.); Android uses inputType (Android Developers, n.d.).
Enter key and autocorrect
Set Enter to Next, Search or Send (enterkeyhint, imeOptions). Disable autocorrect and auto-capitalization for emails, usernames and codes. Declare purpose per WCAG 2.2 (W3C, 2023) 1.3.5 and flag errors with inline validation.
FAQ
- Is type=number wrong?
- Fine for quantities; use inputmode=numeric for identifiers.
- When to disable autocorrect?
- For emails, usernames, codes and addresses.
Sources reviewed: 2026-10-27
References
- MDN Web Docs. (n.d.-a). inputmode. Choosing virtual keyboards.
- MDN Web Docs. (n.d.-b). HTML attribute: autocomplete. Autofill tokens.
- Apple. (n.d.). UITextContentType. UIKit documentation. iOS content types.
- Android Developers. (n.d.). Specify the input method type. inputType and action keys.
- Reyal, S., Zhai, S., & Kristensson, P. O. (2015). Performance and user experience of touchscreen and gesture keyboards in a lab setting and in the wild. In Proceedings of the 33rd Annual ACM Conference on Human Factors in Computing Systems (pp. 679–688). ACM. Touch typing is slow and error-prone.
- Parhi, P., Karlson, A. K., & Bederson, B. B. (2006). Target size study for one-handed thumb use on small touchscreen devices. In Proceedings of MobileHCI 2006 (pp. 203–210). ACM. Bigger keys, fewer errors.
- World Wide Web Consortium. (2023). Web Content Accessibility Guidelines (WCAG) 2.2. Criterion 1.3.5 input purpose.
