Buttons are used for interface actions. Primary style should be used only once per section for main call-to-action, while other styles can appear more frequently.
<nord-stack gap="s" direction="horizontal" wrap> <nord-button href="#">Default</nord-button> <nord-button href="#" variant="primary">Primary</nord-button> <nord-button href="#" variant="danger">Danger</nord-button> <nord-button href="#" variant="dashed"> <nord-icon slot="start" name="interface-filter"></nord-icon> Filter </nord-button> <nord-button href="#"> <nord-icon name="interface-menu-small" label="Options"></nord-icon> </nord-button> <nord-button href="#" variant="plain">Plain</nord-button> <nord-button href="#" disabled>Disabled</nord-button> </nord-stack>
The style variant of the button.
The type of the button.
The size of the button. This affects font-size and padding.
When provided, renders the button as a link, with its href attribute set to the given value.
When provided together with a href property, the button will trigger a file download instead of a page visit.
When provided together with a href property, determines where to open the linked URL. The keywords have special meanings for where to load the URL: “_self” means the current browsing context, “_blank” usually a new tab but users can configure browsers this to open a new window instead, “_parent” means the parent browsing context of the current one, but if no parent exists, behaves as _self, and finally “top” means the topmost browsing context.
Controls whether the button expands to fill the width of its container.
Controls whether the button is in loading state. Please note that the spinner is hidden from assistive technologies, so you need to make sure to announce the loading state to e.g. screen reader users. We also recommend disabling all user interactions on the button itself while in loading state.
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.
Gets the form, if any, associated with the form element. The setter accepts a string, which is the id of the form.
The button content
Used to place content at the start of button text. Typically used for icons.
Used to place content at the end of button text. Typically used for icons.
Programmatically move focus to the component.
Programmatically remove focus from the component.
Programmatically simulates a click on the component.
CSS Custom Properties provide more fine grain control over component presentation. We advise utilizing existing properties on the component before using these.
Controls the rounded corners of the button, using border radius tokens.
Controls the spacing between items within the button, using our spacing tokens.
Controls the overlayed gradient background on the button.
Controls the background color of the button, using our color tokens.
Controls the border color of the button, using our color tokens.
Controls the text alignment for the text in the button.
Controls the surrounding shadow, using our box shadow tokens.
Controls the color of the text within the button, using our color tokens.
Controls the inline, or left and right, padding of the button.
Controls the size of the text within the button, using our font tokens.
Controls the weight of the text within the button, using our font tokens.
Controls the minimum block size, or height, of the button using our spacing tokens.
Controls the color of toggle icon that gets rendered when the button is used as a Dropdown toggle.
This component is internally dependent on the following components:
This section includes guidelines for designers and developers about the usage of this component in different contexts.
- Only use one primary button per section, as a main call-to-action.
- Use clear and accurate labels.
- Use established button colors appropriately. For example, only use a danger button style for an action that’s difficult or impossible to undo.
- Prioritize the most important actions. Too many buttons will cause confusion.
- Be consistent with positioning of buttons in the user interface.
- Use strong, actionable verbs in labels such as “Add”, “Close”, “Cancel”, or “Save”.
- Don't use a primary button in every row of a table.
- Don’t use buttons to link to other pages. Use regular link or a plain style instead where necessary.
- Don’t use buttons for navigation where the link appears within or following a sentence.
- Don’t use labels such as “Read more”, “Click here” or “More”.
Content guidelines #
Button labels should be clear, accurate and predictable. It should be possible for the user to understand what will happen when they click a button:
When writing button labels, always write them in sentence case, not title case. The first word should be capitalized and the rest lowercase (unless a proper noun):
Avoid unnecessary words and articles in button labels, such as “the”, “an” or “a”:
This section describes the different component variants, their purpose, and when to use each variant.
|Default style is the most common button variant. Only switch to another variant if you need to adjust the visual weight of the element.|
|Primary style is reserved for main call-to-actions. Should be used only once per content area or panel, e.g. for a “Save” action.|
|Dashed style should be used for actions that trigger filtering.|
|Danger style should be used for actions that delete data or otherwise make it hard to undo the action.|
|Used for less important or less common actions. Can be also used for linking to other pages.|
|Used for actions that aren’t currently available or not available anymore. Also prevents users from being able to interact with the component, and conveys its inactive state to assistive technologies.|
Icon usage in button #
Illustrative icons should be always positioned in the
When a button is used as a dropdown toggle, the
interface-dropdown-small icon from Nordicons is automatically placed in the
Each button size has a recommended icon size. The medium button uses the
s icon size, the small button uses the
xs icon size, and the large button uses the
m icon size. The icon will adjust size automatically based on the button size, so you will get the correct behavior by default. However, this can be overridden by explicitly setting a size on the icon.
interface-add-small icon in the
start slot for create/add type primary actions in the header:
Additional considerations #
- Users of assistive technology expect a button to submit data or do an action. If you need the button to navigate into another view, use the
hrefproperty which will output
<a>tag instead of a
- When you need to disable a button, use
disabledproperty as it conveys this information correctly to assistive technologies like screen readers.
- Button component provides 3 size variants; small, medium and large. The large size should only be used for marketing purposes or on areas such as an empty space/content notice.
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.