Skip to main content

BETANow in public beta.Public betaBeta

日本語Español

ACD-008 Published

Details disclosure

Help that only some people need is tucked away in one place as a small "If you…" link.

FigmaThis part is included in our free, editable Figma file: 235 website UI patterns across 32 parts, 2 designs each Open in Figma Community ↗ (opens in a new tab)

Wireframe (desktop) | Details disclosure

Details disclosure UI design (desktop wireframe)

Wireframe (mobile) | Details disclosure

Details disclosure UI design (mobile wireframe)

What changes on mobile

  1. Wider explanation: The left line and spacing are slimmer so more words fit on each line of the opened text.
  2. Larger touch area: The small text link has a line height of at least 32px so it is easy to tap.

Before you choose this pattern | Details disclosure

Good fit

  • One or two pieces of help are needed by only some people
  • Showing that help all the time makes the field or text harder to read
  • Most people can carry on without reading it
  • Help under form fields, exceptions in a procedure, explaining a term

Poor fit

  • Several heading-and-text pairs in a row (the exclusive accordion works better)
  • Help that most people need (write it in the text without hiding it)

Why this wireframe works | Details disclosure

Only help for some people is tucked away

Help for everyone and help for a few side by side make the area around a field long. Only the help that some people need is tucked away, in one place.

The summary says who should open it

“More information” does not tell people whether it concerns them. The summary describes the situation directly, as in “If you do not know your company number”.

Small and quiet when closed

A large toggle button would stand out more than the field itself. When closed, it is just a small triangle and underlined text, so it does not interrupt the form.

A line sets the opened help apart

If opened help looks like the rest of the text, it is unclear where it starts and ends. A line on the left marks it as extra help.

Help everyone needs is not hidden

Hiding format rules that everyone needs leads to more mistakes. Help such as “13 digits” stays visible above the field; only exceptions are tucked away.

Common mistakes when building it

Hiding help everyone needs

Hiding format rules or warnings means some people fill in the field without opening it and get it wrong. Keep help that everyone needs visible near the field.

Many disclosures on one page

A row of disclosures leaves people unsure which to open, so they open them all. Keep it to one or two per page.

A summary that does not say what it is about

Summaries such as “Note” or “Other” give no clue until opened. Say who should open it and when.

Putting fields inside the disclosure

Fields hidden inside a closed disclosure get missed. Keep fields outside and tuck away only explanations.

Building a custom widget that keyboards cannot open

A div with click-to-open behaviour cannot be opened by keyboard and does not convey its state. details and summary work with keyboards and convey state by default.

Frequently asked questions

How is it different from other accordions?

Accordions such as the exclusive accordion open and close a series of heading-and-text pairs. The details disclosure tucks away one piece of help for some people, partway through a text or form.

Do details and summary work everywhere?

They work by default in current major browsers. The open state is conveyed automatically, so you do not need to add aria-expanded. The triangle can be restyled with CSS.

Is a tooltip better for field help?

Tooltips often appear only on hover and can be hard to open on mobile or by keyboard. For a few sentences, a details disclosure can be opened by anyone.

What if the help gets long?

If it runs beyond three or four sentences, put it on a separate page and link to it from the disclosure. Long reading inside the form pulls people out of filling it in.

Related pages

Share this pattern

Send this page to your team or your design partner.

Was this pattern useful?

Written by

Yuta Okano

ENVY DESIGN Inc.

CEO / Director / Designer

14 years in the web industry. Has worked on more than 500 web projects, from corporate and recruiting sites to e-commerce. Focuses on information architecture, direction and design, from planning websites to improving them. In recent years he has focused on AIO (AI optimization) and GEO, helping sites get cited by generative AI search such as ChatGPT, Perplexity and Google AI Overviews.

Review and revision history

  1. Published AvatarYuta Okano Pattern published