Bad Form
summary
Shows that usable forms come from concrete rules not theory: adopt HTML5 input types and aria, prefer native validation with polyfills (Modernizr) over rewriting everything, avoid jQuery bloat, and use the uploaded Quaid-JS style validation library example (author’s v4 exists). Enforce validate on blur not keypress, mark optional fields instead of asterisks, strip spaces from numbers and credit cards, place inline error labels next to inputs, repopulate fields after server checks — these changes reduce failures and actually increase completion.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:04HTML5 forms overview
- 4:11Form validation pitfalls
- 8:27Select elements best practices
- 11:59Label placement patterns
- 14:07Completion rates
- 15:52Mark optional fields
- 17:35User-friendly validation
- 24:40Minimum validation rules
- 26:46Password validation myths
- 31:23Address validation limits
- 32:47Email validation pitfalls
- 34:53HTML5 forms with polyfills
- 36:20Performance impact of jQuery
- 38:28Human form design
- 40:12Q&A
related talks
36mBack to Basics Why HTML Forms Still Rule the Web
27mCreating Beautiful, Accessible, and User Friendly Forms
47mMake form validation fun again
01h 07mInclusive Design Series: How to stop worrying and love accessible forms
19mBuilding Forms Mobile Users Will Love
52mConsidering Accessible HTML Forms, JavaScript & WAI-ARIA
50mStructuring Accessible Forms
41mLet’s play with vanilla CSS / JS validations