The decision that matters
Choose what belongs in the summary based on the user’s task. A title, status and short description may be enough for a document list, while an invoice needs the amount and due date. Keep expand controls clearly labeled and keyboard accessible. Do not hide errors, required inputs or the consequence of an action inside a collapsed area that users have no reason to open.
A practical scenario
A task card can show its title and status, with “Read description” opening the longer brief. The edit action remains available without forcing the reader through a large block of text. Once expanded, the description should use readable typography rather than inheriting the compressed spacing of the card’s metadata.
Before you ship
- Keep decision-critical information in the summary.
- Use explicit expand labels instead of an unexplained icon.
- Ensure expanded content follows a sensible keyboard order.
A useful next step
Test the list with both a two-line description and a long illustrated document. The summary should stay scannable while the expanded view remains comfortable to read. Disclosure is useful when it reduces clutter without making people hunt for essential facts.
Primary reference & further reading
This guide combines general engineering recommendations with an illustrative scenario. Provider behavior can change; check current documentation before applying it. Read our editorial approach.