accessibility-remediate

--- name: accessibility-remediate description: Fix the issues from an accessibility audit report in code, critical first, committing each fix and logging what was fixed, deferred or needs a design decision. Use when the user has an accessibility audit report and asks to start fixing its issues. Not for a design-stage check or feedback on one component; see /accessibility-checklist, /design-a11y-audit or /coaching-a11y. metadata: argument-hint: "[project] [--skip-checks]" workflow: accessibility phase: 4 artifact: 04-remediate.md stack-aware: true --- # Remediate Fix the accessibility issues found in "$ARGUMENTS". Apply remediation patterns to resolve WCAG violations, starting with critical barriers. **Arguments.** `$ARGUMENTS` may contain the project name and optional flags. Take the first token as `<project>` and treat `--skip-checks` as a flag; never include flags in file paths. All paths below use `<project>`. If `--skip-checks` is present, skip the prerequisite check and, **before writing any artifact**, append one line to `.singularskills/log.jsonl`: `{"ts":"<ISO timestamp>","skill":"accessibility-remediate","workflow":"accessibility","phase":4,"project":"<project>","event":"skipped","artifact":"04-remediate.md","note":"<reason or \"none given\">"}`. ## Prerequisites **Part of a workflow.** This skill is phase 4 (Remediate) of the WCAG-EM workflow (`accessibility`); cross-domain workflows run it too. First check `.singularskills/log.jsonl` for an open run for this project: a `run-started` line with `"project":"<project>"` and no later `run-finished` line for the same `workflow` and `project`. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the `workflow` skill with the workflow the user asked for, or `accessibility` when they named none, followed by `<project>`; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate. **Stack.** Before you build, test, lint, run or generate code, read the `Stack` section of the project's `AGENTS.md`, or of `CLAUDE.md` when `AGENTS.md` has none. Use its commands exactly as written, its `layout` for where files go and its `rules` as requirements. If it names a `profile`, also read the file `<profile>.md` in the `stacks` folder of this skill's bundled references for the full commands, layout and rules; the project's own keys win where both speak. If there is no `Stack` section, run the `singular-detect` skill, state what you inferred in one line, and offer to write the section with `singular-init`. Never assume a package manager, test runner or formatter the project did not declare. Run this skill's gate before writing: `sh <this skill's folder>/scripts/gate.sh <project> <project root>`, where `<project root>` is the folder that contains `.singularskills/` (use `.` when you are already there). If it exits non-zero, stop and tell the user what it printed, unless `--skip-checks` was given (see Arguments). On a refusal, before you stop, append this line to `.singularskills/log.jsonl` (create the folder and file if missing): `{"ts":"<ISO timestamp>","skill":"accessibility-remediate","workflow":"accessibility","phase":4,"project":"<project>","event":"refused","artifact":"04-remediate.md","note":"<what the gate printed>"}`. Once the gate has passed, or under `--skip-checks` once you have appended the `skipped` line, append this line before you start work: `{"ts":"<ISO timestamp>","skill":"accessibility-remediate","workflow":"accessibility","phase":4,"project":"<project>","event":"started","artifact":"04-remediate.md","note":""}`. Read `.singularskills/accessibility/<project>/03-report.md`. If this file does not exist, tell the user: > Phase 3 (Report) has not been completed for "<project>". Run `/accessibility-report <project>` first, or use `--skip-checks` to bypass. ## Process 1. **Read context files:** - Read `.singularskills/accessibility/<project>/03-report.md` for prioritized issues and remediation steps - Read `references/remediation-patterns.md` for common fix patterns 2. **Fix issues by priority:** - Start with Critical severity issues - Then Major, then Minor - For each issue: - Read the affected code - Apply the recommended fix from the report - Follow the remediation patterns in shared resources - Verify the fix doesn't introduce new issues - Commit each fix or group of related fixes 3. **Log remediation progress:** - Track each issue: fixed, deferred, or cannot fix (with reason) - Record commit hashes for each fix - Note any issues that require design changes or stakeholder decisions 4. **Write the artifact** to `.singularskills/accessibility/<project>/04-remediate.md` with sections: - **Fixes Applied** — each issue with what was changed and commit hash - **Deferred Issues** — issues not fixed and why - **Design Decisions Needed** — issues requiring stakeholder input - **New Considerations** — any new issues discovered during remediation ## References - `references/stacks/bun-react-ts.md` and `references/stacks/rust-gpui.md`: the shipped stack profiles ## Output The remediation log written to `.singularskills/accessibility/<project>/04-remediate.md`. Present a summary to the user highlighting: - Issues fixed vs. total - Commits made - Any deferred issues needing attention **Record the run.** After you have written the artifact, append this line to `.singularskills/log.jsonl` (the `started` line of Prerequisites, with `"event":"finished"`): `{"ts":"<ISO timestamp>","skill":"accessibility-remediate","workflow":"accessibility","phase":4,"project":"<project>","event":"finished","artifact":"04-remediate.md","note":""}`. Open the artifact with this frontmatter (`agent` is the agent you run in, or `unknown`; `gate` is `passed` when the gate ran clean and `skipped` under `--skip-checks`): ```yaml --- skill: accessibility-remediate workflow: accessibility phase: 4 project: <project> started: <ISO timestamp> finished: <ISO timestamp> agent: <the agent you run in, or "unknown"> gate: <passed|skipped> --- ``` End the artifact with `## Decisions` and `## Open questions`, in this shape: ```markdown ## Decisions - <what was chosen> — <why> — <what was rejected> ## Open questions - <what the next phase or a reviewer must settle> ```