...

Field Validations are a way of talking to our users. It is designed to make making the user understand a mistake, and the ways how to correct it.  Example:

...

Types

Usage & Behaviour

Internal Logic

All input fields will display the value entered by the user. If the input is invalid, an indication for invalid/warning will be displayed. Prevention of input is not allowed (e.g. typing on the keyboard “A” and not displaying it in the field)

Triggering the validation is set by 3 types:

• Syntax validation - validation should be displayed while typing.
  For example:

  • An illegal character was typed  (e.g. numbers instead of alphabetic)

  • Exceed the number of characters (e.g. user input 3 digit number where only 2 digits is allowed)

• Logical validation - any validation that is set on the required value (e.g. Max. input of 100)

  • In most cases, the validation will occur after the user left the field

• Missing input on a required field

  • Validation is displayed as soon as the user leaves (out of focus) the required input field which has no input

  • Note: when a form has a single required field, the validation will appear only after the user tries to submit the form (Submit button is enabled)

Autocorrect - Some cases require an automatic correction of the invalid input.

• The components Pagination and Slider with a numeric input, which have a clear visible definition of a numeric range, will behave as follow.

  1. An invalid value will be indicated.

  2. On OutOfFocus (e.g. user clicked somewhere outside the field) the entered value will automatically change to:

     1. Last valid

     2. Edge range - if the input exceeds the range of options(e.g. in pagination “0” will auto-correct to the “1” )

• Connected fields - where different fields are dependent on each other and the numeric range is dynamic.
  On OutOfFocus with an indicated invalid input, a pop-up message will appear with the options of:

  • Back - returns the focus to the field with the last used input 

  • Revert - returns the focus to the field with the latest valid input (the one before the user changed it)
    See pop-up example:

    Image Removed

Default input/validation

• When starting to edit a field with a validation indication on it, the current indication will be hidden (i.e. it will be treated as if the user had edited the field for the 1st time).

• If the user had entered a form/page/screen for the first time (fields are empty), logical validation should not be enabled. However, syntax validation should be enabled.

• In cases where the user enters a page that already had input, the warning validation should be displayed (e.g. the user enters a page already edited with warnings in it).

Structure

...

Structure

A validation field consists of:

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

• A  validation tooltip message appears upon hover of A validation Tooltip message, which appears on hover over the validated field/component .

• A descriptive message next to the submit buttonaction buttons:

  • Error messages have a higher priority than a warning . In case the error was messages. When errors are fixed, the warning validation should then be presentedshown.

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

Examples:

 *  Unlike "field validation error" the warning version

Components		Error	Warning
Text fieldField
Text areaArea
Dropdown menuDrop-down Menu
Combo box (free text field)Box
Spinner (free text field)Numeric Stepper
Date Picker (free text field)Picker
Time Picker (free text field)Picker
Search fieldField		NA
SwitchSwitches		NA
Slider		NA
Single checkboxcheck box		NA
Checkbox Check box group
Grid table cell
Tab Tabs
Call To Action with short text		on Error, the button is disabled
Call To Action with mixed errors  error  Error takes priority
Call to action with long text.  Pop-up size might need to expand in height

• Unlike Errors, the Warning fields can appear on top of controls

...

• which do not have a text field, since a warning can appear when there is a conflict between

...

• two controls.

...

Text position:

• Text position can be either near the CTA calls to action (right-aligned) or at the beginning of the row (left-aligned) according to size and available width
  See examples:

...

Content

• Descriptive text on the actions row (e.g. Submit)near the action buttons.

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

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

• If multiple fields didn't pass haven’t passed validation of the same type, the text near the CTA action buttons should be "X warnings found" <<TBD with Docs.>>‘X warnings found’.

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

  

• In general:

  • Specify why the field info was information has not been accepted - your . 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 it short!

Rephrasing examples (taken from Verint's Suite):

Internal Logic

All input fields will display the value entered by the user. If the input is invalid, an error or warning message will be displayed. Prevention of input is not allowed (e.g. not displaying characters in the field as they’re entered).

Errors and warnings can be trigger by 3 types of action:

• Syntax validation.
  Validation should be displayed while typing. For example:

  • An illegal character was typed (e.g. numeric instead of alphabetic).

  • The maximum number of characters has been exceeded (e.g. user input a 3 digit number where only 2 digits are allowed).

• Logical validation.
  Any validation that is set on the required value (e.g. Max. input of 100). In most cases, the validation will occur after the user has left the field.

• Missing input on a required field.

  • Validation is displayed as soon as the user leaves (out of focus) a required input field which has no input.

  • Note: when a form has a single required field, the validation will appear only after the user tries to submit the form.

Autocorrect. Some cases require an automatic correction of the invalid input.

• The components Pagination and Slider with a numeric input, which have a clear visible definition of a numeric range, will behave as follows.

  • An invalid value will be indicated.

  • When the user clicks outside of the field (out of focus), the entered value will automatically change to:

    • Last valid.

    • Edge range, if the input exceeds the range of options (e.g. in pagination 0 will auto-correct to 1).

• Connected fields. Where different fields are dependent on each other, and the numeric range is dynamic.
  When the user clicks outside of the field (out of focus) with an indicated invalid input, a Popup message will appear with the options of:

  • Back - returns the focus to the field with the last used input.

  • Revert - returns the focus to the field with the latest valid input (the one before the user changed it).

    Image Added

Default validation

• When starting to edit a field with a validation message on it, the current validation will be hidden (i.e. it will be treated as if the user had edited the field for the 1st time).

• If the user has entered a form, page, or screen for the first time (fields are empty), logical validation should not be enabled. However, syntax validation should be enabled.

• In cases where the user enters a page that already has an input, the warning validation should be displayed (e.g. the user enters a page already edited with warnings in it).

Interaction

Validation tooltips

• Any field /or tab that has validation indication message will also have a tooltip.

• The validation tooltip takes priority over any other tooltip (if one exists).

• Location By default, the location of the tooltip is by default on to the right of the field, except when where there is no space

• Tooltip timing should be - Tooltips (see interaction section) 

• Warning and Error has .

• See the Interaction section of Tooltips for timing information.

• Warnings and Errors have the same tooltip interaction.

Tooltips positioning examples:

Content	Examples	Comments
1 or more rows of text, to the right to of the warning or error icon of validaton
Partial coverage of control		User can still click the control
Left position

...

Use field validations for any user input fieldsContent Guidelines.

• 2 options for the content of the error message:

  • Generic 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, for EX: "such as This is not a valid zip code" .

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

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

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

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

• Try to avoid negative words

  (e.g. "

  . For example rather than

  • Rather than Password does not meet requirements" or "Invalid Password" → could be turned into→ "use Password must contain 8 alphanumeric characters")

         

  • .
    Image Modified

Accessibility Compliance

Unless otherwise specified, see our general compliance information in Fundamentals - Accessibility.

Design

Zeplin link	Screen thumbnail
https://app.zeplin.io/project/5970b366bee38cf87b2de932/screen/5baca0fa7044c49e813fe220
https://app.zeplin.io/project/5970b366bee38cf87b2de932/screen/5baca11066034667cc35f576

...