– A form that works on paper may not necessarily work online.
– Don’t ask for the same information more than once; collect only information that you are going to use.
– Provide a logical structure.
And then the article goes on to point out 6 usability issues to keep in mind when designing the web version of the form:
– Avoid using jargon; use clear, simple language for all field labels and questions.
– Provide a context for filling out the form.
– Include field formatting instructions, if necessary.
– Ensure form elements (widgets) can actually be used.
– Ensure all questions are worded clearly.
– Reduce cognitive load in a form; don’t make users think (humans don’t think like a database).
Overall, the change is drastic, and I find the web version of their form much more pleasant to look at. You can also note that they opted for [label placement above rather than to the side](/2006/10/09/label-placement-above-is-faster-than-side/ “Form Labels above the Field”). You can compare the [paper version](http://www.usability.gov/lessons/form.html#initial “Paper Form”) and the [final web result](http://www.usability.gov/lessons/sample.html “Online Form”). In addition, I created a copy of the form using Wufoo. 10 minutes later I had a fully functioning form with validation that met all of the usability requirements.