github-a11y-scanner

Detect and track accessibility issues in GitHub workflows with delta caching.

Updated Aug 16, 2025
One-click install
npx skills add https://github.com/dodyg/blue-nile-pds --skill github-a11y-scanner-dodyg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-a11y-scanner
Source: https://github.com/dodyg/blue-nile-pds/tree/main/.agents/skills/github-a11y-scanner
Command: npx skills add https://github.com/dodyg/blue-nile-pds --skill github-a11y-scanner-dodyg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Integrate and orchestrate the GitHub Accessibility Scanner in CI to automatically detect accessibility issues on live pages, generate trackable issues, and optionally engage Copilot for fixes, providing delta-aware results across runs.

Core Features & Use Cases

  • Scans live URLs for accessibility barriers using axe-core in a headless browser
  • Creates trackable GitHub Issues for each finding with element, WCAG criterion, and remediation guidance
  • Optionally assigns issues to GitHub Copilot for AI-powered fix suggestions and PR creation
  • Caches results across runs to enable delta detection of new, fixed, or persistent findings
  • Supports authenticated scanning with login flows, SSO, and Playwright auth context
  • Attaches screenshots to filed issues when enabled

Quick Start

Add the github/a11y-scanner action to your workflow and configure it with your repository, token, and cache key to start scanning accessibility issues.

Frequently Asked Questions about github-a11y-scanner

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

FAQPage Schema
How do I automate accessibility testing in GitHub CI workflows?

Automate accessibility testing in GitHub CI by adding the scanner action to your workflow, configuring it with live URLs, a repository token, and a cache key to detect axe-core violations mapped to WCAG criteria. It runs headless browser scans on every run and outputs structured findings.

Can I track accessibility issues found by axe-core as GitHub Issues?

Yes, the scanner automatically creates trackable GitHub Issues for each accessibility finding, including the violating element, the specific WCAG criterion, and remediation guidance directly in the issue body. You can optionally attach screenshots of the violations.

Does the GitHub accessibility scanner support authenticated pages and SSO?

Yes, it supports authenticated scanning using login flows, SSO, and Playwright auth contexts. You configure these by passing the login_url, username, password, and auth_context inputs directly in your GitHub workflow configuration.

How do I prevent duplicate accessibility findings across multiple CI runs?

You prevent duplicate findings by using the cache_key input to enable delta caching. This stores previous results to detect new, fixed, or persistent accessibility violations across runs, ensuring you only track relevant changes.

Can GitHub Copilot automatically fix accessibility issues detected in CI?

Yes, you can optionally assign the generated GitHub Issues to GitHub Copilot. Copilot then provides AI-powered fix suggestions and can automatically create pull requests to remediate the detected WCAG violations.