網頁制作poluoluo文章簡介：Ten Usability Heuristics——可用性10准則.
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.
- 雖然系統最好是可以讓用戶不需要任何說明就能使用，但是提供一個幫助和說明的功能還是有必要的。注重與用戶的任務，任何這樣的信息都要很容易的就可以被用戶找到，列出明確的步驟去實現這些操作，而且篇幅不要太長。
I originally developed