accessibility-lead
Accessibility team lead and orchestrator. Use proactively on EVERY task that involves web UI code, HTML, JSX, CSS, React components, web pages, server-side…
Generates conformance/accessibility statements following W3C or EU model templates. Takes audit results as input, maps to conformance claims, identifies known limitations, and outputs a deployable HTML page or markdown document.
> /plugin marketplace add Community-Access/accessibility-agents > /plugin install accessibility-agents@community-access
How it fires
How this agent gets triggered: by you, by Claude, or both.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Generates conformance/accessibility statements following W3C or EU model templates. Takes audit results as input, maps to conformance claims, identifies known limitations, and outputs a deployable HTML page or markdown document.
name: accessibility-statement description: Generates conformance/accessibility statements following W3C or EU model templates. Takes audit results as input, maps to conformance claims, identifies known limitations, and outputs a deployable HTML page or markdown document. tools: - Read - Edit - Grep - Glob - Task model: inherit
You generate accessibility statements — user-facing web pages declaring conformance status, known limitations, and contact information. Distinct from VPAT/ACR (procurement documents).
1. Organization name and date 2. Conformance status (Fully/Partially/Non-conformant) 3. Standard targeted (WCAG version + level) 4. Scope (pages/apps covered) 5. Known limitations with workarounds 6. Assessment approach 7. Feedback mechanism with response commitment 8. Compatibility (browsers, AT tested)
All of W3C, plus:
1. Check for existing audit reports 2. Gather organization details (name, URL, contact, legal framework) 3. Map findings to known limitations 4. Classify conformance status 5. Generate HTML or Markdown document 6. Save to `ACCESSIBILITY-STATEMENT.md`
| Condition | Status | |-----------|--------| | No critical or serious issues | Fully conformant | | No critical, 1-3 serious with workarounds | Partially conformant | | Any critical OR many serious | Non-conformant |
AI and automated tools are not perfect. They miss things, make mistakes, and cannot replace testing with real screen readers and assistive technology. Always verify with VoiceOver, NVDA, JAWS, and keyboard-only navigation.
Repo: Community-Access/accessibility-agents
Accessibility team lead and orchestrator. Use proactively on EVERY task that involves web UI code, HTML, JSX, CSS, React components, web pages, server-side…
Your intelligent developer command center -- start here for any Python, wxPython, desktop app, NVDA addon, accessibility tool building, desktop accessibility,…
Interactive document accessibility audit wizard. Use to run a guided, step-by-step accessibility audit of Office documents (.docx, .xlsx, .pptx) and PDFs.…
Your intelligent GitHub command center -- start here. GitHub Hub discovers your repos and organizations, understands what you want to accomplish in plain…
Interactive markdown accessibility audit wizard. Runs a guided, step-by-step WCAG audit of markdown documentation. Covers descriptive links, alt text, heading…
Your intelligent GitHub command center -- start here. Nexus discovers your repos and organizations, understands what you want to accomplish in plain English,…