Usability Principles - Coggle Diagram
System status being visible
The user should always be informed on where they are in the website and what they are doing. This is done through clear descriptions and appropriate feedback.
For example, if the user clicks on a button in the header they expect to be transported to another page in appropriate time and therefore good interface design is doing so.
Having the interface and the real world be interlinked
The system should use words and phrases the user is familiar with rather than system specific language and conventions
For example, if an interface asked the user to input their password a description next to the text box should use the word 'Password' as this is the well known phrase for the type of input required.
The user having a sense of both control and freedom
The user should have an emergency exit to leave pages and functions.
For example, a redo and undo function should be supported
Interfaces have a consistent style and standard
Actions or functions instigated by the user should result in the same outcome throughout the different pages within an interface.
For example, the buttons within the header should always lead to the same pages when they are pushed.
Eliminating error messages from the system
Test the interface thoroughly for errors to ensure that the user does not encounter error messages
For example, if a process commonly results in an error message then the code should either be worked on and then tested or deleted from the interface all together.
Ask the user to recognise information rather than recall information
The system should not ask the user to remember information that is not present on the current interface. Instead, the interface should present the information to the user and ask them to recognise that piece of information
For example, if a user is purchasing an item the picture of the item should be present on the checkout page so that the user does not have to remember what the item they are buying is
A minimalist design should be used within each interface
Every piece of dialogue and every element within the interface should be necessary as unnecessary information cognitively strains the user.
For example, a description next to the submit button is not necessary as the user already knows what the button does and therefore should not be included.
Making sure users understand and diagnose error messages
error messages should be presented in plain language