The First Contact
summary
Registration forms often fail on details: use one field for full name and support Unicode and very long names (one example hits 988 characters), ask for pronouns instead of a binary gender field, require only data you actually need, and mark required fields clearly. Validate dates with a date picker and tolerant parsing, send an email verification link and allow correcting typos, show all actionable errors inline, and for passwords allow passphrases, use PHP’s password hashing API, don’t roll your own crypto, and don’t disable paste or password managers.
AI-written summary · about
chapters (19)
- 0:00Intro
- 1:06Who am I
- 1:17Disclaimer
- 2:05Examples of Registration Forms
- 8:08Family Name
- 8:35Transcription
- 10:17Twitter Threat
- 10:44Gender
- 12:27Email
- 15:05Dates
- 18:42Required Fields
- 19:34Optional Fields
- 19:53Error Messages
- 24:09Passwords
- 31:58Copy and Paste
- 33:13Security Questions
- 34:16CAPTCHA
- 34:52Captures
- 35:37Honeypot
related talks
48mCollecting information with care
27mCreating Beautiful, Accessible, and User Friendly Forms
14mBuild a signup flow that doesn't suck
29mDesigning Accessible Sign Up Forms
14mSign-up form best practices
57mSpeak your users’ language: what to look out for when going global
46mContent Design Saves Your Forms
37mBuilding simple and secure account systems on Android