# Reveal optional detail without hiding the answer

ID: cmp-disclosure. Sources: [S19](https://design-system.service.gov.uk/components/details/), [S20](https://www.w3.org/WAI/ARIA/apg/practices/read-me-first/), [S28](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/popover).

Teach essential explanation versus optional depth. Use disclosures for exceptional conditions, extra specifications, or annotations. Keep the core decision understandable without opening everything.

Application A: visible service scope includes optional technical details. Application B: an annotated object offers clearly labeled explanatory notes with in-flow fallback.

Counterexample: primary offer, important price qualifications, and all proof are hidden in accordions.

Mobile: preserve labels, comfortable interaction, focus, and expanded content order. Reuse tested behavior or appropriate native elements.

Storyboard: distinguish visible/revealed content and fallback. Review: inspect closed/open states and execute keyboard/touch paths. An initial screenshot cannot establish disclosure functionality.

## Authority and use

This is an original design-teaching hypothesis. It is advisory and does not change factual, accessibility, or functional requirements. Adapt it to verified business evidence and inspect the current render before accepting an outcome. The applications above are contrasting examples, not copyable site presets.