imbahub
Menu +
EN
Talk to us
IMBAHUB / Knowledge & guides

An error message should explain what to change and how.

Colour alone does not explain an error. Connect the message to the right field, use everyday words and give a concrete correction. Confirm successful submission only when it has happened through the actual contact route.

From error marker to a confident correction

  1. Identify

    Connect the error with the right control.

  2. Explain

    Describe a practical correction.

  3. Follow through

    Test correction, submission and truthful confirmation.

Give every control a visible, clear label

Read the form without relying on placeholder text. Can you tell what belongs in every field? A label such as Company name is clearer than an example alone. Place instructions beside the control that needs them, such as the accepted characters for a reference code.

W3C WAI explains how labels connect with form controls so their purpose can be communicated to assistive technology. Review the visible wording as well: a technically associated but vague label such as Other still does not help someone choose correctly.

Explain errors so people can fix them

Try an empty required field and an invalid format. Identify the field and describe the change. This email address appears incomplete is more useful than Invalid value. If a format matters, provide an understandable example rather than assuming technical knowledge.

A longer form may also need an error summary before its fields, with links to the controls that need attention. Someone who has already entered a detailed enquiry should not have to search the entire page. Avoid a generic summary that is not connected to the actual errors.

Test recovery after the error appears

Use a keyboard to submit the form with errors and visit each affected field. Can you tell what to change? Does focus move predictably? Does the error update once the value is corrected? Check that errors are not conveyed only through a red border or icon.

On mobile, labels, instructions and errors should tolerate larger text and narrow widths. A longer message must not cover its field or hide the submit control. Capture the error state and ask someone unfamiliar with the form to find the next action without verbal help.

TestQuestion for the reviewer
Required field is emptyCan I tell what is missing?
Invalid formatCan I see a valid example?
Several errorsCan I find each affected field?
Corrected fieldDoes the error update clearly?
Mobile and keyboardCan I reach, read and fix the issue without losing context?

Keep validation and confirmation truthful

Browser-side checks can catch common mistakes but do not prove a server has accepted or received the information. Validate data at the appropriate step, and report success only after the actual route confirms it. Do not conceal uncertain receipt behind a green status.

Record five test cases and retest when the form changes. W3C WAI covers labels, validation and user feedback; an automated accessibility scan does not replace manual review of the task. This guide covers understandable fields and errors, not delivery to the recipient.

Sources and further reading

Questions, answered

Is a red field enough?

No. Explain what should change and how to fix it.

Does passing validation mean the enquiry arrived?

No. Confirmation must match actual receipt. See the guide to testing the full contact route.

IMBAHUB

What would you like to make possible?

Colour alone does not explain an error. Connect the message to the right field, use everyday words and give a concrete correction. Confirm successful submission only when it has happened through the actual contact route.

Talk to us
Product interface set to English in an isolated environment with fictional English demo content.

Product interface set to English in an isolated environment with fictional English demo content.