confirmation

16 Sep 2010 - 4:20pm
0
2 years ago
5 replies
Terms:
Jeff Kraemer
2009

How many users confirm their email addresses?

Hi all,

I'm looking for stats or anecdotal evidence (yeah, I said it) regarding email verification--that is, you register and a site says your registration will be complete once you click a link they've sent you. The purpose, of course, is to confirm that the user's email address is valid.

If you work(ed) at a site that practices email verification, how many users actually clicked the link you sent? In other words, how many users did not complete registration because of the email verification step?

13 May 2009 - 8:27am
0
4 years ago
5 replies
Terms:
sherihy
2008

Confirm Email field

Does anyone have or know of any research on whether a "confirm email
address" field is helpful or increases the number of valid email
addresses? I am suggesting to my client that they drop it, on the
assumption that most people would copy and paste the same email
address. (But I don't know if that's true, I only know that's what
I do!)

This is in the context of a checkout, where the email address is good
to have but not mission-critical to the task.

Thanks,
Sheri

10 Feb 2009 - 8:36pm
0
4 years ago
9 replies
Terms:
Nonie Kimpitak
2009

Confirmation Dialog Boxes

I'm in the process of creating the "Delete" and "Save"
confirmations for a web app. In most cases, I prefer to label
buttons according to the action being performed. But in this case, in
order to answer the question being posed, it seems as though I should
be using "Yes" and "No" buttons.

DELETE: "Are you sure you want to permanently delete your
selection?"
- [Yes] = delete and return to page
- [No] = skip deletion and return to page

SAVE: "You are navigating away from the page.

11 Jul 2008 - 3:53pm
0
Terms:
Adam Korman
2004

Confirm password field - Superfluous?

Since your users don't have email, it sounds like the plan is to use
the hint (and response) to directly gain access to the account. So
really you're creating two paths to sign in, and you're asking your
users to come up with two passwords instead of one.

First, consider dropping one of the two sign-in paths (i.e., just have
the main password, don't put any strength requirements on it like
minimum length, etc. OR just have the hint/response to sign in).

9 Jul 2008 - 3:25pm
0
4 years ago
32 replies
Terms:
Steven Chalmers
2007

"Confirm password" field - Superfluous?

I have a design for a new user registration form in which I am proposing to
not use a "Confirm password" field and would like your feedback on this
decision.
The form will have 4 fields, all of which are required:

1: User name (This will be supplied to the user prior to their using this
form)
2: Password
3: Hint question
4: Hint answer

The form also has some explanatory text that describes the use of the hint
question and answer which is that the pair of fields will be used when the
user forgets their password.

8 Feb 2005 - 9:29am
0
8 years ago
5 replies
Terms:
Welie, Martijn van
2005

Asking twice for email address in a form

Hi,

Me and my collegues have a discussion about how to minimize the problem that
people are (apparently) not able to type in their own email address
correctly. In the application we developed for a customer this turns out to
be quite an issue.

One of the possible remedies could be to ask people to type in their email
address twice, just as it is often done with passwords.

However, we wonder how effective this will actually be. This trick will not
help if people 'copy-paste' their email adress.

Syndicate content Get the feed