Osaf Community
Open Source Accessibility Framework Community phase: reports, participation, recognition, progress, resources.
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 osaf-communitygit clone --depth 1 https://github.com/Community-Access/accessibility-agents.git /tmp/accessibility-agents
mkdir -p ~/.claude/skills
cp -r /tmp/accessibility-agents/skills/osaf-community ~/.claude/skills/osaf-communityPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
You implement the Community phase of the Open Source Accessibility Framework in one repository: all six actions, or those the request names. Most of this phase is practice and relationships, so you write the documents and drafts, and the maintainer decides what is published. Facts and the action index: `kb-open-source-accessibility-framework`. ## How you work 1. **Scope.** Every action in phase order, or only those named by number, title or ID. If none is named, ask before changing files. Report an unknown action and list the valid ones. 2. **Bundled requirements.** The Definitions of Done below are the minimum, from the phase document at `metadata.osaf-commit`, and work offline. Read an action's reference only when it is in scope. 3. **Online check, only when asked.** Fetch `metadata.osaf-source`; if the first 12 hex characters of its SHA-256 differ from `metadata.osaf-digest`, report the change and ask before using it. A failed fetch never blocks the work. 4. **Inspect before editing.** Per item: met (cite file, line or URL), needs a change, or needs maintainer input, external configuration or a person. 5. **Edit in phase order**, keep repository conventions, extend `ACCESSIBILITY.md` rather than replace it. 6. **Protect contributor privacy and choice.** Never infer consent, disclose disability-related or accommodation information, speak for a disability community, or publish recognition or community messages without authorization.
Details
- Skill name
osaf-community- Repository
- Community-Access/accessibility-agents
- Path
skills/osaf-community/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Osaf Community skill do?
Open Source Accessibility Framework Community phase: reports, participation, recognition, progress, resources.
How do I install the Osaf Community 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 Osaf Community 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.
Osaf Foundational
449Community-Access/accessibility-agents
Open Source Accessibility Framework Foundational phase: ACCESSIBILITY.md and an accessibility label.
Mobile Accessibility
449Community-Access/accessibility-agents
React Native, Expo, iOS and Android: labels, roles and touch targets.
Performance Accessibility
449Community-Access/accessibility-agents
Lazy loading, skeletons, layout shift and loading states for AT users.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.