The gold standard for assessing the user experience of a website or application is moderated in-person usability testing. That’s why we built a lab here in Tacoma: to make testing easier. However, usability testing is a rigorous process that involves recruiting people, getting them to show up and then observing as they walk through a website step-by-step.
Usability testing requires time which not every project timeline can afford. When time is a limited resource, we follow a different approach for assessing the user experience of a website or application: a heuristic evaluation — and you can, too.
A heuristic evaluation is a method for identifying potential design problems by reviewing them against common standards. Our preferred framework for conducting a heuristic evaluation is Nielsen’s 10 Usability Heuristics. In a heuristic evaluation, two members of our User Experience team conduct a double-blind review of your website or application using the heuristics listed below. The reviewers then compare their evaluations and create a report outlining usability issues.
Heuristic evaluations offer a cost-effective alternative to user testing, effectively uncovering severe usability problems. If you want to know if your website is optimized for your users, these evaluations are the perfect place to start.
The 10-Step UX Audit Checklist
Visibility of System Status
The design should always keep users informed about what is going on, through appropriate feedback within a reasonable amount of time.
[ ] Are page title headers clearly displayed on every page?
[ ] Are icons and designs consistent across the site?
[ ] Is there clear user feedback for user actions? (e.g, success messages, errors, selections are visible, etc.)
[ ] Do buttons and inputs display different states? (e.g., active, inactive, focus, etc.)
[ ] Does the terminology used on the site match a user’s understanding?
Match Between the System and the Real World
The design should speak the users’ language. Use words, phrases, and concepts familiar to the user, rather than internal jargon. Follow real-world conventions, making information appear in a natural and logical order.
[ ] Are menu options organized logically into categories that are readily understood by the user?
[ ] Are the icons familiar and not abstract?
[ ] Are form fields grouped logically within forms?
[ ] Are error messages worded in a way that a user will understand?
[ ] Are input prompts for forms worded in language that a user will understand?
User Control and Freedom
Users often perform actions by mistake. They need a clearly marked “emergency exit” to leave the unwanted action without going through an extended process.
[ ] Can a user easily cancel or stop an action within the website or application?
[ ] Is it easy for a user to go back a step in a process?
[ ] Is it easy to find exit links?
[ ] Are pop-up messages clear? Is the pop-up’s message clear to a user? (e.g., canceling vs. selecting “ok.”)
Consistency and Standards
Users should not have to wonder whether different words, situations or actions mean the same thing. Follow platform and industry conventions.
[ ] Are the menus easy to find and intuitive? Is the navigation presented broadly and shallowly or is it deep and nested?
[ ] Are design elements used and placed consistently throughout the site?
[ ] Does the site use design patterns or features that are familiar or common to users?
[ ] Is the user’s location clear as they navigate the site?
Error Prevention
Good error messages are important, but the best designs carefully prevent problems 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.
[ ] If an error is detected in a form field, is the form field highlighted with a message to show the user how to correct the error?
[ ] Are required fields marked as required?
[ ] Do form fields provide a forgiving format? (e.g., they help a user with the proper input of information like a telephone number.)
[ ] Are default values or placeholder text displayed on forms to help a user understand what type of entry is expected?
Recognition Rather than Recall
Minimize the user’s memory load by making elements, actions, and options visible. The user should not have to remember information from one part of the interface to another. Information required to use the design (e.g. field labels or menu items) should be visible or easily retrievable when needed.
[ ] Are items available in multiple locations (polyhierarchy) to better match a user’s understanding of categories?
[ ] Are inactive or disabled form fields or buttons grayed or deactivated when appropriate?
[ ] Does the site use adequate white space to separate text and design patterns?
[ ] Is the content organized into logical areas with clear headings?
Flexibility and Efficiency of Use
Shortcuts — hidden from novice users — may speed up the interaction for the expert user so that the design can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.
[ ] Is content written simply and at a level that is appropriate for the users?
[ ] Is it clear to a user where they are when navigating the site?
[ ] Is information scannable and easy to find?
Aesthetic and Minimalist Design
Interfaces should not contain information that is irrelevant or rarely needed. Every extra unit of information in an interface competes with the relevant units of information and diminishes their relative visibility.
[ ] Are forms easy to understand and fill out?
[ ] Is the design focused on essential user actions?
[ ] Does the site have distracting or unnecessary elements?
[ ] Is there clear visual contrast between design patterns and text elements? (e.g., H1-H5 and body.)
[ ] Is content designed for scannability? (e.g., structured through headings, subheadings, bulleted lists and accordions.)
[ ] Are calls-to-action clear and displayed prominently for users?
Help Users Recognize, Diagnose and Recover from Errors
Error messages should be expressed in plain language (no error codes), precisely indicate the problem and constructively suggest a solution.
[ ] Does the site use standard error messaging visuals? (e.g., bold red text.)
[ ] Are error messages provided to the user?
[ ] Are error messages worded simply and unambiguously?
[ ] Do error messages tell a user how to correct an action?
[ ] Are error messages consistent in their style and placement?
Help & Documentation
It’s best if the system doesn’t need any additional explanation. However, it may be necessary to provide documentation to help users understand how to complete their tasks.
[ ] Do complex forms or form fields provide help text?
[ ] Are instructions for using the application task-specific and sequential?
[ ] For more complicated applications, is there an area where users can access a help section?
[ ] Is it easy to return from the help section to the task the user was completing?
Ready to Turn This UX Audit Checklist into Action?
Completing a UX audit is crucial to ensuring your website or application meets user needs and expectations. Whether you’re starting with a checklist or looking to conduct a full heuristic evaluation, taking these steps will help improve your website’s usability.
If you’ve run through this UX audit checklist and want a deeper, double-blind expert review, reach out to our User Experience team. We’re here to help you transition from a quick self-assessment to a comprehensive UX audit with actionable recommendations. Connect with us today.
