I was working through some broken link issues on a friend's website when it occurred to me. What do all these error messages mean? For example:
- HTTP_400: Bad Request - did I forget to say please?
- HTTP_403: Forbidden - now I really want to know what’s behind that link!
- HTTP_406: Not Acceptable - well, pardon me!
Web users who lack technical expertise may find those messages challenging to comprehend, and even some tech-savvy folks might need clarification on a few.
We all encounter error messages online now and then. But an error message should provide information that helps us understand the issue and provides insight into how to resolve it.
A Good Error Message vs a Bad Error Message
Let’s start with what makes a poorly written error message.
- "Oopsy!" - Inappropriate tone
- "Looks like someone’s server is not responding" - Passing the blame
- "therefore, we can’t fetch your data." - Technical jargon
- "Maybe try again later." - Generic and unhelpful
- No contact email, phone number, or even a link to the Helpdesk - No way out
Now, let’s look at the components of a well-written error message.
- "We are unable to connect you to your account." - Say what happened
- "There may be a technical issue on our end." - Say why it happened
- "Your data is safe." - Provide assurance
- "Please try to connect again." - Help resolve the issue
- "If the problem persists, please contact our support team at support@ourcompany.com or via chat." - Provide a way out.
Remember. Good error messages provide " constructive communication and respect user effort. "
Writing Tips for Well-Constructed Error Messages
- Use Descriptive Language: Write error messages that clearly and concisely describe the problem. Avoid generic messages like "Error 404" and use descriptive language such as "Page not found: The requested page does not exist."
- Use Active Voice: For example, a passive corrective instruction might read, "A secure password is required;" an active instruction might read, "Enter a secure password." Active voice helps with being concise – it is less wordy and more direct.
- Provide Suggested Solutions: When possible, offer solutions or suggestions to help users resolve the error. For instance, if a form submission fails, provide tips like "Check that all required fields are completed." or "Verify your internet connection."
- Use Semantic HTML: Use semantic HTML elements to structure your error messages to allow screen readers to interpret and present the information more effectively to users with disabilities.
- Carefully position error messages: Screenreader users and screen magnifier users require error messages to appear close to the error’s source. If they are not adjacent, they may have difficulty finding the error.
- Contrast and Readability: Ensure the text of your error messages has sufficient contrast against its background, making it easier to read for users with visual impairments. Choose high-contrast color combinations and consider text sizing.
- Testing and User Feedback: Regularly test your website with users with disabilities and gather their feedback to help you identify and rectify any accessibility issues related to error messages.
Effective error messages are essential in alleviating frustration, elevating the user experience, and fostering a positive perception of the system.
