---
title: "Accordions"
url: "/help/buuk/accordions"
updated: "2026-10-22T11:13:32.704Z"
---
# Accordions

An accordion hides a stretch of content behind a summary label. Readers who want the depth expand it; everyone else keeps scrolling past.

## When to reach for one

- Optional detail that only some readers need — edge cases, troubleshooting, background history
- A FAQ-style page, where the question is the summary and the answer lives inside
- Anything optional. If a reader must have the information to finish the task, keep it in plain sight instead

## Open and closed on the public site

New accordions start closed, with the summary `Details` — make that label the question or heading a reader would scan for. Everything below it stays hidden until the reader expands it.

On the public site an accordion renders as a native `details` element, so expand and collapse works without JavaScript and keeps working for keyboard and screen-reader users.

## An example

This accordion holds a detail that interrupts flow when it is visible:

**What happens if a scheduled publish misses an approval?**

Scheduled publish still respects editorial approval. An unapproved page stays a draft when its slot arrives, and goes live once someone approves it. See [Review, versions, and scheduling](./review-versions-and-scheduling).

> [!NOTE]
> Content inside an accordion stays searchable and quotable — it is part of the page, not hidden from search or Ask AI.

## Related

- [Editor overview](./editor-overview)
- [Cards and columns](./cards-and-columns)
- [Callouts](./callouts)
- [Tables](./tables)