A11y Tool Builder
Build accessibility scanners, rule engines, parsers and report generators.
Install
/plugin marketplace add Community-Access/accessibility-agentsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Community-Access/accessibility-agents --skill a11y-tool-buildergit clone --depth 1 https://github.com/Community-Access/accessibility-agents.git /tmp/accessibility-agents
mkdir -p ~/.claude/skills
cp -r /tmp/accessibility-agents/skills/a11y-tool-builder ~/.claude/skills/a11y-tool-builderPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
## Accessibility Tool Builder **Skills:** `kb-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 1. **Rules are data, not code.** Store rules as YAML/JSON with WCAG mappings. Adding a rule should never require code changes. 2. **Severity scoring is principled.** One formula: severity weight x confidence, scaled by the checks run (`kb-web-severity-scoring`). 3. **Reports serve multiple audiences.** Developers need line numbers. Managers need scores. Compliance needs WCAG references. 4. **Parsers are the foundation.** Invest in parsing robustness for HTML, DOCX, PDF, UIA trees. 5. **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
Details
- Skill name
a11y-tool-builder- Repository
- Community-Access/accessibility-agents
- Path
skills/a11y-tool-builder/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the A11y Tool Builder skill do?
Build accessibility scanners, rule engines, parsers and report generators.
How do I install the A11y Tool Builder skill?
Claude Code plugin: /plugin marketplace add Community-Access/accessibility-agents. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is A11y Tool Builder popular?
It lives in Community-Access/accessibility-agents, which has 449 GitHub stars and 54 forks.
Related skills
A11y Core
449Community-Access/accessibility-agents
Shared contract for the Accessibility Agents skills - dispatch, findings schema, report rules. Read by skills, never dispatched on its own.
Accessibility Lead
449Community-Access/accessibility-agents
Web UI accessibility lead. Use before writing or changing HTML, JSX, TSX, Vue, Svelte, CSS or templates. Picks specialists and merges their findings.
Accessibility Regression Detector
449Community-Access/accessibility-agents
Compare audits across commits to find new, fixed and regressed issues.
Vueuse Functions
398JetBrains/skills
Apply VueUse composables where appropriate to build concise, maintainable Vue.js / Nuxt features.
Accessibility Statement
449Community-Access/accessibility-agents
Generate a W3C or EU model accessibility statement from audit results.
Vue
398JetBrains/skills
Vue 3 Composition API, script setup macros, reactivity system, and built-in components. Use when writing Vue SFCs, defineProps/defineEmits/defineModel, watchers, or using Transition/Teleport/Suspense/KeepAlive.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.