Single line field
TextField component renders an input field as well as supporting UI elements like a label, error message, and hint text.
|Apply an |
|Sets the initial value. Use this for an uncontrolled component; otherwise,
use the |
|A unique |
|Access a reference to the |
|Text showing the requirement ("Required", "Optional", etc.). See Required and Optional Fields.|
|Applies the "inverse" UI theme|
|Applies date format masking to the input value entered
and renders to a text field above the input.
|Apply formatting to the field that's unique to the value you expect to be entered. Depending on the mask, the field's appearance and functionality may be affected.|
|Whether or not the text field is a multiline text field|
|Optionally specify the number of visible text lines for the field. Only applicable if this is a multiline field.|
|Set the max-width of the input either to |
|Sets the input's |
|Additional classes to be added to the root element.|
|Label for the field.|
|Enable the error state by providing an error message.|
|Additional classes to be added to the error message|
|The ID of the error message applied to this field.|
|Additional hint text to display|
|Additional classes to be added to the label text.|
|Location of the error message relative to the field input|
|Additional classes to be added to the field label|
|A unique |
The following CSS variables can be overridden to customize Input/Form components:
This component also makes use of form field styles, which can be customized by the following variables:
When to use
- If you can’t reasonably predict a user’s answer to a prompt and there might be wide variability in users’ answers.
- When using another type of input will make answering more difficult. For example, birthdays and other known dates are easier to type in than they are to select from a calendar picker.
- When users want to paste in a response.
When to consider alternatives
- When users are choosing from a specific set of options. Consider checkboxes, radio buttons, or a dropdown in these cases.
- Don't use placeholder text in form fields. Use hint text instead, if you need to provide contextual information. Placeholder text disappears after a user types a value, therefore users will no longer have that text available when they need to review their entries. People who have cognitive or visual disabilities have additional problems with placeholder text.
- The length of the text field provides a hint to users as to how much text to write. Do not require users to write paragraphs of text into a single-line
inputbox; use a
- Text fields are among the easiest type of input for desktop users but are more difficult for mobile users.
- Only show error messages or styling after a user has interacted with a particular field.
View the "Forms" guidelines for additional guidance and best practices.
- Group each set of thematically related controls in a
fieldsetelement. Use the
legendelement to offer a label within each
legendelements make it easier for screen reader users to navigate the form.
- Keep your form blocks in a vertical pattern. This approach is ideal, from an accessibility standpoint, because of limited vision that makes it hard to scan from left to right.
- Form Guidelines
- "Placeholders in Form Fields Are Harmful"
- Asking for a date of birth
- GOV.UK text boxes discussion
- Four steps for choosing form elements on the Web (PDF)
For more information about how we tested and validated our work for each checklist item, read our component maturity documentation.
ColorMeets AA color contrast standards for accessibility and color blindness.Complete
Forced Colors Mode (FCM)While using FCM the components text is legible and improves readability.Complete
WCAG 2.1 Level AA ConformanceAll Axe checks for WCAG AA compliance have passed.Complete
Screen readersVoiceOver, NVDA, and JAWS screen readers provide concise communication and interaction.Complete
Keyboard navigationComponent is fully navigable with a keyboard.Complete
StorybookComponent has stories to cover all defined props.Complete
ResponsiveComponent designed to work in all responsive breakpoints.Complete
Spanish translationsIncludes Spanish translations for default text content.Not applicable
CodeTokens implemented in code.Complete
DesignTokens implemented in the Sketch.Complete