Web Application Form Design
The pros and cons of different web form layouts are explored and explained by Luke Wroblewski in Web Application Form Design.
- Previous post: Killing Referral Spam
- Next post: An introduction to mod_security
Favourites, here and elsewhere
Best of 456 Berea Street
- Bring on the tables
- How to use HTML tables the right way – to create accessible data tables.
- Fixed or fluid width? Elastic!
- How to combine fixed and fluid width to create an elastic layout.
- A web professional can never stop learning
- People who refuse to update their skills can not be called web professionals.
- CSS 3 selectors explained
- Browser support for CSS 3 selectors is currently lacking, but taking a look at what lies ahead is still useful.
- Google valid and strict
- Making Google’s home page use valid HTML 4.01 Strict and CSS for layout reduces file size by 21 percent.
Random places to go
Affiliation
Support this site
Show your support by buying a book or two from SitePoint or getting me something from my Amazon Wish List.
Comments
I'm surprised this article didn't say anything about fieldsets...
Good article though... personally i go with the right aligned nav...
I'm thinking maybe some JavaScript would help, whereby the label of the selected element becomes bold... infact that can probably be done with CSS can't it? or is that CSS3?
Has provided food for though anyway...
Fieldsets are definitely part of good form design. The example forms in the article are pretty simple though, so maybe that's why there is no mention of fieldsets.
My personal favourite is the vertical labels layout.
This is very timely. We've just revamped the UI of our product, one of the key decisions was to pick an efficient way to build forms.
We used to put form controls in tables, but the markup was too repetitive, we hated carrying around more HTML than we had to. Besides, styling the right look with tables sucked.
Eventually, we settled on definition lists.
Sorry, comments are closed for this post.