Web Interface Guidelines Reviewer
vercel-labs/openreview
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
Build accessibility scanners, rule engines, parsers and report generators.
Install A11y Tool Builder
$ npx skills add Community-Access/accessibility-agents --skill a11y-tool-builder -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Community-Access/accessibility-agents a11y-tool-builder --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/a11y-tool-builder .claude/skills/a11y-tool-builder && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "a11y-tool-builder" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/a11y-tool-builder into .claude/skills/a11y-tool-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "a11y-tool-builder", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Community-Access/accessibility-agents/tree/main/skills/a11y-tool-builderType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Community-Access/accessibility-agents --skill a11y-tool-builder -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Community-Access/accessibility-agents a11y-tool-builder --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/a11y-tool-builder .agents/skills/a11y-tool-builder && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "a11y-tool-builder" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/a11y-tool-builder into .agents/skills/a11y-tool-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "a11y-tool-builder", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Community-Access/accessibility-agents --skill a11y-tool-builder -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Community-Access/accessibility-agents a11y-tool-builder --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/a11y-tool-builder .cursor/skills/a11y-tool-builder && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "a11y-tool-builder" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/a11y-tool-builder into .cursor/skills/a11y-tool-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "a11y-tool-builder", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Community-Access/accessibility-agents.git --path skills/a11y-tool-builder--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Community-Access/accessibility-agents --skill a11y-tool-builder -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Community-Access/accessibility-agents a11y-tool-builder --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/a11y-tool-builder .gemini/skills/a11y-tool-builder && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "a11y-tool-builder" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/a11y-tool-builder into .gemini/skills/a11y-tool-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "a11y-tool-builder", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Community-Access/accessibility-agents a11y-tool-builderInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Community-Access/accessibility-agents --skill a11y-tool-builder -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/a11y-tool-builder .github/skills/a11y-tool-builder && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "a11y-tool-builder" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/a11y-tool-builder into .github/skills/a11y-tool-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "a11y-tool-builder", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Community-Access/accessibility-agents --skill a11y-tool-builder -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Community-Access/accessibility-agents a11y-tool-builder --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/a11y-tool-builder .opencode/skills/a11y-tool-builder && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "a11y-tool-builder" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/a11y-tool-builder into .opencode/skills/a11y-tool-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "a11y-tool-builder", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
a11y-tool-builder- GitHub stars
- 423
- Token cost
- ~991 tokens
- SKILL.md length
- 456 words
- Files
- 2
- Skills in repo
- 108
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build accessibility scanners, rule engines, parsers and report generators.
- Works in 5 steps: Rules are data, not code. Store rules as… → Severity scoring is principled.… → Reports serve multiple audiences.… → …
- Tasks that involve Accessibility
- SKILL.md covers Accessibility Tool Builder, Core Principles, Rule Engine Pattern and Report Generation, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
A11y Tool Builder is an agent skill from Community-Access/accessibility-agents. Build accessibility scanners, rule engines, parsers and report generators.
Its SKILL.md is about 990 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Frontend & Design, covering Accessibility. The repository describes itself as: Accessibility review agents for Claude Code, GitHub Copilot, and Claude Desktop. Eleven specialists that enforce WCAG 2.2 AA compliance so AI coding tools stop generating… The licence is MIT.
When your agent uses it
- Tasks that involve Accessibility
Example prompts
- “/a11y-tool-builder”
Requirements
- Python 3
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Rules are data, not code. Store rules as YAML/JSON with WCAG mappings. Adding a rule should never require code changes.
- Severity scoring is principled. Consistent formulas: impact x frequency x confidence.
- Reports serve multiple audiences. Developers need line numbers. Managers need scores. Compliance needs WCAG references.
- Parsers are the foundation. Invest in parsing robustness for HTML, DOCX, PDF, UIA trees.
- Cross-team alignment. Findings must be compatible with web, document, and desktop audit workflows.
What it can do on your machine
Read from SKILL.md and the folder at commit decf6ba. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
A11y Tool Builder loads about 991 tokens when it runs. Until then it costs about 23 tokens; SKILL.md has 456 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Community-Access/accessibility-agents at commit decf6ba, republished under its MIT licence (© Community-Access). 456 words, ~991 tokens.
Download SKILL.mdSave it as
.claude/skills/a11y-tool-builder/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- a11y-tool-builder
- description
- Build accessibility scanners, rule engines, parsers and report generators.
- license
- MIT
- disable-model-invocation
- true
- metadata.tier
- specialist
- metadata.domain
- developer
- metadata.output
- guidance
- metadata.effort
- medium
- metadata.title
- Accessibility Tool Builder
Accessibility Tool Builder
Skills: python-development
You are an accessibility tool builder -- an expert in designing and building the scanning tools, rule engines, parsers, and report generators that power accessibility auditing workflows. You understand the architecture of tools like axe-core, pa11y, Accessibility Insights, and know how to build equivalent tooling for desktop apps, documents, and custom domains.
You receive handoffs from the Developer Hub when a task involves building accessibility tooling. You coordinate extensively with both the Web Accessibility and Document Accessibility teams to ensure tools you build are aligned with existing audit methodologies.
Core Principles
- Rules are data, not code. Store rules as YAML/JSON with WCAG mappings. Adding a rule should never require code changes.
- Severity scoring is principled. Consistent formulas: impact x frequency x confidence.
- Reports serve multiple audiences. Developers need line numbers. Managers need scores. Compliance needs WCAG references.
- Parsers are the foundation. Invest in parsing robustness for HTML, DOCX, PDF, UIA trees.
- Cross-team alignment. Findings must be compatible with web, document, and desktop audit workflows.
Rule Engine Pattern
- Store rules in YAML with: id, name, description, wcag mapping, severity, applies_to, check logic, fix template, auto_fixable flag
- Engine loads rules from directory, evaluates against parsed elements, produces Finding objects
- Findings include: rule_id, severity, wcag_criteria, element, location, description, fix_suggestion, auto_fixable, confidence
Report Generation
- Severity scoring: critical=10, serious=5, moderate=2, minor=1. Score = 100 * (1 - weighted_issues / max_penalty)
- Grade scale: A (90+), B (80+), C (70+), D (60+), F (below 60)
- Output formats: Markdown report + CSV export + SARIF (for GitHub Code Scanning)
- Report sections: Metadata, executive summary, findings, severity breakdown, remediation priorities, next steps, delta tracking
Show full SKILL.md (188 more words)Show less
Document Parser Patterns
- DOCX: python-docx for heading hierarchy, alt text, table headers, hyperlink text
- PDF: pikepdf/pdfplumber for tagged structure, language, bookmarks
- UIA tree: comtypes/pywinauto for live desktop app accessibility tree walking
Cross-Team Alignment
- Web: Use web-accessibility-wizard rule IDs for web checks. Align with web-severity-scoring formulas.
- Document: Use document-accessibility-wizard rule IDs (DOCX-, XLSX-, PDFUA.*). Align with report-generation scoring.
- Desktop: Define DESK-* rule IDs. Map to WCAG. Route findings to desktop-a11y-specialist.
Behavioral Rules
- Rules are data -- design engines that load from YAML/JSON
- Always include WCAG mapping for every rule
- Use consistent critical/serious/moderate/minor severity scale
- Route Python implementation to python-specialist
- Route GUI work to wxpython-specialist
- Route web rule questions to web-accessibility-wizard
- Route document rule questions to document-accessibility-wizard
- Produce multiple output formats (Markdown + CSV + SARIF)
- Include auto-fix classification for every finding
- Include pytest tests for rule engines and parsers
Output contract
Answer the question. Keep the answer to what was asked, cite the criterion or API by name, and stop. Do not append a checklist that was not requested.
Shared rules, dispatch contract and schemas: skills/a11y-core/SKILL.md.
Authoritative specifications for this skill: skills/a11y-core/references/sources.md.
© Community-Access, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/a11y-tool-builder of Community-Access/accessibility-agents.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit decf6ba
Compare with similar skills
A11y Tool Builder next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| A11y Tool Builder this skillCommunity-Access/accessibility-agents | 423 | — | ~991 | Automated safety check: Pass | MIT | |
| Web Interface Guidelines Reviewervercel-labs/openreview | 1.7k | 97 repos | ~308 | Automated safety check: Pass | None | |
| Accessibility Reviewmarkmead/hyperui | 12k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Web Animation DesignbaptisteArno/typebot.io | 11k | 2 repos | ~2.7k | Automated safety check: Pass | Custom licence | |
| Accessibility Fixeribelick/ui-skills | 9.5k | 4 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Wcag Audit PatternsvmDeshpande/ai-agent-automation | 178 | 11 repos | ~610 | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Accessibility Review
markmead/hyperui
Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.
Web Animation Design
baptisteArno/typebot.io
Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.
Accessibility Fixer
ibelick/ui-skills
Audits and fixes HTML accessibility problems such as ARIA labels, keyboard navigation, focus management, contrast and form errors with minimal changes.
Wcag Audit Patterns
vmDeshpande/ai-agent-automation
Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.
Baseline UI
ibelick/ui-skills
Applies a fixed set of UI rules for stack, components, interaction, animation, typography and layout, or reviews a file against them with concrete fixes.
More from Community-Access/accessibility-agents
All 108 skills in this repoA11y Core
Community-Access/accessibility-agents
Shared contract for the Accessibility Agents skills - dispatch, findings schema, report rules.
Kb Web Scanning
Community-Access/accessibility-agents
Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.
Accessibility Lead
Community-Access/accessibility-agents
Web UI accessibility lead. An agent skill from Community-Access/accessibility-agents.
Alt Text Headings
Community-Access/accessibility-agents
Alt text, SVGs, figures, charts, heading order, page titles and landmarks.
Aria Specialist
Community-Access/accessibility-agents
ARIA roles, states and properties for custom widgets and dynamic content.
Cognitive Accessibility
Community-Access/accessibility-agents
Plain language, WCAG 2.2 cognitive criteria, COGA guidance and auth UX.
Related
Categories
Questions about A11y Tool Builder
What does A11y Tool Builder do?
Build accessibility scanners, rule engines, parsers and report generators. A11y Tool Builder is an agent skill from Community-Access/accessibility-agents. Build accessibility scanners, rule engines, parsers and report generators.
When should I use A11y Tool Builder?
A11y Tool Builder fits situations like: tasks that involve Accessibility.
How do I install A11y Tool Builder in Claude Code?
Run `npx skills add Community-Access/accessibility-agents --skill a11y-tool-builder -a claude-code`. Or copy the skill folder (skills/a11y-tool-builder in Community-Access/accessibility-agents) into .claude/skills/a11y-tool-builder in your project. Claude Code loads it when a task matches its description.
How do I install A11y Tool Builder in Codex?
Run `npx skills add Community-Access/accessibility-agents --skill a11y-tool-builder -a codex`. Or copy the skill folder (skills/a11y-tool-builder in Community-Access/accessibility-agents) into .agents/skills/a11y-tool-builder in your project. Codex loads it when a task matches its description.
Can I use A11y Tool Builder in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Community-Access/accessibility-agents --skill a11y-tool-builder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/a11y-tool-builder, .gemini/skills/a11y-tool-builder, .github/skills/a11y-tool-builder and .opencode/skills/a11y-tool-builder in your project.
What does A11y Tool Builder need to run?
SKILL.md names no scripts, command-line tools or credentials: A11y Tool Builder is instructions for the agent only. Our summary lists: Python 3.
Does A11y Tool Builder access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is A11y Tool Builder safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does A11y Tool Builder use?
A11y Tool Builder is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does A11y Tool Builder use?
About 991 tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to A11y Tool Builder?
Skills that share tags, products or a category with A11y Tool Builder: Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars), Accessibility Review (markmead/hyperui, 12k stars), Web Animation Design (baptisteArno/typebot.io, 11k stars) and Accessibility Fixer (ibelick/ui-skills, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains A11y Tool Builder?
Community-Access (a GitHub organization) maintains it in Community-Access/accessibility-agents, which has 423 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on September 23, 2026.
Source: Community-Access/accessibility-agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.