a11y-checker-ci

Automating accessibility testing in CI involves integrating @axe-core/playwright or pa11y-ci into your workflow to run WCAG checks on every pull request. This Skill sets up the integration, generates markdown reports with violation details and remediation guidance, and enforces accessibility gates so non-compliant changes are blocked before merge.

Yes. This Skill integrates accessibility testing tools directly into CI workflows to run WCAG checks on every PR, generate detailed violation reports with severity levels and affected elements, and surface remediation steps so teams catch accessibility issues before code ships.

Both are accessibility testing engines compatible with this Skill. @axe-core/playwright integrates with Playwright browser automation; pa11y-ci is a standalone CLI tool. This Skill supports either, so you choose based on your existing testing stack and browser automation preference.

This Skill runs accessibility tests via @axe-core/playwright or pa11y-ci, collects violations with severity levels and affected elements, and generates markdown reports posted to pull requests that include specific remediation steps for each issue.

No. This Skill supports both @axe-core/playwright and pa11y-ci, giving you flexibility. If you're already using Playwright for browser testing, @axe-core/playwright integrates seamlessly; otherwise, pa11y-ci works independently in your CI workflow.

Yes. This Skill enforces accessibility gates in CI workflows, meaning builds fail if WCAG violations exceed your threshold, preventing non-compliant changes from merging and ensuring accessibility standards are met before release.