scanner-bridge

To integrate GitHub Accessibility Scanner results with agent issue tracking, you can use a bridge to fetch, normalize, and deduplicate CI findings against local scans. This requires GitHub API access to query issues and PRs for audit reporting.

Deduplication works by fetching scanner issues from CI and standardizing the findings using axe-core rule IDs and WCAG criteria. The normalized findings are then merged with your local scan data to eliminate redundant accessibility violations.

Yes, you can track Copilot fix status for scanner-identified accessibility violations. The bridge monitors whether Copilot has proposed or implemented fixes for issues found by the GitHub Accessibility Scanner in your CI pipeline.

Yes, GitHub API access is required to query issues and PRs. You also need knowledge of axe-core rule IDs and WCAG criteria to properly normalize and standardize the accessibility findings fetched from the scanner.

The best way to automate audit reporting from GitHub Actions is to detect the scanner configuration in your repository and bridge the CI data to your agent ecosystem. This normalizes findings and tracks Copilot fix proposals automatically.