可以穷手机操作器

System Requirements

⚠️ CRITICAL: To remain current with Accessibility Agents and ensure proper functionality, you must keep all tools updated to their latest versions. New platform capabilities, API changes, accessibility features, and bug fixes directly impact agent behavior.

Required Tools (Latest Versions)

For GitHub Copilot (VS Code):

• VS Code: Latest stable release and/or VS Code Insiders (Download)
• GitHub Copilot Extension: Latest version from VS Code Marketplace
• GitHub Copilot Chat Extension: Latest version from VS Code Marketplace
• Node.js: v18.0.0 or higher (for CLI tools like axe-core)

For Claude Code:

• Claude Code CLI: Latest version (Installation)
• Claude Subscription: Pro, Max, or Team plan

For Gemini CLI:

• Gemini CLI: Latest version (Installation)
• Google AI Studio API Key: Active key (Get Started)

Operating Systems:

• macOS: 10.15 (Catalina) or later
• Windows: Windows 10/11 with PowerShell 5.1+ (pre-installed)

Extensions → @installed → Click update icon next to GitHub Copilot extensions

5.0 Installation Direction

Version 5.0.0 moves Accessibility Agents to a GitHub Skills installation flow backed by native Go binaries for setup, health checks, repair, and hook management.

Planned 5.0 flow:

gh skill install Community-Access/accessibility-agents
gh skill setup Community-Access/accessibility-agents
gh skill health Community-Access/accessibility-agents

Important:

• gh skill install is the future primary install path.
• The setup tooling is being implemented as native Go binaries, not Node.js scripts.
• Node.js is still required for the MCP server itself, but not for the installer experience.

Build the 5.0 CLI

If you are contributing to the 5.0 installer transition or preparing release artifacts, install Go and build the native CLI locally.

Windows:

winget install --id GoLang.Go --exact --accept-package-agreements --accept-source-agreements
go version
pwsh -NoProfile -File scripts/build-go-cli.ps1

macOS:

brew install go
go version
bash scripts/build-go-cli.sh

The compiled binaries are written to go-cli/bin/. Windows outputs are .exe files. macOS outputs are native CLI executables.

GitHub Actions also builds the Go CLI automatically on Windows, macOS, and Linux via .github/workflows/build-go-cli.yml.

5.0+ uses the GitHub Skills / Go CLI path as the supported installer path.

Install

Use the GitHub Skills installer:

gh skill install Community-Access/accessibility-agents

Then run setup/health/repair utilities as needed:

gh skill setup Community-Access/accessibility-agents
gh skill health Community-Access/accessibility-agents
gh skill repair Community-Access/accessibility-agents

Uninstall

gh skill uninstall Community-Access/accessibility-agents

If you need manual cleanup details, see UNINSTALL.md.

Safe installation — your files are never overwritten

The setup flow is designed to be additive and non-destructive:

• Agent files (~/.claude/agents/, .github/agents/) - existing files are skipped, not replaced. A message tells you which agents were skipped so you know what you already have.
• Config files (copilot-instructions.md, copilot-review-instructions.md, copilot-commit-message-instructions.md) - our content is wrapped in `` markers and merged into your existing file. Your content above and below the markers is always preserved. If the file does not exist, it is created.
• Asset directories (skills/, instructions/, prompts/) - copied file-by-file; files that already exist are skipped.
• Manifest file (.a11y-agent-manifest) - tracks every file we installed. Repair and update flows use this list to ensure they only touch files we own, never user-created agents. When contributors add new agents to the repo, those files are installed on the next setup/repair pass and added to the manifest.

Updates are equally safe - maintenance flows never delete user agent files. If a file is not in the manifest (meaning you created it yourself), it will not be modified or removed.

To reinstall a specific agent from scratch, delete it first and rerun setup or repair.

Post-Install Validation

After installation, run a validation and self-repair pass. This verifies that all installed surfaces are intact, MCP base dependencies are present, and Playwright is functional if installed.

You can also run it manually at any time:

PowerShell (Windows) — validate only:

pwsh -NoProfile -ExecutionPolicy Bypass -File scripts/repair-install.ps1 -SummaryPath .a11y-agent-team-install-summary.json

PowerShell (Windows) — validate and auto-repair:

pwsh -NoProfile -ExecutionPolicy Bypass -File scripts/repair-install.ps1 -SummaryPath .a11y-agent-team-install-summary.json -Repair

Shell (macOS / Linux / Git Bash) — validate only:

bash scripts/repair-install.sh --summary=.a11y-agent-team-install-summary.json --validate-only

Shell (macOS / Linux / Git Bash) — validate and auto-repair:

bash scripts/repair-install.sh --summary=.a11y-agent-team-install-summary.json

VS Code users can run these via the Terminal > Run Task menu: look for the Repair: task group.

The repair pass checks and fixes:

• Destination paths — every installed surface (Claude, Copilot, Codex, Gemini, MCP) exists on disk
• MCP base dependencies — @modelcontextprotocol/sdk and zod are present; runs npm install --omit=dev if missing
• Playwright — playwright-core is installed; Chromium is functional; re-runs setup if broken
• Copilot profile root cleanup — removes stray agent/prompt/instruction files placed directly in VS Code profile roots instead of the expected subdirectories

Findings are appended to the install summary JSON and a separate .a11y-agent-team-repair-summary.json is written next to it. See Troubleshooting for symptom-specific guidance.

