№ 005 / Opening sequence
Reveal the right amount
Clear hierarchy reduces the amount someone must interpret at once.
Try it. Nothing is sent.
IN EVERYDAY WORDS
Show the main decision first. Let the person open extra detail when they need it.
The look
A simple first choice, with a clearly labeled control for optional details below it.
Say this to a designer
Use progressive disclosure on this form. Keep the main question visible and place optional detail behind a clearly labeled expand button. Open that detail directly beneath the button, keep entered answers when it closes, and make the main action stay obvious. Required information and errors must remain visible.
Direct the motion
These are starting points, not fixed rules. Match the timing to the content and the person using it.
- trigger
- The visitor activates the optional-detail button.
- entrance
- Reveal the supporting fields from beneath their own control so the relationship is clear.
- path
- Expand downward within the form. Let nearby content move only as much as necessary.
- timing
- If adding movement, begin with a 180–240 millisecond expansion. The example uses a direct reveal for easy comparison.
- easing
- Ease out for opening; keep closing equally clear and slightly quicker if needed.
- hold
- Keep the expanded form completely still while someone reads or types.
- exit
- Collapse only when requested. Preserve input and return focus to the disclosure button if focus was inside.
The vocabulary
- Progressive disclosure
- Showing the information needed now, with more detail available when requested.
- Visual hierarchy
- Using size, placement, spacing, and contrast to show what matters first.
- Accordion
- A labeled section that can expand to reveal content and collapse to hide it.
Make it fit your project
Good places to use it: intake form, optional detail, service selector, settings.
A form or panel has useful details that are not needed for the first decision.
Watch for: Do not hide pricing, material conditions, errors or required information.
When motion is off: Expand and collapse directly without sliding.
Implementation and accessibility
- Identify the primary decision and make it the clear first control.
- Move optional detail behind an explicit disclosure button.
- Keep entered information when the section closes.
- Use a short expansion that reveals the relationship between control and content.
- Confirm the next action and test the complete keyboard path.
- Use a button with aria-expanded and aria-controls.
- Keep hidden fields out of the tab order.
- Use persistent labels, not placeholder-only instructions.
- Avoid animating a large page layout on every frame.
- Reserve a clear final layout and prevent horizontal overflow.
Give it to your AI
Download the working source and example assets. Match this reference number in the included catalog to its renderer.
Replace [ELEMENT] with the part of your project you want to change. The prompt includes the design brief, motion direction, definitions, and implementation steps.
Read the full prompt
Use AI Acceleration Design Ref #005 (Reveal the right amount, version 2) on [ELEMENT] in my existing project. Permanent reference: https://aiacceleration.ai/designrefs/005. This local brief contains the full definition. Inspect my existing stack, component, design tokens and interaction before editing. Goal: Clear hierarchy reduces the amount someone must interpret at once. DESIGN REF #005 · Reveal the right amount In everyday words: Show the main decision first. Let the person open extra detail when they need it. The look: A simple first choice, with a clearly labeled control for optional details below it. Say this to a designer: Use progressive disclosure on this form. Keep the main question visible and place optional detail behind a clearly labeled expand button. Open that detail directly beneath the button, keep entered answers when it closes, and make the main action stay obvious. Required information and errors must remain visible. Motion direction (starting points to adapt): Trigger: The visitor activates the optional-detail button. Entrance: Reveal the supporting fields from beneath their own control so the relationship is clear. Path: Expand downward within the form. Let nearby content move only as much as necessary. Timing: If adding movement, begin with a 180–240 millisecond expansion. The example uses a direct reveal for easy comparison. Easing: Ease out for opening; keep closing equally clear and slightly quicker if needed. Hold: Keep the expanded form completely still while someone reads or types. Exit: Collapse only when requested. Preserve input and return focus to the disclosure button if focus was inside. Design vocabulary: Progressive disclosure: Showing the information needed now, with more detail available when requested. Visual hierarchy: Using size, placement, spacing, and contrast to show what matters first. Accordion: A labeled section that can expand to reveal content and collapse to hide it. Reduced motion: Expand and collapse directly without sliding. Implement: 1. Identify the primary decision and make it the clear first control. 2. Move optional detail behind an explicit disclosure button. 3. Keep entered information when the section closes. 4. Use a short expansion that reveals the relationship between control and content. 5. Confirm the next action and test the complete keyboard path. Adapt the reference to my branding and content. Preserve existing functionality and semantic HTML. Reduced motion: Expand and collapse directly without sliding. Accessibility: Use a button with aria-expanded and aria-controls. Keep hidden fields out of the tab order. Use persistent labels, not placeholder-only instructions. Performance: Avoid animating a large page layout on every frame. Reserve a clear final layout and prevent horizontal overflow. Avoid: Do not hide pricing, material conditions, errors or required information. Show me the working result, verify keyboard, mobile, loading/error and reduced-motion behavior, and explain any tradeoff. Do not publish or change unrelated elements.
Permanent reference #005 · version 2. Pairs with #003, #008.