Skip to main contentCarbon Design System

Accordion

An accordion is a vertically stacked list of headers that reveal or hide associated sections of content.

Live demo


    This live demo contains only a preview of functionality and styles available for this component. View the full demo on Storybook for additional information such as its version, controls, and API documentation.

    Accessibility testing status

    For every latest release, Carbon runs tests on all components to meet the accessibility requirements. These different statuses report the work that Carbon has done in the back end. These tests appear only when the components are stable.

    Overview

    The accordion component delivers large amounts of content in a small space through progressive disclosure. The header title give the user a high level overview of the content allowing the user to decide which sections to read.

    Accordions can make information processing and discovering more effective. However, it does hide content from users and it’s important to account for a user not noticing or reading all of the included content. If a user is likely to read all of the content then don’t use an accordion as it adds the burden of an extra click; instead use a full scrolling page with normal headers.

    When to use

    • To organize related information.
    • To shorten pages and reduce scrolling when content is not crucial to read in full.
    • When space is at a premium and long content cannot be displayed all at once, like on a mobile interface or in a side panel.

    Formatting

    Anatomy

    accordion anatomy
    1. Header: contains the section title and is control for revealing the panel.
    2. Icon: indicates if the panel is open or closed.
    3. Panel: the section of content associated with an accordion header.

    Alignment

    By default the chevron icon is placed on the end side of the header. This allows for the title on the start side to align with other type elements in the layout, which is the preferred alignment scenario.

    However, in some rare scenarios, the accordion may be modified to place the icon in start front of the title to function more like a tree. Most instances should use the default end alignment, especially for any pure content or documentation purposes. Icon placement in accordions should be consistent throughout your page and should not alternate.

    Do use the default end icon alignment to keep accordion text aligned with other content on the page.

    In most cases, use the default end icon alignment to keep accordion text aligned with other content on the page.

    Do place icons on the start side for tree like functionality.

    In rare cases, you can place icons on the start side for tree like functionality.

    Placement

    Accordions can be placed with main page content or placed inside of a container such as a side panel or tile.

    accordion placement

    Grid placement

    When placing an accordion on the 2x Grid with its default alignment, the indented title and content align to the grid columns, and the top and bottom borders hang into the gutter. However, the accordion can be modified to have a flush alignment where the titles and content are instead flush aligned with the top and bottom borders having 0px padding.

    accordion grid placement

    Content

    Main elements

    Title

    • The title should be as brief as possible while still being clear and descriptive.
    • Each title should be wrapped in a role heading (h1-h6) that is appropriate for the information architecture of the page.

    Body copy

    • Content inside of a section may be split into paragraphs and include sub-headers if needed.

    Scrolling content

    When the accordion content is longer than the viewport the whole accordion should vertically scroll. Content should not scroll inside of an individual panel. Content should never scroll horizontally in an accordion.

    Behaviors

    States

    The accordion component has two main states: collapsed and expanded. The chevron icon at the end of the accordion indicates which state the accordion is in. The chevron points down to indicate collapsed and up to indicate expanded.

    Accordions begin by default in the collapsed state with all content panels closed. Starting in a collapsed state gives the user a high level overview of the available information.

    accordion states

    A user can then independently expand each section of the accordion allowing for multiple sections to be open at once.

    multiple sections expanded

    In addition to the collapsed and expanded states, accordions also have interactive states for focus, hover, and disabled. See the style tab for more details.

    accordion interactives states

    Interactions

    Mouse

    Users can trigger a state change by clicking on the chevron or clicking anywhere in the header area.

    accordion click targets

    Keyboard

    Users can navigate between accordion headers by pressing Tab or Shift-Tab. Users can trigger a state change by pressing Enter or Space while the header area has focus. For additional keyboard interactions, see the accessibility tab.

    Modifiers

    Flush alignment

    Use flush alignment when designing within smaller spaces on a page such as side panels or sidebars to achieve better text alignment with other content. Flush alignment is also used to help avoid converging rule lines between components that are close to each other on a page.

    accordion flush alignment

    Flush alignment places the row title and chevron icons with 0px padding, keeping them flush to the rule dividers. For hover and focus interactive states, the left and right padding receives an additional 16px padding.

    accordion flush alignment spec

    The following components are additional ways to organize content. Consider the type and length of content you are working with when choosing a content container. Longer form content may benefit from tabs or a content switcher while very short content might do better in a structured list.

    References

    Feedback

    Help us improve this component by providing feedback, asking questions, and leaving any other comments on GitHub.