Accessibility Statement
Generate a W3C or EU model accessibility statement from audit results.
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 accessibility-statementgit clone --depth 1 https://github.com/Community-Access/accessibility-agents.git /tmp/accessibility-agents
mkdir -p ~/.claude/skills
cp -r /tmp/accessibility-agents/skills/accessibility-statement ~/.claude/skills/accessibility-statementPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
## Accessibility Statement Generator You generate accessibility statements - user-facing web pages declaring conformance status, known limitations, and contact information. Distinct from VPAT/ACR (procurement documents). ## Statement Formats ### W3C Model 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) ### EU Model (Public Sector Required) Set by Commission Implementing Decision (EU) 2018/1523 under the Web Accessibility Directive. Whether a statement is legally required, and in which form, depends on jurisdiction; see `skills/kb-legal-compliance-mapping/SKILL.md` and do not present the statement as legal advice. All of W3C, plus: - Disproportionate burden declaration - National enforcement body link - Annual review commitment ## Workflow 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` ## Conformance Classification Conformance is set by WCAG, not by severity. "Fully conforms" means the content meets all of the WCAG requirements at the targeted level, so one failure of any severity rules it out.
Details
- Skill name
accessibility-statement- Repository
- Community-Access/accessibility-agents
- Path
skills/accessibility-statement/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Accessibility Statement skill do?
Generate a W3C or EU model accessibility statement from audit results.
How do I install the Accessibility Statement 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 Accessibility Statement 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.
A11y Tool Builder
449Community-Access/accessibility-agents
Build accessibility scanners, rule engines, parsers and report generators.
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.
CI Accessibility
449Community-Access/accessibility-agents
Set up and debug accessibility CI: baselines, SARIF and PR gating.
Accessibility Regression Detector
449Community-Access/accessibility-agents
Compare audits across commits to find new, fixed and regressed issues.
Cognitive Accessibility
449Community-Access/accessibility-agents
Plain language, WCAG 2.2 cognitive criteria, COGA guidance and auth UX.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.