github-a11y-scanner

Detect GitHub Accessibility Scanner presence and parse violation issues.

Updated Mar 10, 2026

Search Tags:#ci/cd #accessibility #a11y #github actions #copilot #scanner

Ready to run

npx skills add https://github.com/josephblais/jeeby-cms --skill github-a11y-scanner

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-a11y-scanner
Source: https://github.com/josephblais/jeeby-cms/tree/main/.github/skills/github-a11y-scanner
Command: npx skills add https://github.com/josephblais/jeeby-cms --skill github-a11y-scanner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps integrate the GitHub Accessibility Scanner into your development workflow, enabling automated detection and remediation of accessibility issues directly within your GitHub repositories.

Core Features & Use Cases

Scanner Detection: Identifies if the GitHub Accessibility Scanner is configured in a repository.
Issue Parsing: Extracts and interprets accessibility violations reported by the scanner.
Copilot Integration: Tracks the lifecycle of accessibility fixes proposed by GitHub Copilot.
Use Case: Automatically scan your web application's staging environment on every commit, identify accessibility violations, and track their resolution status through GitHub Issues and Copilot-generated Pull Requests.

Quick Start

Use the github-a11y-scanner skill to detect the presence of the GitHub Accessibility Scanner in the current repository.

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 web accessibility scanning within GitHub Actions?▼

Automating web accessibility scanning in GitHub Actions involves configuring workflow files to run the GitHub Accessibility Scanner on commits, enabling automated detection of violations and issue tracking within your repositories.

How does Copilot integration work for fixing accessibility violations?▼

Copilot integration for accessibility violations tracks the lifecycle of fixes proposed by GitHub Copilot through issue and PR lifecycles, monitoring the resolution status of scanner-created issues containing violation details and severity levels.

Can I track automated accessibility issue status through GitHub Issues and Pull Requests?▼

Tracking automated accessibility issue status through GitHub Issues and Pull Requests is supported by parsing scanner-created issues for violation details and correlating findings with Copilot-assigned fix status throughout the issue and PR lifecycles.

How do I detect if the GitHub Accessibility Scanner is configured in my repository?▼

Detecting the GitHub Accessibility Scanner configuration in a repository is done by inspecting workflow files to identify the presence of the scanner, allowing you to verify CI/CD accessibility checks are active.

What is the best way to correlate local accessibility scan results with GitHub scanner findings?▼

Correlating local accessibility scan results with GitHub scanner findings requires parsing scanner-created issues for violation details and severity, then matching those automated findings against local scans to track resolution status.