User experience: What is the form of site confirmation page

You will see many kinds of two confirmed forms.

This article may not cover all, only the most common (you are welcome to provide the case at any time OH).

Related articles: User experience: When to design the site confirmation page

The next content is organized according to the following directory:

1. Two confirmation page (two partition dimensions: Design angle and content and functional dimension)

2. What are the alternatives to the two confirmation page?

3. How do I choose a different form?

Two confirmation pages in the form of:

From the design point of view Division:

1. System Pop-up Box

2. Lightbox (surface layer)

Explanation: The Lightbox effect is similar to the WinXP OS Logout/Shutdown dialog box, which removes the dialog box at the center of the screen, and the rest of the area fades into silvery gray to increase contrast, and no other area can be clicked except for the form controls in the dialog box.

3. E-mail verification and cell phone verification code, such as alternative forms

For example, I want to delete the net account, happy net sent me an email, let me click on the link in the mailbox to confirm must delete. This form is applicable to more important and unrecoverable situations.

Cell Phone Verification Code confirmation form is generally related to funds, but also for more important operations.

From the perspective of content and function

This information comes from Windows Vista UX Guide, to keep the original name in order to avoid the occasional translation of the English language:

1.Routine confirmations (General confirmation)

Confirm That's user wants to proceed with a routine, low risk action.

Verify that the user wants to continue with a regular, low-risk operation.

As shown in figure:

2.Risky Action confirmations (Risk operation Confirmation)

Confirm that "user wants to proceed" with a action that has some risk and can "t be easily undone.

Verify that the user wants to continue an operation that is risky and not easy to undo.

Figure:

3.Unintended consequence confirmations (unexpected confirmation)

Confirm that "user wants to proceed" with a action that has unexpected or unintended
Consequences.

Confirm that the user wants to continue an action that may result in unexpected results.

Many times, the confirmation page is based on the user has a clear intention to operate, in this case, the user may have the consequences of the expected judgment: the deletion means that the result is deleted. And if the deletion of the command can lead to other unexpected results, that is unintended consequence confirmation.

A typical example: in a multi-label browser environment, close the browser, the general will pop up a confirmation box.

Figure:

4.Clarifications (clarified confirmation, inquiring confirmation)

Clarify How the user wants to proceed with a action that has potentially ambiguous or unexpected
Consequences.

Figure out how users want to continue a behavior that could lead to unexpected results.

As if at a fork in the road, the guide said: OK, let's go on. You might want to ask: How do you go? To the left or to the right? Because you're worried there might be an ambush on the right.

UX Guide recommends that no such clarification be required unless it is true that the behavior may occur in a variety of outcomes.

5. Security confirmations(Safety confirmation)

Confirm that "user wants to proceed" with a security consequences.

Confirm that the user wants to continue with an action that will cause a security problem.

This is common to all of you:

6. Ulterior Motive confirmations(confirmed with ulterior motives--Khan, it seems not very good to translate into this)

Do we need to remember so many forms? What is the guiding significance of our actual design?

In fact, these forms also illustrate some of the use of the occasion, there will be some considerations, but also closely related to these forms.

Alternative to two confirmation pages:

I don't like the confirmation page two times? Is there another way to replace it?

1. Prevent errors -Set the task, the user before the destructive operation of the predecessor task need to complete.

For example, in our most recent project, when a user clicks on a button, that command needs to be confirmed, otherwise the unintended consequences of a false click are irreversible. But after clicking on this button, the user is required to fill out a form. When submitting the form, we find it unnecessary to use another two confirmation. Because the user in the process of filling out the form can be thought and regret, since he is willing to spend time and energy to fill out the form, prove that he really want to understand.

2. Provide undo (undo)--Gmail's Undo

Figure:

3. Provide feedback to make the results of the unexpected significant.

Figure: In Alipay Direct Payment page, click Radio button has been used to inform the consequences, so click the next step will not need to confirm again.

4. Elimination of choice -often need to be confirmed because there are two or more response (follow-up action), you can seriously think about whether there must be more than one choice, if only the only one left, then there is no need to ask.

If the option to be confirm is not very important, simply take it off. I hate some sites to give you a long form, below there are two button, one to submit a clear. Often will accidentally click on the empty, the result just busy for half a day of things are not. To avoid this, you can, of course, give me a confirmation when I click Empty, but I'd like to take this button off.

Choice of design form:

It's tiring to write such an article. So I want to finish off this chore, just to talk about how to choose to use the system pop-up or surface.

I've found that since the surface layer, more and more Web 2.0 sites have abandoned the system pop-up box. Start using Lightbox (surfaced), of course, they have advantages and disadvantages, can not generalize.

For example, the following situation:

The system pop-up layer allows me to move the confirmation window to read "What needs to be confirmed".

And if you use the surfacing layer, you have this effect:

How can you confirm that you can't move? Of course, you can put what needs to be confirmed on the surface, provided there is enough information to withstand the amount.

Made a table for the pros and cons of both, for reference (direct section of the PPT diagram ...) ）：