出自UXGuide.net

确认信息：设计规范

Confirmations: Guidelines

目录 1 常规 2 图标 3 提交按钮 4 命令链接 5 默认值 6 不要再显示此信息 7 大宗操作 8 渐进展开 9 用户帐户控制

常规

• 仅在存在重大更改的时候才使用“保存更改”确认信息。不要确认那些像文档自动格式化等并非由用户直接作出的更改。

错误：

该示例如果用于用户没有编辑过的空 E-mail 或者文档的话则是错误的。

图标

• 确认信息的标题栏上无须放置图标。
• 确认信息内容区域上的图标根据其设计模式的不同而不同：

  模式	图标
  常规确认信息	无图标。
  风险操作确认信息	警告图标。
  非预期结果确认信息	如果存在风险则使用警告图标，如果对应的功能特性有图标也可使用，否则，不要使用图标。
  明确含义	如果确认信息与文档有关，则使用文档缩略图；否则，如果对应的功能特性有图标则可使用，没有则不使用图标。
  安全确认信息	警告图标。
  隐蔽动机确认信息	无图标。

• 不要在普通问题上使用警告图标。否则会与鼓励式的Windows Vista 语气相悖，且使得使用你的程序如同冒险一般。假设用户明白在任务结束之前取消的后果如何。
  
  错误：
  
  在这个示例中，警告图标用在了一个普通的问题上。

提交按钮

• 将“是”和“否”按钮用于回应确认信息。这使用户能够在对确认信息作出回应之前先思考片刻。绝不要将“确定”和“取消”按钮用于确认信息。

正确：

在这个示例中，使用 Yes/No 提交按钮可以迫使用户至少阅读完主标题说明。

错误：

在这个示例中，使用 OK/Cancel 会造成误解。

例外：

• • 当确认信息的原因显而易见时，应当对主标题说明使用明确的回应。这种方式对于常规确认信息模式最为适用。

在这个示例中，确认信息的原因是显而易见的，因此 Save 和 Don't save 也很合适。

• • 对于明确含义模式，应当改用命令链接。

命令链接

• For the clarifications pattern, consider using command links to make the alternatives clear.

Acceptable:

Better:

In the better example, command links make the alternatives clear.

• Present the most commonly used command links first. The resulting order should roughly follow the likelihood of use, but also have a logical flow.
• If a command link requires further explanation, provide a supplemental explanation. Supplemental explanations describe why users might want to choose the option or what happens if the option is chosen.

For more guidelines and examples, see Command Links.

默认值

• The default response for a confirmation is based on its design pattern:

  Pattern	Default response
  Routine confirmations	Proceed.
  Risky action confirmations	Don't proceed (or the safe choice).
  Unintended consequence confirmations	If consequences are significant, don't proceed; otherwise, proceed.
  Clarifications	The most likely response.
  Security confirmations	Don't proceed.
  Ulterior motive confirmations	Proceed.

不要再显示此信息

• Use this option only for the routine and ulterior motive confirmation patterns. For the other patterns, if the information is necessary, it should always be displayed.
• Don't provide this option to justify displaying an unnecessary confirmation. Just get rid of the confirmation instead.

Incorrect:

Still incorrect:

In these examples, adding a Don't show this message again option doesn't fix an unnecessary confirmation.

For more guidelines, see Dialog Boxes.

大宗操作

• For confirmations that apply to bulk operations, provide an option to apply the confirmation to the entire operation.

This example has an option for bulk operations.

• Eliminate or postpone confirmations in a bulk operation.

Incorrect:

In this example, Windows Explorer in Windows XP confirms each read-only file during a bulk file move. Better just to copy the read-only files without asking, or postpone handling these files and present the confirmation at the end of the task.

渐进展开

• If you must include advanced information in a confirmation message, reveal it by using progressive disclosure buttons (for example, "Show details"). Doing so simplifies the confirmation for typical usage. Don't hide needed information because users might not find it.
• Don't use "Show details" unless there really is more detail. Don't just restate the existing information in a different format.

For labeling guidelines, see Progressive Disclosure.

用户帐户控制

• Don't use the User Account Control (UAC) elevation UI as a substitute for a confirmation. If an action needs a confirmation, use a separate dialog box. During the elevation UI, users need to focus on whether they started task and if the program is trustworthy.
• Display the confirmation before the elevation UI. Doing so eliminates unnecessary elevations.