Accessibility Gate
Gate UI work against WCAG 2.2 AA and semantic correctness. Treat ARIA as a sharp tool, justify every usage, and map issues to explicit success criteria when possible.
Workflow
- Model keyboard interaction, focus order, and focus visibility.
- Inspect semantic structure, names, roles, values, and announcement behavior.
- Only recommend ARIA when semantic HTML cannot express the behavior, and list misuse risks when ARIA is necessary.
- Return findings, WCAG mapping, remediations, tests, and a skill log.
Inputs
- Artifact under review
- Primary user flows
- Target conformance level if not WCAG 2.2 AA
Deliverables
- JSON with
findings, wcag_map, remediations, tests, and skill_log
- Severity for each finding
- Explicit keyboard and screen-reader verification plan
Quality Gates
- Every issue is tied to a behavior, criterion, or stated assumption.
- No blanket ARIA recommendations.
- Test plan covers keyboard, focus, and assistive technology impact.
- Remediation steps are concrete enough to implement.
Prompt Scaffold
SYSTEM
You are an accessibility gatekeeper.
USER
Inputs:
- Artifact under review
- Primary user flows
- Target conformance level if not WCAG 2.2 AA
Task:
Audit the artifact, map issues to WCAG where possible, and return a JSON remediation plan.
Output requirements:
- JSON with `findings`, `wcag_map`, `remediations`, `tests`, and `skill_log`
- Severity for each finding
- Explicit keyboard and screen-reader verification plan
1---2name: accessibility-gate3description: Run a testable accessibility review with WCAG mapping, keyboard and focus analysis, and semantic or ARIA remediation guidance. Use when Codex needs to audit a page or component and produce a formal accessibility gate instead of generic UX feedback.4---56# Accessibility Gate78Gate UI work against WCAG 2.2 AA and semantic correctness. Treat ARIA as a sharp tool, justify every usage, and map issues to explicit success criteria when possible.910## Workflow111. Model keyboard interaction, focus order, and focus visibility.122. Inspect semantic structure, names, roles, values, and announcement behavior.133. Only recommend ARIA when semantic HTML cannot express the behavior, and list misuse risks when ARIA is necessary.144. Return findings, WCAG mapping, remediations, tests, and a skill log.1516## Inputs17- Artifact under review18- Primary user flows19- Target conformance level if not WCAG 2.2 AA2021## Deliverables22- JSON with `findings`, `wcag_map`, `remediations`, `tests`, and `skill_log`23- Severity for each finding24- Explicit keyboard and screen-reader verification plan2526## Quality Gates27- Every issue is tied to a behavior, criterion, or stated assumption.28- No blanket ARIA recommendations.29- Test plan covers keyboard, focus, and assistive technology impact.30- Remediation steps are concrete enough to implement.3132## Prompt Scaffold33```text34SYSTEM35You are an accessibility gatekeeper.3637USER38Inputs:39- Artifact under review40- Primary user flows41- Target conformance level if not WCAG 2.2 AA4243Task:44Audit the artifact, map issues to WCAG where possible, and return a JSON remediation plan.4546Output requirements:47- JSON with `findings`, `wcag_map`, `remediations`, `tests`, and `skill_log`48- Severity for each finding49- Explicit keyboard and screen-reader verification plan50```
henryhawke