ci-cd

Enforce Lighthouse and axe-core accessibility checks in CI pipelines.

39|2|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/mgifford/accessibility-skills --skill ci-cd-mgifford
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-cd
Source: https://github.com/mgifford/accessibility-skills/tree/main/skills/ci-cd
Command: npx skills add https://github.com/mgifford/accessibility-skills --skill ci-cd-mgifford

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure accessibility regressions are caught before code reaches production by integrating checks into CI/CD pipelines, providing deterministic gates and clear reporting.

Core Features & Use Cases

  • Lighthouse & axe-core checks: Enforces accessibility and performance thresholds across builds and PRs.
  • Structured reporting: Generates actionable results that feed into dashboards and issue tracking.
  • Use Case: When a new feature is introduced, the CI workflow blocks merges that cause accessibility regressions or low Lighthouse scores.

Quick Start

Run the configured CI workflow in your repository and ensure failing builds block deployment until issues are resolved.

Frequently Asked Questions about ci-cd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate accessibility testing in CI/CD pipelines?

Automate accessibility testing in CI/CD by configuring Lighthouse CI, Playwright tests, and GitHub Actions workflows. This enforces accessibility thresholds and runs scheduled scans to catch regressions before code reaches production.

Can I use axe-core and Lighthouse to block PR merges for accessibility regressions?

Yes, you can block PR merges by enforcing axe-core and Lighthouse checks in GitHub Actions. The CI workflow enforces accessibility and performance thresholds, blocking deployments that cause regressions or low scores.

How do I generate structured reporting for accessibility tests in CI?

Generate structured reporting for accessibility tests by running configured CI workflows with Lighthouse and axe-core. This produces actionable results that feed directly into dashboards and issue tracking systems.

Does this accessibility governance approach work for both mobile and desktop builds?

Yes, this accessibility governance approach applies Lighthouse and axe-core checks across both mobile and desktop builds. It enforces thresholds and runs scheduled scans to prevent regressions on all device types.

What do I need to configure to enforce accessibility gates in GitHub Actions?

To enforce accessibility gates in GitHub Actions, you need to configure Lighthouse CI, Playwright tests, and workflow files. This setup enforces thresholds and runs scheduled scans to block regressions before deployment.