This blog is best viewed on Mozilla Firefox web browser - www.mozilla.com

Thursday, October 9, 2008

effective registration: part 2

How long or short should a registration form be?

The business objective is to generate user registrations, not to throw them off. However, if a form is confusing, complex or too long, the lower the chances are of completion. Do not ask for too much information on the initial landing screen as it will de-motivate users to fill the form. Making the form fast and simple ensures a higher conversion rate.

Unnecessary fields that are not directly related to the product or service the site or business is trying to offer should not be included. For instance, you need not require the P.O. Box or physical address from a user for merely participating in a social networking site, or ask for credit card details if a user only wishes to open a gift registry on an e-commerce site.

On another note, if additional information will eventually be required at a later stage, as part of the user profile on a social networking site, or at the check-out process on an e-commerce site, you may divide the form into steps or stages.

This means, you keep the most important information on the first screen so as not to overwhelm the user with too many fields, and then guide them through the next steps with a 'skip' button for optional pages. Then, allow users to enter additional information later after their account has been created.

Section headings, consistency and white space

When a form runs continuously, users may consider it a tedious task rather than a process that will benefit them in the end. Adding section headings for fields with a logical grouping creates a visual break in the form preventing information overload.

It is also important to distinguish section headings from field labels, from the page title and from instructional text by use of different text styles or font sizes.

All fields should follow a strict alignment in the entire form, if field labels are right aligned with the input field to the left, it should follow the same trend throughout so that it follows a consistent flow. Also, all input fields, where applicable, should relatively have a uniformed width creating a visual symmetry reducing clutter.

The provision of white space ensures that the layout clean and comprehensible, making it more efficient and user-friendly as it becomes easier to read with less eye strain.

Drop-downs, radio buttons and checkboxes

Drop-downs are not usually recommended for a very long list of choices that can reach hundreds in value as the user would need to scroll several times to view them all. An alternative would be to have a text field which auto-suggests a selection when a user types, or to keep the list in alphabetical order for easier browsing, or replace the drop-down completely with an open text field if the information required is straightforward like a date or year, but be careful to validate the form so the user enters in the correct format.

Radio buttons are essential for 'yes or no', or 'this or that' options, which can replace a drop-down if the selections are limited to a maximum of 3. This aids usability as it saves the user an extra click through a drop-down as the radio button options are available upfront.

Checkboxes are often used to present multiple-selection choices, whereby the user can check '1, 2, and 5', and may replace a radio button at the end of the page where you find 'I agree to the terms & conditions' or 'I would like to receive email updates' so that users need only to read the instruction once without 'yes or no' variations especially when the text is a full sentence.

Finally, it is best not to pre-select a choice in the drop-downs, radio buttons and checkboxes as it would annoy the user to have to un-select or choose another, amounting to more clicks if the pre-selected choice does not apply to them. It is only acceptable in case of language or country, whereby the site can pre-define the selection by detecting the user's computer IP address.

No comments: