ci-cd

# CI/CD Accessibility Skill > **Canonical source**: `examples/CI_CD_ACCESSIBILITY_BEST_PRACTICES.md` in `mgifford/ACCESSIBILITY.md` > This skill is derived from that file. When in doubt, the example is authoritative. > The canonical guide states synchronization with this skill is **not automatic** > — re-check this file against canonical periodically. Apply these rules when adding, reviewing, or maintaining CI/CD accessibility checks. For guidance on when to use AI skills versus automated scanners during audits, see `AI_AUDIT_GUIDE.md` in this repository. --- ## Core Mandate CI can prevent known accessibility regressions, preserve tested semantics, and produce evidence for human review. **It cannot establish WCAG conformance by itself.** Automated rules, scores, snapshots, and AI output are inputs to an accessibility evaluation, not substitutes for one. This guide targets WCAG 2.2 AA for in-scope content — that target is not itself a conformance claim. A confirmed AAA-level finding under this AA target is `obligation: aspirational` by default (a visible, non-blocking stretch goal), not `advisory`, unless a project explicitly elevates that specific criterion to `required`. Principles: test complete user tasks and relevant states, not only page loads; run fast deterministic checks locally and repeat in CI; block known regressions using explicit reviewable rules; keep accessibility, performance, security, and functional signals distinct; test the final rendered/sanitized/...