Rating scale

• 0 = I don't agree that this is a usability problem at all
• 1 = Cosmetic problem only: need not be fixed unless extra time is available on project
• 2 = Minor usability problem: fixing this should be given low priority
• 3 = Major usability problem: important to fix, so should be given high priority
• 4 = Usability catastrophe: imperative to fix this before product can be released

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

Recommendations:

• Include visual confirmation clues such as checkmarks
• Show progress bars in the onboarding process
• Use text to notify users of system changes, such as successful publishing and saving

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.

Recommendations:

• Reference similar services and mimic common UI patterns
• Use UI to influence the user's actions and walk them through tasks

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.

Recommendations:

• Provide more information on usage of text inputs and customizable areas
• Build backups and undos and breadcrumbs into the UI
• Allow users more control over the content in their sites, such as deleting photos

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

Recommendations:

• "Clean up" the design for consistency
• Edit the dialogs and text on the page to be more understandable
• Use modern conventions for interactive elements such as buttons and inputs

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.

Recommendations:

• Build undos into the UI
• Make the user enter their password in twice when signing up
• Add warnings for content deletion and other sensitive areas

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.

Recommendations:

• Include visual location clues
• Add tooltips and labels for almost everything

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.

Recommendations:

• Add accessibility and improve keyboard navigation
• Make clickable areas larger
• Improve the usability of the responsive 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.

Recommendations:

• Edit the wording to be more clear and less heavy
• Arrange the dashboard to be less heavy, move the news
• Present the information on each page in a more intuitive way

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

Recommendations:

• Add notifications for action completion
• Add undo buttons and warnings for sensitive actions
• Fix all of the error pages and make them modal windows

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.

Recommendations:

• Be more descriptive of sections of the site without being over bearing
• Create more help and tutorial videos.
• Create first time walkthrough.