Forms & Validation
A form is where someone finally hands something over: a shipping address, a card number, the reason they want a refund. Most of the decisions behind it are small, and people only notice them when one goes wrong. Where does the label sit? When does an error show up? What happens after someone presses submit with three fields still empty?
Some of these questions are settled. All 16 systems we track put the error message next to the field that caused it, and 9 of 12 put the label above the input. Others are still open. Validation timing splits four ways, with GOV.UK and GitHub Primer checking on submit while IBM Carbon and Porsche check when you leave a field. Disabling the submit button until everything is valid divides the systems evenly. And small choices carry real cost: Baymard found that 32% of checkout users hit validation errors when a form marked only its optional fields.
- systems tracked
- 17
- sources cited
- 19
- evidence cards
- 107
- questions tallied
- 9
Popular questions
Each one is researched across every system we track. Pick one and it opens in chat, ready to send.
Systems tracked
The same core design systems are tallied on every topic, so answers compare like with like. See every source
- GOV.UK
- IBM Carbon
- Shopify Polaris
- Google Material 3
- Atlassian
- GitHub Primer
- Adobe Spectrum
- Microsoft Fluent
- Salesforce Lightning
- Ant Design
- Mozilla Acorn
- Stripe Apps
- shadcn/ui
- Porsche Design System
- Base Web
- GitLab Pajamas
- Radix UI
Got a forms & validation question?
Your first 3 questions are free. Every answer comes with the sources behind it.