Version 3.0.0

Close button

The close button is used inside of other components, like a toast or an action bar, for closing or dismissing its parent component.

Key example of a close button. A mouse cursor hovers over a close button that is within a positive variant of a toast that is green with a checkmark icon. Toast text, Copied to clipboard.

Anatomy#


Diagram illustrating through labels the component parts of a close button including the cross UI icon.

Options#


Key example of four close buttons in their default and hover states showing the size options available including small, medium, large, and extra-large. The hover state has a visible circle showing the button’s bounds.

Size#

Close buttons come in four different sizes: small, medium, large, and extra-large. The medium size is the default and most frequently used option. Use the other sizes sparingly; they should be used to create a hierarchy of importance within the page.

Key example of two medium-sized close buttons in their default and hover states showing the icon sizes in regular and large.

Icon size#

The icon inside of the close button comes in two options: regular and large. These scale up and down for each close button size. This is a cross UI icon, not a workflow icon or the letter “x.”

Key example of static color white and black close buttons in the medium size.

Static color#

Use the static color option when a close button needs to be placed on top of a color background or visual. Static color close buttons are available in black or white, regardless of color theme.

Use static black on light color or image backgrounds, and static white on dark color or image backgrounds, regardless of color theme. Make sure that the background and the close button color meet the minimum color contrast ratio.

Key example of a single disabled close button.

Disabled#

A close button in a disabled state shows that an action exists, but is not available in that circumstance. This state can be used to maintain layout continuity and to communicate that an action may become available later.

Table of options#

From the design point of view, each component has a number of options. These options and their names are platform agnostic, and each implementation should adapt these to fit into their framework.

PropertyValuesDefault Value
is disabled
yes / no
no
static color
none / white / black
none
icon size
regular / large
regular
size
small / medium/ large / extra-large
medium

Behaviors#


Key example of 2 close buttons in their keyboard focus states, default with a blue ring and static color white with a white ring.

Keyboard focus#

A close button can be navigated using a keyboard. The keyboard focus state takes the close button’s visual hover state and adds a ring to the button in focus.

Usage guidelines#


Don’t use close buttons for delete actions#

A close button is only for dismissing or closing its parent component, not for taking a destructive action (like deleting a file). Use an action button instead.

Key example showing correct usage of action button for deleting an asset. Action button with trash can icon and label, Delete. Two asset cards, one selected.
Key example showing incorrect usage of close button for deleting an asset. Two asset cards, one on hover with a close button appearing in its top right corner.

Keyboard interactions#


KeyInteraction
Space or EnterExecutes the button (closes or dismisses the parent component). Focus moves to the target or back to the caller.

Changelog#


DateNumberNotes
Apr 06, 20223.0.0
  • Updated all colors to 6.0.0
Feb 09, 20222.0.0
  • Renamed "clear button" to "close button"
  • Added size option
  • Added icon size option
  • Added static color option
Feb 28, 20201.0.0
  • This component has been added to the website

Design checklist#


All interactive states

Includes all interactive states that are applicable (hover, down, focus, keyboard focus, disabled).

All color themes

Works properly across all four color themes (lightest, light, dark, darkest).

All platform scales

Includes a desktop scale (UWP, macOS, web desktop) and a mobile scale (iOS, Android, web mobile).

Accessible use of color

Color is not used as the only visual means of conveying information (WCAG 2.0 1.4.1).

N/A

Accessible contrast for text

Text has a contrast ratio of at least 4.5:1 for small text and at least 3:1 for large text (WCAG 2.0 1.4.3).

Accessible contrast for UI components

Visual information required to identify components and states (except inactive components) has a contrast ratio of at least 3:1 (WCAG 2.1 1.4.11).

Content design

UI language and information design considerations have been incorporated into component design.

Defined options

Includes relevant options (variant, style, size, orientation, optional iconography, decorations, selection, error state, etc.)

Defined behaviors

Includes guidelines for keyboard focus, layout (wrapping, truncation, overflow), animation, interactions, etc.

Usage guidelines

Includes a list of dos and don'ts that highlight best practices and common mistakes.

N/A

Writing guidelines

Includes content standards or usage guidelines for how to write or format in-product content for the component.

Internationalization guidelines

Works properly across various locales and includes guidelines for bi-directionality (RTL).

Keyboard interactions

Follows WCAG 2.0 standards for keyboard accessibility guidelines and includes a description of the keyboard interactions.

Design tokens

All design attributes (color, typography, layout, animation, etc.) are available as design tokens.

UI kit

Includes a downloadable XD file that shows multiple options, states, color themes, and platform scales.

Generated UI kit

Includes a downloadable XD file, generated by code using design tokens defined in Spectrum DNA, and shows multiple options, states, color themes, and platform scales.

In Spectrum for Adobe XD plugin

Component is included in the Spectrum for Adobe XD plugin.