Menu
Experience design
Help users to remain in control
We should encourage a sense of freedom and confidence in the user, and make it easy for all of them to back out of a process or undo an action & avoid/correct mistakes.
UX Owner: Emeline Lise
UI Owner: Gemma D.
This page is In Progress and subject to frequent changes
Please contact Adrian T. to verify any information is correct before using it.
We all make mistakes
Users with disabilities may be more likely to make mistakes, so you should use a combination of techniques to prevent, detect and correct errors that have serious consequences. We need to put the user in control of their experience by:
Avoid mistakes with serious consequences
When it comes to errors and mistakes in the user experience, prevention is key. To avoid unrecoverable errors, you must provide all users the opportunity to detect mistakes before committing an action that cannot be reversed (this is particularly important for financial transactions, tests i.e. drivers licence, deleting important data, etc.).
Where possible, prevent mistakes from happening by using appropriate & effective messaging techniques like alert, validation and success.
How to create a good error message
Diagram coming soon
Highlight mistakes and suggest corrections
When a user does encounter an error, facilitate and be of assistance. Error messaging in a form should use a combination of techniques to communicate the issue(s). It must be constructed with a combination of a specific text description and visual cues to ensure all users can easily identify where and what is the issue.
See some WCAG-compliant examples of how to highlight an errorWhere possible a suggestion of the right answer should be visible alongside the error message.
See some WCAG-compliant examples of error messagesIt should include a mechanism that allows users to jump to errors, and provide successful feedback when data is submitted successfully.
What is a good combination?
The best way to help your users is to give instant help and feedback as they type, and use technology to format the data.
Diagram coming soon
Always give feedback in a non-intrusive manner
We need to inform our users of their progression in their journey without disrupting their experience. The aim is to let them know how they are progressing and if they are successful, not to stop them in their journey. From a slow loading page to added content, the site should always and immediately make sure all users know what is happening as they enter an input or take an action in a non-disruptive way. We must ensure that status text, alt-text and all other copy in the code used by assistive technology can communicate those changes.
In the case of the system experiencing a slight delay, it should inform the user and communicate when its action is finished.
See the WCAG guidelines on how to give constructive feedbackWARNING!
By communicating all changes the system might become too chatty and overwhelm our users. It’s best to use moderated testing to find the optimal balance.
Diagram coming soon
Reduce the noise and user anxiety
Depending on how we design them, our experiences can improve or worsen user anxiety or overload their senses. We need to be considerate with the mediums of communication we use in our designs and must:
Avoid autoplaying video and audio
Did you know video and audio files usually play on the top of the screen readers?
Avoid using autoplay for sound and images as it might become a nuisance for our users with disabilities. You should completely turn off all background sounds and give control of the volume to users. Let the user switch it on when they are ready, as sound from video and audio files usually play over the top of the screen readers.
Moving images also can distract users with low literacy, reading and intellectual difficulties, and those with attention deficit disorders. It’s best to stop the video after five seconds if autoplay is used.
See the WCAG guidelines on audio control See the WCAG guidelines on pause, stop and hideTurn off time limits
First and foremost, everyone moves at their own pace, and users with disabilities will likely take longer to complete a task so time limits increase pressure and anxiety for those users.
Time limits include timed ‘windows of opportunity for user input, and animated, moving or scrolling content. These time limits could stop some users from reading or interacting with our content or completing their tasks.
We must avoid time limits altogether, but if a time limit is necessary on your journey, page or product, then you must provide options to:
There are some exceptions, including if the time limit is essential; a required part of a real-time event, such as an auction, or if the limit is longer than 20 hours.
See the WCAG guidelines on time limits