github-a11y-scanner

Detect GitHub Accessibility Scanner presence and parse scanner-created issues.

387|42|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/Community-Access/accessibility-agents --skill github-a11y-scanner-community-access
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-a11y-scanner
Source: https://github.com/Community-Access/accessibility-agents/tree/main/.gemini/extensions/a11y-agents/skills/github-a11y-scanner
Command: npx skills add https://github.com/Community-Access/accessibility-agents --skill github-a11y-scanner-community-access

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps agents integrate with and understand the GitHub Accessibility Scanner Action, enabling automated detection, parsing, and tracking of accessibility issues within GitHub repositories.

Core Features & Use Cases

  • Scanner Detection: Identifies if the GitHub Accessibility Scanner is configured in a repository.
  • Issue Parsing: Extracts key information from scanner-generated GitHub Issues, including violation details, WCAG criteria, and severity.
  • Copilot Fix Tracking: Monitors the lifecycle of accessibility fixes proposed by GitHub Copilot.
  • Use Case: An agent can use this skill to automatically check a repository for accessibility issues using the GitHub Scanner, report on any findings, and track if Copilot is assigned to fix them.

Quick Start

Use the github-a11y-scanner skill to check for the presence of the accessibility scanner action in the repository's workflows.

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 GitHub accessibility scanning in CI/CD pipelines?

Automate GitHub accessibility scanning by integrating the GitHub Accessibility Scanner Action into your CI/CD pipelines to detect violations, parse issues, and track WCAG AA compliance. The agent identifies scanner presence in workflow files and manages the issue lifecycle automatically.

What is axe-core rule mapping for WCAG AA compliance checks?

Axe-core rule mapping correlates scanner-detected violations with specific WCAG AA criteria. The agent parses GitHub issue payloads generated by the scanner to extract violation details, severity, and the corresponding WCAG criteria mapped by axe-core rules.

Can I track Copilot-assigned accessibility fixes in GitHub Issues?

Yes, you can track Copilot-assigned accessibility fixes by monitoring the lifecycle of GitHub Issues. The agent parses scanner-created issues and tracks the fix status of accessibility violations proposed by GitHub Copilot within your repository.

Does the GitHub Accessibility Scanner Action detect existing workflow configurations?

The scanner detection feature identifies if the GitHub Accessibility Scanner Action is already configured in a repository's workflow files. It checks for scanner presence so agents can report findings and determine if automated WCAG AA compliance checks are active.

What's the best way to parse GitHub issue payloads for accessibility violations?

The best way to parse GitHub issue payloads for accessibility violations is using an agent that extracts violation details, WCAG criteria, and severity from scanner-generated issues. This correlates findings with local scans and manages the accessibility issue lifecycle.