accessibility-statement
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.
pinned to #0872b4aupdated 2 weeks ago
Ask your AI client: “install skills/accessibility-statement”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/accessibility-statementmetahub onboarded this repo on the author's behalf.
If you own github.com/Community-Access/accessibility-agents on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
356
Last commit
2 weeks ago
Latest release
published
- #a11y
- #accessibility
- #ai-agents
- #aria
- #assistive-technology
- #claude
- #claude-code
- #copilot
- #github-copilot
- #screen-reader
- #wcag
- #web-accessibility
About this skill
Pulled from SKILL.md at publish time.
Derived from `.claude/agents/accessibility-statement.md`. Treat platform-specific tool names or delegation instructions as Codex equivalents.
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.0872b4a· 2 weeks ago
Kind-specific
31Skill: SKILL.md present
found at codex-skills/accessibility-statement/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
182 words · 1,376 chars · 5 sections
Skill: triggers declaredwarn
No `trigger` phrases in SKILL.md frontmatter
Add `trigger:` lines so Claude knows when to activate this skill — e.g. `when building MCP servers` or `for diagram creation`.
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)
Release history
1- releasecurrent0872b4awarn2 weeks ago
Contents
Derived from .claude/agents/accessibility-statement.md. Treat platform-specific tool names or delegation instructions as Codex equivalents.
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
- Organization name and date
- Conformance status (Fully/Partially/Non-conformant)
- Standard targeted (WCAG version + level)
- Scope (pages/apps covered)
- Known limitations with workarounds
- Assessment approach
- Feedback mechanism with response commitment
- Compatibility (browsers, AT tested)
EU Model (Public Sector Required)
All of W3C, plus:
- Disproportionate burden declaration
- National enforcement body link
- Annual review commitment
Workflow
- Check for existing audit reports
- Gather organization details (name, URL, contact, legal framework)
- Map findings to known limitations
- Classify conformance status
- Generate HTML or Markdown document
- Save to
ACCESSIBILITY-STATEMENT.md
Conformance Classification
| 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 |
Reviews
No reviews yet. Be the first.
Related
Planning With Files
Claude Code skill implementing Manus-style persistent markdown planning — the workflow pattern behind the $2B acquisition.
Frontend Slides
Create beautiful slides on the web using Claude's frontend skills
orchestration-patterns
>
mh install skills/accessibility-statement