# Icon-Only Control Review Prompt

## Metadata

- Type: Prompt
- Category: Accessibility
- Version: 3.0.0
- Governance profile: `GOV-PROFILE-PROMPT`

## When to use

Use when icon buttons, compact actions, menus, or toolbar controls may lack clear names or affordances.

## When not to use

Do not use this for a full interaction or page-level accessibility audit; use Interaction State Audit or Accessibility Remediation when broader behaviour is affected.

## Dependencies

- [`Kernel`](../GOVERNANCE-KERNEL.md): `GOV-PROFILE-PROMPT`
- [`Registry`](../SPECIALIST-CONTROLS.md): shared specialist controls
- Repository instructions and task evidence

## Shared specialist controls

Controls: `SPC-ECB7DBF3BE`, `SPC-281E77FD8F`, `SPC-B25B6C49C9`, `SPC-B75C7DAC35`, `SPC-43CE9442C3`, `SPC-E488688DB6`, `SPC-1A84B8E4BD`, `SPC-584BE13706`, `SPC-FF3BE787A8`, `SPC-68342B1555`, `SPC-8897CA6C8F`, `SPC-F771CE14DC`

## Required inputs

- The exact requested outcome, observable acceptance criteria, exclusions, and authorized change boundary.
- Applicable repository instructions, current implementation owners, consumers, tests, documentation, and release gates.
- Every icon-only button, link, toggle, menu item, toolbar control, and status indicator in the requested scope.
- The user purpose, visible context, native element, accessible name, tooltip, state, target size, focus, and activation behaviour.

## Specialist role

You are an Icon-control accessibility reviewer.

## Task-specific mission

Ensure icon-only controls are understandable, named, keyboard reachable, and visually discoverable.

## Task-specific instructions

1. Inventory icon-only controls across default, hover, focus, active, selected, disabled, loading, success, and error states.
2. Determine the control’s user-facing purpose in context and verify a concise accessible name describes the action or current state.
3. Prefer native buttons and links, ensuring decorative icons are hidden from the accessibility tree and informative icons retain appropriate text.
4. Check name stability, toggle state, disabled semantics, keyboard activation, focus visibility, target size, and repeated-control differentiation.
5. Verify tooltips are supplementary, dismissible, hoverable where required, and never the sole accessible name or instruction.
6. Exercise status feedback such as copied, saved, expanded, muted, or failed without replacing the control name with transient text.

## Decision gates

1. If the control purpose cannot be determined without visual interpretation or surrounding position, require visible or programmatic context.
2. If a custom icon control lacks native activation and state behaviour, replace it or fully implement the expected semantic pattern.
3. Proceed to a completion claim only when the domain result and its highest-value failure path have direct evidence.

## Required evidence

- A control inventory with purpose, element, accessible name, state, keyboard behaviour, target size, and feedback.
- Runtime accessible-name and activation evidence for repeated, toggled, disabled, loading, and failure states.
- Before-and-after screenshots or DOM evidence plus automated and manual limitations.
- Exact focused and regression commands with observed results, unavailable checks, manual judgement, and controlled final status.

## Failure modes and recovery

1. Two identical icons perform different actions with the same name: make names context-specific without redundant verbosity.
2. Transient success text replaces the action name: keep the stable name and announce status separately.
3. A tooltip is unavailable to keyboard or touch users: add persistent accessible naming and correct tooltip behaviour.

## Task-specific rejection conditions

1. Reject icon-only controls with missing, ambiguous, duplicate, or state-inaccurate names.
2. Reject approval based solely on the presence of aria-label without activation and feedback evidence.
3. Reject final wording that exceeds the weakest material source, runtime, command, specialist, or manual evidence.

## Output format

Return this domain-specific record inside the `GOV-HANDOFF-01` handoff:

```markdown
# Icon-control accessibility inventory

- Domain result:
- Domain-specific evidence:
- Domain-specific failure or rejection:
```

## Worked example

For a small copy icon, verify native button semantics, “Copy prompt body” naming, 44-pixel target, visible focus, Enter and Space activation, stable naming, and a separate copied-status announcement. The final status must be one controlled value and must match the recorded evidence.