Heuristic Evaluation Checklist

Heuristic Evaluation Checklist

User Interface Information

Provide a description about the user interface. Discuss the purpose and provide information on the tasks that you would complete using the user interface.

 

Don't use plagiarized sources. Get Your Custom Essay on
Heuristic Evaluation Checklist
Just from $13/Page
Order Essay

 

Overall UI/UX

Review the user interface and experience. Discuss the usability overall, including learnability, effectiveness, efficient, engaging, and forgiving.

Learnability

The application is not complex so the user doesn’t have to put an extra effort to understand what the product is about and how to work with it to achieve a goal. The application should tell a story to reveal itself.

 

 

Effectiveness

The completeness and accuracy with which users achieve their goals.

 

 

Efficient

The speed and accuracy with which this work can be done.

 

 

Engaging

How pleasant, satisfying or interesting an application is to use.

 

 

Forgiving

The design allows the users to recover from errors and prevent errors by error detection and correction.

Heuristic Evaluation Checklist

Review the user interface and experience. Complete the heuristic evaluation.

Score: 0-Deficient, 1-Needs Improvement, 2-Fair, 3-Good, 4-Great, 5-Excellent.

 

Visibility of system status

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

Score:

Comments:

 

 

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.

Score:

Comments:

 

 

User control and freedom

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

Score:

Comments:

 

 

Consistency and standards

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

Score:

Comments:

 

 

Error prevention

Eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.

Score:

Comments:

 

 

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.

Score:

Comments:

 

 

Flexibility and efficiency of use

The design should be easier to use for all the user groups. Even though we have only one set of a user group, then there would be novice users and experienced ones.

Score:

Comments:

 

 

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.

Score:

Comments:

 

 

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.

Score:

Comments:

 

 

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.

Score:

Comments:

 

Summary

Provide a summary of the results of the evaluation. Discuss the strengths and weaknesses of the user interface and experience.

 

Strengths

 

 

Weaknesses

 

 

 

Recommendations

Based on the evaluations, provide three suggestions for improvement.

ORDER NOW »»

and taste our undisputed quality.