Osaf Foundational
Open Source Accessibility Framework Foundational phase: ACCESSIBILITY.md and an accessibility label.
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-foundationalgit 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-foundational ~/.claude/skills/osaf-foundationalPersonal 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 Foundational phase of the Open Source Accessibility Framework in one repository: both of its actions, or the one the request names. You write what the actions need, verify each against its Definition of Done, and return the work for the maintainer to review. This phase comes before the other three. Framework facts, the full action index and the tracking issue: `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 the request names none, ask before changing files. If a named action does not exist, say so and list the valid ones below. 2. **Bundled requirements.** Each Definition of Done below is the minimum, taken from the canonical phase document at `metadata.osaf-commit`. It works offline. Read an action's reference only when that action is in scope. 3. **Online check, only when asked** for the latest guidance. Fetch `metadata.osaf-source`, take the first 12 hex characters of its SHA-256 and compare with `metadata.osaf-digest`. If they differ, report what changed and ask before using it. A failed fetch never blocks the work. 4. **Inspect before editing.** For each Definition of Done item decide: met (cite the file and line), needs a change, or needs maintainer input, external configuration or a person. 5. **Edit in phase order.** Keep the repository's conventions. Extend an existing accessibility document rather than replace it.
Details
- Skill name
osaf-foundational- Repository
- Community-Access/accessibility-agents
- Path
skills/osaf-foundational/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Osaf Foundational skill do?
Open Source Accessibility Framework Foundational phase: ACCESSIBILITY.md and an accessibility label.
How do I install the Osaf Foundational 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 Foundational 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.
Performance Accessibility
449Community-Access/accessibility-agents
Lazy loading, skeletons, layout shift and loading states for AT users.
Osaf Community
449Community-Access/accessibility-agents
Open Source Accessibility Framework Community phase: reports, participation, recognition, progress, resources.
Web Accessibility Wizard
449Community-Access/accessibility-agents
Guided WCAG 2.2 audit of a web app or site, phase by phase, with severity scores, a written report and optional fixes.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.