GitHub Skills Rollout Guides

For the GitHub Skills specification rollout and release-readiness workflows, see:

• docs/guides/GITHUB-SKILLS-CLI-READINESS.md
• docs/guides/SKILLS-RELEASE-READINESS-TEST-PLAN.md
• .github/workflows/skills-cli-readiness.yml
• .github/workflows/skills-release-readiness.yml

Quick Start

Advanced Guides

The following guides cover advanced configuration, cross-platform handoff, and distribution.

Example Project

The example/ directory contains a deliberately broken web page with 20+ intentional accessibility violations. Use it to practice with the agents and see how they catch real issues. See the example README for details.

Help → Check for Updates (or auto-updates if enabled in settings)

Optional Customization

Update GitHub Copilot Extensions

GitHub Workflow Agents

The following agents handle GitHub repository management, triage, and workflow automation.

See the Agent Reference Guide for deep dives on every agent, example prompts, behavioral constraints, and instructor-led walkthroughs.

GitHub Workflow Docs

The following guide covers all GitHub workflow agents and their invocation syntax.

Update VS Code

VS Code 1.113 Highlights

VS Code 1.113 is currently the most relevant baseline for GitHub Copilot users of this repo. The release added several changes that improve Accessibility Agents workflows directly:

• MCP across agent types - MCP servers configured in VS Code now bridge into Copilot CLI and Claude agents, which makes this repo's MCP guidance more consistent across local, CLI, and Claude workflows.
• Chat Customizations editor - Chat: Open Chat Customizations gives you one place to inspect and manage instructions, prompt files, agents, skills, MCP servers, and plugins.
• Broader Agent Debug coverage - Agent Debug Logs now cover Copilot CLI and Claude agent sessions in addition to local sessions.
• Integrated browser improvements - local HTTPS testing with self-signed certificates is easier, and browser tab management is better for accessibility testing workflows.
• Nested subagents - VS Code now supports nested subagent delegation. For this repo, that is treated as an optional platform capability, not a default architecture choice. We favor explicit coordinator-worker flows and keep nested subagents disabled by default.

Subagent stance for this repo:

• Reward: bounded subagents improve specialization, parallel analysis, and audit structure.
• Risk: unrestricted or nested subagents can increase duplicate findings, wrong-agent selection, token cost, and debugging complexity.
• Recommendation: use explicit, allowlisted specialist delegation; avoid recursive subagent chains unless a workflow is intentionally designed for them.

For official details, see the VS Code 1.113 release notes: https://code.visualstudio.com/updates/v1_113.

VS Code 1.113 Workflow Tips

If you are using Accessibility Agents in VS Code 1.113, these settings and commands are the most useful starting point:

{
  "chat.useCustomizationsInParentRepositories": true,
  "github.copilot.chat.agentDebugLog.enabled": true,
  "github.copilot.chat.agentDebugLog.fileLogging.enabled": true,
  "chat.imageSupport.enabled": true
}

• Run Chat: Open Chat Customizations to inspect loaded instructions, agents, skills, MCP servers, and plugins.
• Use /troubleshoot when a customization is not loading or an expected tool is missing.
• Keep chat.subagents.allowInvocationsFromSubagents disabled unless you are intentionally experimenting with recursive orchestration patterns.

That last point is a repo recommendation, not a VS Code limitation.

Custom Thinking Phrases (VS Code 1.110+)

VS Code users: Personalize the loading text that appears while agents think with accessibility-themed phrases.

Add to VS Code Settings (settings.json):

{
  "chat.agent.thinking.phrases": {
    "mode": "append",  // Adds to default phrases
    "phrases": [
      "Checking contrast ratios...",
      "Testing with screen readers...",
      "Verifying keyboard navigation...",
      "Reviewing ARIA patterns...",
      "Scanning for accessibility barriers...",
      "Consulting WCAG 2.2..."
    ]
  }
}

Options:

• "mode": "append" - Adds your phrases to VS Code's default list (recommended)
• "mode": "replace" - Only shows your custom phrases

Why This Matters:

• Reinforces accessibility focus during agent work
• Reminds team members that accessibility is actively considered
• Optional fun enhancement to make wait time more engaging

How to Add:

1. Open VS Code Settings (Ctrl/Cmd + ,)
2. Click "Open Settings (JSON)" icon in top-right
3. Add the chat.agent.thinking.phrases setting
4. Reload window (Command Palette → "Developer: Reload Window")

Community Contributions: Have a great accessibility-themed thinking phrase? Submit a PR to add it to our recommended list in CONTRIBUTING.md!

Install from VS Code Marketplace (Coming Soon)

GitHub Copilot users (VS Code): A VS Code extension is in development that will allow one-click install from the Extensions marketplace. Until then, use the one-liner install above or the manual steps in Getting Started.

What the extension will include:

• ✅ 59 fully-integrated agents in GitHub Copilot (VS Code and CLI)
• ✅ 18 reusable accessibility skills (WCAG rules, severity scoring, scanning patterns)
• ✅ 106 custom prompts for web audits, document audits, GitHub workflows, and developer tooling
• ✅ 6 workspace instructions (automatic WCAG AA enforcement on every chat)
• ✅ 100% source citation coverage (all agents cite authoritative standards)
• ✅ Auto-update mechanism (new agents and features arrive automatically)

For other platforms (Claude Code, Gemini, Claude Desktop, Codex), see Getting Started.