skills.rest
Community-Access
Community-AccessOFFICIAL
Explore all skills by this author →
GitHub

Accessibility Tracker

Monitor accessibility issues and generate WCAG 2.2 reports for GitHub repositories.

387|42|Updated Feb 21, 2026
Search Tags:#vscode#accessibility#github#reporting#wcag#tracking
One-click install
npx skills add https://github.com/Community-Access/accessibility-agents --skill accessibility-tracker
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Accessibility Tracker
Source: https://github.com/Community-Access/accessibility-agents/tree/main/.gemini/extensions/a11y-agents/skills/insiders-a11y-tracker
Command: npx skills add https://github.com/Community-Access/accessibility-agents --skill accessibility-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users stay on top of accessibility improvements across VS Code and any configured repositories, preventing accessibility regressions and ensuring inclusive development practices.

Core Features & Use Cases

  • Proactive Monitoring: Automatically tracks accessibility issues in specified GitHub repositories.
  • Categorized Summaries: Provides categorized lists of accessibility updates (Screen Reader, Keyboard Navigation, Visual/Contrast, etc.).
  • Deep Dive Analysis: Offers detailed information on specific accessibility changes, including user impact and code modifications.
  • Workspace Reporting: Generates comprehensive monthly or weekly reports for offline review and team sharing.
  • WCAG Cross-referencing: Maps accessibility findings to relevant WCAG 2.2 success criteria.

Quick Start

Show me the latest accessibility updates for the microsoft/vscode repository.

Frequently Asked Questions about Accessibility Tracker

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

FAQPage Schema
How do I track accessibility improvements and regressions in GitHub repositories?▼

To track accessibility improvements and regressions in GitHub repositories, you can monitor specified repos to categorize issues by type, cross-reference WCAG criteria, and generate detailed workspace reports on a11y progress.

Does VS Code accessibility monitoring map issues to specific WCAG success criteria?▼

Yes, VS Code accessibility monitoring maps findings to relevant WCAG 2.2 success criteria. It categorizes issues by type like Screen Reader and Keyboard Navigation, providing comprehensive insights into a11y progress.

How do I generate weekly or monthly accessibility reports for my development team?▼

You can generate weekly or monthly accessibility reports for your team by integrating with GitHub issue tracking. This produces categorized summaries of a11y updates for offline review and team sharing.

Can I get detailed analysis on specific accessibility changes and their user impact?▼

Yes, you can get detailed analysis on specific accessibility changes and their user impact. It offers deep dive insights into code modifications, categorizing updates to prevent accessibility regressions across configured repositories.

What types of accessibility issues can I monitor across my repositories?▼

You can monitor various types of accessibility issues across your repositories, providing categorized lists of updates including Screen Reader, Keyboard Navigation, and Visual/Contrast improvements to ensure inclusive development practices.

Related Skills

Explore More Software Engineering Skills→
Obsidian-OwlObsidian-Owl
1

dev.tasks

Convert feature design artifacts into a dependency-ordered tasks.md file.

Official
Advanced
jaypatrickjaypatrick

web-accessibility-audit

Automate WCAG accessibility audits and generate remediation guidance for web applications.

Community
Advanced
eaglhuangeaglhuang
3

crossref-progress-scanner

Scan TypeScript files and compare them against cross-ref-code.md mappings.

Community
Advanced
josephblaisjosephblais

github-a11y-scanner

Detect GitHub Accessibility Scanner presence and parse violation issues.

Community
Advanced