Skip to content
Back to skills

Apple Hig Disclosure Controls

ASecurity

Use when designing, reviewing, or adapting progressive disclosure, expansion labels, and collapsed or expanded state.

  • 7 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 26, 2026
ai-agentsgo

Works with

  • cli

Security analysis

A100/100

Scanned October 26, 2026

npx -y skills add AyushRajSinghParihar/apple-human-interface-skills --skill apple-hig-disclosure-controls --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Apple Hig Disclosure Controls?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Apple Hig Disclosure Controls
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ayushrajsinghparihar-apple-hig-disclosure-controls/badge)](https://www.skillsdirectory.com/skills/ayushrajsinghparihar-apple-hig-disclosure-controls)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: apple-hig-disclosure-controls
description: Use when designing, reviewing, or adapting progressive disclosure, expansion labels, and collapsed or expanded state.
---

# Reveal the optional without hiding the essential

Read [the disclosure guide](../../references/disclosure-controls.md). This workflow applies the source; it does not invent support for custom controls.

Inspect the content hierarchy, platform, evidence artifact, and create/review/adapt goal. Separate common actions from advanced/occasional detail. Record which view/control owns each expansion and whether hidden contents include validation errors or essential next steps.

Keep common information visible. Use a labelled triangle for revealing details or hierarchy children, with inward-leading collapsed and downward expanded direction. Use the distinct disclosure button for functionality associated with a particular control; its down/up directions and one-per-view constraint must not be generalized to every disclosure triangle. Place the trigger beside its controlled content and expose state/name in the accessibility structure. The guide identifies platform disclosure behavior on iOS/iPadOS/visionOS and marks tvOS/watchOS unsupported; adapt the information architecture there rather than copying unsupported chrome.

Implement the expansion, specify the trigger/content/state relationship, or review exact hidden-task failures. Preserve entered values and task continuity when a section collapses; that is an application decision to verify, not an asserted system guarantee.

**Worked transformation:** Before: a video export view hides Format and Destination under an unlabeled triangle alongside three separate down/up expansion buttons. Decision: necessary choices are hidden and trigger meanings conflict. After: keep Format/Destination visible, put rare encoder parameters under `Advanced Encoding`, and use a single nearby control-specific expansion only if needed.

Deliver the modified hierarchy and initial/expanded states. Verify the label predicts revealed content, keyboard activation changes exposed state, resizing does not clip content, and collapse preserves intended values. Fail for hidden essential actions, ambiguous ownership, or a state announced opposite to its visual direction. Native accessibility execution requires a suitable runtime.

Use [outline-views](../apple-hig-outline-views/SKILL.md) for tree traversal or [buttons](../../../apple-hig-menus-and-actions/.topics/apple-hig-buttons/SKILL.md) for action semantics.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.