A11y Tool Builder logo

A11y Tool Builder

Organization
Community-Access
a11y-tool-builder

Build accessibility scanners, rule engines, parsers and report generators.

Overview

PublisherCommunity-Access
Repositoryaccessibility-agents
Skill namea11y-tool-builder
Stars
429
Forks
51
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Community-Access on GitHub. Read the source before you install it.

Installation

Install the A11y Tool Builder AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Community-Access/accessibility-agents/tree/main/skills/a11y-tool-builder
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git 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-builder
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable A11y Tool Builder in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads A11y Tool Builder on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so A11y Tool Builder is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

  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. Consistent formulas: impact x frequency x confidence.
  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
  • 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

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

  1. Rules are data -- design engines that load from YAML/JSON
  2. Always include WCAG mapping for every rule
  3. Use consistent critical/serious/moderate/minor severity scale
  4. Route Python implementation to python-specialist
  5. Route GUI work to wxpython-specialist
  6. Route web rule questions to web-accessibility-wizard
  7. Route document rule questions to document-accessibility-wizard
  8. Produce multiple output formats (Markdown + CSV + SARIF)
  9. Include auto-fix classification for every finding
  10. 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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the A11y Tool Builder AI skill do?

Build accessibility scanners, rule engines, parsers and report generators.

Why use A11y Tool Builder on TypingMind?

Because you install it once and use it with any model. A11y Tool Builder is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install A11y Tool Builder in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Community-Access/accessibility-agents/tree/main/skills/a11y-tool-builder. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use A11y Tool Builder?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with A11y Tool Builder?

As many as you like. As long as a model supports skills, you can use A11y Tool Builder with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the A11y Tool Builder AI skill free?

Yes. It is published on GitHub by Community-Access under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