Validation messages help users recognize, diagnose, and recover from errors. Validation messages should be:
expressed in plain language (no codes)
precisely indicate the problem, and
constructively suggest a solution (if not easily determined from the problem)
Scenarios and Examples
Common validation message wording
The following are some examples of common wording used. This wording is not an exhaustive list and does not cover all possible error conditions that could arise, as these are driven by the contents and business rules for any given page. Usage of this wording should always be considered in the context of the page and the question for which it is being applied. In particular, if several errors are presented together and could display the same message multiple times on a page, care should be taken to ensure that each message is unique. Any situations requiring new error message wording should be reviewed by a member of the UX team.
Tips
For field-level errors, refer to the name of the field as it appears on the screen whenever possible. When users read the error message, it’s much easier associated with the field and more recognizable.
Capitalization of field names should be removed in favour of following the capitalization style of the error message (ie. Sentence case).
Avoid
Phrasing errors as questions.
Referring to the user in the first person using “you” or “your”, “me” or “my”. This can appear accusatory in tone.
“Please enter the company name.” rather than “You did not enter a name for the company”.
Using the same error message for different fields on the same page. This makes it difficult to relate the message to the specific field(s) that caused the error, and some users relate the messages together and understand them as a single error.
“The start date of the reporting period must be entered in the YYYY-MM-DD format” and “The end date of the reporting period must be entered in the YYYY-MM-DD format” rather than “The reporting period must be entered in the YYYY-MM-DD format”
Mandatory field
This is used very sparingly when a page cannot be processed/continue without it.
Situation | When to use | Wording structure | Sample wording |
|---|---|---|---|
Mandatory field
|
| Please enter the {name of field}. | “Please enter the first name of the company contact person.” |
Mandatory field
| Please enter the {name of field}. If unsure of the exact amount, please enter your best estimate. | “Please enter the total household income. If unsure of the exact amount, please enter your best estimate.” | |
Mandatory field
| Please enter the {name of field} for {rostered item}. | “Please enter the business name for location 1.” | |
Mandatory field
|
| ‘Because {name of field}’ was selected, please describe {description of desired input}. | Because “’Other type of payment – specify’ was selected, please describe the other types of payment provided to affiliated companies.” |
Mandatory field
|
| Because ‘{name of field}’ was selected, please select the {description of desired input} | Because "’Yes - specify’ was selected, please select the number of affiliated companies.” |
Mandatory field
| Please enter the {day/month/year} of birth. | "Please enter the day of birth." | |
Mandatory field
|
| Please select the {name of field}. | "Please select the dwelling type." |
Consistency check
This is used to inform users when information entered may not be consistent with other information previously entered.
Situation | When to use | Wording structure | Sample wording |
|---|---|---|---|
Consistency check
| The {name of field} entered does not equal parts {start of line #} to {end of line #}. Please verify and correct these answers if required. | “The total land area entered does not equal parts (a) to (f). Please verify and correct these answers if required.” | |
Consistency check
| The {name of field} entered does not equal parts {start of line #} to {end of line #}. Please verify and correct the amounts if required. | “The total assets entered does not equal parts (a) to (f). Please verify and correct the amounts if required.” | |
Consistency check
| The {name of field} entered does not equal the total of {description of parts}. Please verify and correct these answers if required. | “The total land area entered does not equal the total of all other land areas entered. Please verify and correct these answers if required.” | |
Consistency check
| The {name of field} entered does not equal the total of {description of parts}. Please verify and correct the amounts if required. | “The total assets entered does not equal the total of all other assets entered. Please verify and correct the amounts if required." | |
Consistency check
| The {description of fields comprising the percentage} entered does not equal 100%. Please verify and correct these answers. | “The sales breakdown entered does not equal 100%. Please verify and correct these answers.” | |
Consistency check
|
| The {name of field} entered seems {description, such as high, low, unusual}. Please verify and correct these answers if required. | “The total land area entered seems high. Please verify and correct these answers if required.” |
Consistency check
|
| {name or description of field selected} {“was”/”were”} indicated in question {question number}, but an answer was also entered for {name of field describing related textbox}. Please verify and correct these answers.” | “No related companies were indicated in question 3, but an answer was also entered for the number of related companies. Please verify and correct these answers.” |
Consistency check
|
| The {name of field 1} {“selected” (if dropdown/radio button/checkbox)/”entered” (if textfield)} is inconsistent with {name/description of other fields} } {“selected” (if dropdown/radio button/checkbox)/”entered” (if textfield)}. Please verify and correct these answers. | “The province selected is inconsistent with the country selected. Please verify and correct these answers.” |
Consistency check
|
| The {name of field} entered is not valid for the {name of field} selected. | “The postal code entered is not valid for the province/territory selected.” |
Invalid field
This is used to indicate when invalid information is provided for a given field.
Situation | When to use | Wording structure | Sample wording |
|---|---|---|---|
Invalid field
| The {name of field} must be numeric. | “The closing balance of total assets must be numeric. | |
Invalid field
| The {name of field} must be {length} digits. | "The case number entered must be 8 digits long." | |
Invalid field
| The {name of field} entered must be numeric to 2 decimal places. | “The retail pricing entered must be numeric to 2 decimal places.” | |
Invalid field
| The {name of field} must be entered in the 999-999-9999 format. | “The telephone number entered must be in the 999-999-9999 format. | |
Invalid field
| The {name of field} must be entered in the X9X 9X9 format. | “The postal code entered must be in the X9X 9X9 format.” | |
Invalid field
| The {name of field} must be entered in one of the following formats: X9X 9X9, 99999, or 99999-9999. | The postal/ZIP code must be entered in one of the following formats: X9X 9X9, 99999, or 99999-9999. | |
Invalid field
| The {name of field} entered is not valid. | “The e-mail address entered is not valid.” | |
Invalid field
| The {name of field} entered may not be greater than {maximum range}. The {name of field} entered may not be lower than {minimum range}. | “The number of employees entered may not be greater than 500,000.” “The number of employees entered may not be lower than 1,000.” | |
Invalid field
| The {name of field} entered must be from {lower range} to {upper range}. | “The number of business locations entered must be from 1 to 20.” “The annual sales entered must be from $0 to $1,000,000.” | |
Invalid field
| The {name of field} must be entered in either the YYYY-MM-DD format or MMMM D, YYYY formats. | "The date of incorporation entered must be in either the YYYY-MM-DD or MMMM D, YYYY formats." | |
Invalid field
| The {day/month/year} of birth entered is not valid. | "The year of birth entered is not valid." | |
Invalid field
| The {name of field} entered must occur before {date maximum in long date format}. | “The date of incorporation entered must occur before March 31, 2011.” | |
Invalid field
| The {name of field} entered must occur after {date minimum in long date format}. | “The date of incorporation entered must occur after January 1, 2011.” | |
Invalid field
| The {name of field 1} entered must occur after {name of field 2}. | "The fiscal period end date entered must occur after the fiscal period start date." | |
Invalid field
| The {name of field} entered may not be greater than {length of field} characters. | “The comments entered may not be greater than 500 characters.” |