artifactExperience & interface

Accordion

An accordion is a set of labeled sections whose headings control whether associated content panels are expanded or collapsed.

Download Markdown (.md)

01What it means

An accordion groups content into vertically stacked sections with persistent headings and revealable panels. It may allow one or several panels to remain open. An accordion is a disclosure structure, not a substitute for a clear content hierarchy.[1][2]

02Why it matters

Accordions can reduce initial page length and help users scan meaningful headings, particularly on constrained screens. They also hide content and add interaction cost, so the labels and information architecture must support confident choices.

03When to use it

Use an accordion when sections are independently useful, headings are descriptive, and most users need only a subset. Show content directly when readers benefit from comparison, scanning all sections, searching within the page, or seeing important information without interaction.

04How it works

  1. Organize independent content sections under concise headings that predict their panels.
  2. Use a button within each heading and expose its expanded state and controlled panel.
  3. Decide whether multiple panels can stay open based on comparison and task needs.
  4. Make controls work with Enter and Space while preserving ordinary Tab navigation.
  5. Test deep links, printing, in-page search, no-script behavior, zoom, and long content.

05A practical example

Example

A billing help page groups questions under specific accordion headings. Several answers can remain open so customers can compare policies, while the cancellation deadline is displayed outside the accordion because it is essential for everyone.

06Where it breaks

Collapsed content has low discoverability and makes comparison harder. Large nested accordions create navigation overhead, and automatic collapse can make users lose their place. Search engines and in-page find behavior may vary by implementation.

Common mistakes

  • Using vague headings such as “Learn more.”
  • Hiding essential information simply to shorten the page.
  • Making only a small icon, rather than the heading button, interactive.
  • Collapsing another panel when users need to compare content.

07Sources

  1. Accordion PatternW3C Web Accessibility Initiative · Technical guidanceAccordion Pattern
  2. AccordionGOV.UK Design System · Institutional design systemAccordion
View saved topics

Start typing to search titles, definitions, categories, and frameworks.