I have been trying to track down research discussing the use of two vs one field for entering an email address on an online form.
I plan to use inline validation for the field and am trying to keep the number of fields to a minimum. The purpose of the form is to donate money to a public broadcast station. The email address is used to send an email confirmation of the transaction (the user gets an immediate confirmation with a printer-friendly version once they complete the process) and is also used to send the new member a monthly newsletter. The transaction is dependent on having a valid credit card and/or an accurate postal mailing address for gifts and billing - in other words, the email address is not an essential component for the transaction to go through but it is clearly important for the user to receive an email confirmation and member newsletter. Can anyone direct me to research discussing the advantages and disadvantages of using one vs two email fields? I am also looking for inline validation code that addresses the one vs two field issue as well. Surfing around I have seen the field represented both ways on forms. The representation is not as consistent as the password field which seems to typically include two fields since the user does not have visual cues. ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
