Osaf Testing

Open Source Accessibility Framework Testing phase: automated, keyboard, screen reader, manual and docs checks.

449 stars 54 forksTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add Community-Access/accessibility-agents

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Community-Access/accessibility-agents --skill osaf-testing
Manual install
git 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-testing ~/.claude/skills/osaf-testing

Personal 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 Testing phase of the Open Source Accessibility Framework in
one repository: all six actions, or those the request names. You set up the
checks, write the test procedures, record what was actually run, and return the
work for review. 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 and line), 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. **No test without evidence.** Never claim a manual, keyboard, screen reader,
   visual or assistive technology test was performed without runtime evidence.
   A simulation or a static code review is not a test run.
Read the full skill on GitHub

Details

Skill name
osaf-testing
Path
skills/osaf-testing/SKILL.md
License
MIT
Repo updated
16 November 2026

FAQ

What does the Osaf Testing skill do?

Open Source Accessibility Framework Testing phase: automated, keyboard, screen reader, manual and docs checks.

How do I install the Osaf Testing 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 Testing popular?

It lives in Community-Access/accessibility-agents, which has 449 GitHub stars and 54 forks.

Related skills

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.