最初十个原则是针对网页设计的，不过对于网页之外的界面设计也很有指导意义。
请参考。

启发式可用性评价十原则
尼尔森

• 可视性原则：系统状态有反馈，等待时间要合适
• 不要脱离现实：使用用户语言而不是开发者语言，贴近生活实际而不是学术概念
• 用户有自由控制权：操作失误可回退
• 一致性原则：同一事物和同类操作的表示用语要各处保持一致
• 有预防用户出错的措施：关键操作有确认提示，及早消除误操作
• 要在第一时间让用户看到：识别胜于回忆，提供必要的信息提示（可视&易取），减少记忆负担
• 使用起来灵活且高效：为新手和专家设计定制化的操作方式，快捷操作可调整。
• 易读性：减少无关信息，体现简洁美感
• 给用户明确的错误信息，并协助用户方便的从错误中恢复工作
• 必要的帮助提示与说明文档：无需文档就能流畅应用当然更好，一般地文档很必要，而且也提供便利的检索功能，面向用户任务描述，列出具体实现步骤，并且不要太冗长。

补充以下网页设计方面的内容：

在评估时可以考虑这些方面：

Navigation，导航
清晰指示了当前的位置
清晰定义了首页的链接
网站的所有主要 部分都能通过首页访问
如果需要的话，应该有个站点地图
网站结构清晰，没有不必要的层级
如果需要的话，要有个易用的搜索功能

Functionality，功能
所有功能都被清晰地表示出来
所有重要功能在不离开网站的前提 下都可以使用
没有不必要的插件

Control，控制
用户可以取消所有操作
在每一页，用户都可以找到清晰的离开本页的标识
所 有图片链接都和文字链接一样清晰可用
网站的流程符合用户的操作流程
支持所有主流浏览器

Language，语言
文案简洁
没有术语

Feedback，反馈
现在网页发生了什么，应该一直都清晰的标示出来
如果必要的话，用户应该 能收到email反馈
所有反馈都要及时准确
如果需要安装插件或者需要特定的浏览器，必须告知用户
用户可以通过email或者提交 表单来提交反馈意见
如果必要的话，提供个在线帮助

Consistency，一致性
对任何元素都只有固定的一种叫法
链接与其指向页面的标题要匹配
对 链接和已访问链接使用规范的色彩
一致使用术语的普遍叫法

Error Prevention，防止出错
使用朴素的语言来表述错误信息
错误信息需要给出下 一步操作提示
错误信息提供清晰的离开标识
错误信息提供详细的帮助信息

Visual Clarity，视觉清晰
布局清晰
足够的留白
所有图片都有alt标记
使 用标准的模版

【原文】

Ten Usability Heuristics

by Jakob Nielsen

These are ten general principles for user interface design. They are called "heuristics" because they are more in the nature of rules of thumb than specific usability guidelines.

Visibility of system status

The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.

Match between system and the real world

The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.

User control and freedom

Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.

Consistency and standards

Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.

Error prevention

Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.

Recognition rather than recall

Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.

Flexibility and efficiency of use

Accelerators -- unseen by the novice user -- may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.

Aesthetic and minimalist design

Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.

Help users recognize, diagnose, and recover from errors

Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.

Help and documentation

Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.

转载本文请联系原作者获取授权，同时请注明本文来自刘希未科学网博客。
链接地址：https://blog.sciencenet.cn/blog-333718-292283.html

上一篇：[转贴] 分析师：竞争不过中国对手 谷歌是找体面理由退出
下一篇：管理之劫：死亡的制度