Introduction to ten heuristic evaluation principles for Usability Testing

01 the visual system of system status should always be able to get users informed of the current status of the system through appropriate feedback in a timely manner.

02 The system interface should conform to the practice of the real world. The system should use the user's language, sentences, paragraphs, and concepts that the user is familiar with, rather than using system-based terms. Following routine practices, the presented information is natural and logical.

03 A free user with user control may mistakenly execute a function of the system. In this case, a significantThe "Exit urgently" operation allows the user to exit without any expected results,This prevents the system from continuing to execute user misoperations. In addition, the system should support"Undo operation" and "redo ".

04 The Same Thing that follows the uniformity and standardization system should not use different statements, states and operations, which may lead to users' doubts. Generally, the system platform practices should be followed.

05 preventing user errors should be prevented from occurring at the beginning, and any good error information after the event is not as well as the design of preventing unburned errors. Consider setting certain conditions to prevent user errors, or help the User check and confirm before the user chooses to submit the operation.

Something about the internet

06 better than recognizing memories by visualizing objects, operations, and choices, the user's memory burden is minimized. In the continuous operationUsers should not be forced to remember certain information. SystemUse instructions should be significant or easily available when appropriate. 07 efficiency and flexibility(Invisible to novice users)-the operation speed can be improved for expert users, so that the system can take into account both novice users and specialized users.Household. Allows users to quickly customize those frequent operations.

08 simple design operations should not contain irrelevant information or rarely used requirements. Each additional information will compete with the relevant information in the operation, thus reducing the visibility of the main information.

09 to help users identify and diagnose and fix errors and error messages should be expressed in plain language(NonCode), Correctly explaining the problem, and providing constructive solutions.

10 tips and help documentation even if the system can be used by users without the help documentation, it is necessary to provide help tips and documents. This information should be easily searched, integrated into users' tasks, and specific operation steps should be listed, rather than large and general documents.