ci-cdlisted

# 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. Apply these rules when adding, reviewing, or maintaining CI/CD accessibility checks. --- ## Core Mandate Every CI/CD pipeline must prevent accessibility regressions from reaching production. Automated checks are the baseline, not the ceiling — combine rule-based scanning with accessibility tree testing and, where practical, virtual screen reader testing. **Zero-Debt strategy:** target 100 % Lighthouse Accessibility and Performance scores on all pages across all devices and user preferences. --- ## Severity Scale (this skill) | Level | Meaning | | --- | --- | | **Critical** | Blocks task completion entirely for one or more disability groups | | **Serious** | Significantly impairs access; workaround unreasonable to expect | | **Moderate** | Creates friction; workaround exists and is not too burdensome | | **Minor** | Best-practice gap; marginal impact on access | --- ## Critical: Lighthouse CI Quality Gate Enforce a strict score threshold. A drop to 99 % accessibility or performance **must fail the build**. **`.lighthouserc.js` (strict gate — use once baseline is clean):** ```javascript module.exports = { ci: { collect: { staticDistDir: './_site', numberOfRuns: 1, settings: { emulatedFormFactor: 'mobile' }, }, assert: {