| Table of Contents |
|---|
...
The text field consists of:
Label - a meaningful label of what information the user needs to provide.
Input Field (the input field can display a hint text).
 |
States
State | Default | Filled |
|---|---|---|
Regular |  |  |
Hover |  |  |
Active |  |  |
Disabled |  |  |
Read Only |  |  |
Error |  |  |
Warning |  |  |
Focused |  |  |
Focused Hover |  |  |
Focused Active |  |  |
Focused Disabled |  |  |
Interaction
Hover - hovering the text field will change the cursor to a text cursor.
When text exists and the field is active -
Clicking the text field will place the cursor at the cursor position.
Double clicking a word inside the text field will select that word.
Triple clicking the text field will select the whole text in the text field, if exists.
When text was not inserted and the field is active -
Clicking the field will place the cursor at the beginning and the hint text will disappear.
Non active - If no text was inserted, the hint text will be displayed again, if exists, when the field will lose focus.
If a character limit was set, reaching the limit will prevent the user from keeping typing.
When used as a secured field (for example, password), the characters are hidden, also when typing (displayed as dots).
 |
Validations and errors
Please refer to Field validation page for more information.
A text field with a warning will have an orange border and a warning icon, as displayed below:
...
Do not use the text field if:
The user needs to enter dates and times. In this case, use a Date Picker or a Time Picker.
The user needs to enter long texts. In this case, use a Text Area.
The user needs to perform a search. In this case, use a Search Field.
Always provide a clear and meaningful label for any input field.
Where appropriate, help users by providing hint texts which describes the expected value of the field.
Proactively guide users to prevent errors. Help them to identify and fix errors as they occur.
When filling a secured text field, allow the user to temporarily view the inserted input.
Accessibility compliance
<<In general each component should be A11y complied, please follow the 3 guidelines linked below. At the very least we should document that each component is in compliance with each of the 3>>Unless otherwise specified, see our general compliance information in Fundamentals - Accessibility
Design
Zeplin link | Screen thumbnail |
|---|---|
 |
...