Inputs are used to allow users to provide text input when the expected input is short. As well as plain text, Input supports various types of text, including passwords and numbers.
<nord-input label="Label" value="Value"></nord-input>
The type of the input.
Label for the input.
Optional hint text to be displayed with the input. Alternatively use the hint slot.
Visually hide the label, but still show it to assistive technologies like screen readers.
Placeholder text to display within the input.
Optional error to be shown with the input. Alternatively use the error slot.
Determines whether the input is required or not. An input marked as required will be announced as such to users of assistive technology. When using this property you need to also set “novalidate” attribute on a form element to prevent browser from displaying its own validation errors.
Controls whether the input expands to fill the width of its container.
Makes the component disabled. This prevents users from being able to interact with the component, and conveys its inactive state to assistive technologies.
The name of the form component.
The value of the form component.
|Fired as the user types into the input.|
|Fired whenever the input's value is changed via user interaction.|
|Use when a label requires more than plain text.|
|Optional slot that holds hint text for the input.|
|Optional slot that holds error text for the input.|
|Optional slot used to place an icon at the start of the input.|
|Programmatically move focus to the component.|
|N/A||Programmatically remove focus from the component.|
|N/A||Programmatically simulates a click on the component.|
This section includes guidelines for designers and developers about the usage of this component in different contexts.
- Use to provide a text input where the expected input is short.
- Use to only ask for information that’s really needed. Hide optional fields by default if possible or have them shown with a lower priority.
- Use help text and placeholder to provide additional, non-critical instructions.
- Validate input as soon as users have finished interacting with them (but not before).
- Where necessary, label the input as “Optional” when you need to request input that’s not required.
- Don’t use when the expected text input is long. Use textarea component instead.
- Don’t use the placeholder to provide information that’s required to use the input. Hint text should be used for this purpose instead.
Content guidelines #
Input labels act as a title for the text field. Labels should typically be short and in noun form:
When writing input labels, always write them in sentence case, not title case. The first word should be capitalized and the rest lowercase (unless a proper noun):
When an input isn’t part of a form and is placed individually on a page, you could provide the input label as a call to action:
Do not use colons in input label:
This section describes the different input types, their purpose, and when to use each type.
|The default and most common variant. Displayed as a single-line text field. Line-breaks are automatically removed from the input value.|
|A field for editing an email address. Looks similar to a text input, but has validation parameters and relevant keyboard for devices with dynamic keyboards.|
|A single-line text field where the value is obscured. This type will alert user if a site is not secure.|
|A field for entering a telephone number. Displays a number keypad on mobile devices.|
|A field variant that is used to let the user enter and edit an URL.|
|A single-line text field for entering search strings.|
|Used to let the user enter a number.|
Nord provides a lightweight solution for localizing its components. Not all components need localizing, as for the most part snippets of text are set per instance. For full localization guidelines, please see Localization documentation.
If you experience any issues while using Nord Web Components, please head over to the Support page for more guidelines and ways to contact us.