...

Usage & Behaviour

Structure

A validation field consists of:

• Color frame with a small icon on the top-right corner. This marks the validation type.

• A validation Tooltip message, which appears on hover over the validated field.

• A descriptive message next to the action buttons:

  • Error messages have a higher priority than warning messages. When errors are fixed, the warning validation should then be shown.

  • Where there is limited space or a short form, no descriptive message will appear.

Examples:

Components		Error	Warning
Text Field
Text Area
Drop-down Menu
Combo Box
Numeric Stepper
Date Picker
Time Picker
Search Field		NA
Switches		NA
Slider		NA
Single Check Box		NA
Check Box group
Spreadsheet Tables cell
Tabs

...

• Descriptive text near the action buttons.

  • If only one field hasn’t passed validation, the text near the action buttons should be the same as the tooltip.

  • If both Warnings and Errors are found, the text should address the Error.

  • If multiple fields haven’t passed validation of the same type, the text near the action buttons should be ‘X warnings found’.

• In cases where the text is very long, the section should get a Scrollbar.
  For example:
  

  Image RemovedImage Added

• There are 2 options for the content of the error message:

  • Generic
    The content of the message is written in advance and there is no need to refer to the specific text that the user typed, such as This is not a valid zip code.

  • Input based (Preferred where applicable)
    The content of the message can dynamically change based on user input. Use it to clarify where the error is coming from. For example:

    • Rather than Invalid input use → Zip codes cannot contain the special character "%".

    • Rather than You cannot book this flight. Please select another destination or date. Use → Direct flights to Dublin are only available in August. Please select another destination or date. 

...

• Use field validations for any user input fields.

• Specify why the field information has not been accepted. Your validation messages should tell users exactly why their information got rejected or may have some risk, and how it can be fixed.

• If the values entered may impact some other part of the system, briefly explain what may be impacted.

• Keep the text short!

• For complicated fields, using an example in the tooltip message can help.

• Try to avoid negative words. For example: Rather than Password does not meet requirements or Invalid Password use → Password must contain 8 alphanumeric characters.

• Additional examples to avoid:
  

Accessibility Compliance

...