Kb Testing Strategy

Reference data, not a reviewer. Accessibility testing decision trees, browser/AT compatibility matrices, manual vs. automated test coverage, regression testing patterns, and acceptance criteria templates for user stories.

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 kb-testing-strategy
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/kb-testing-strategy ~/.claude/skills/kb-testing-strategy

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

## Testing Strategy Skill

Decision frameworks for accessibility testing - when to use automated tools vs. manual testing, which screen reader + browser combinations to test, and how to write accessibility acceptance criteria.

---

## Automated vs. Manual Testing Coverage

Each row, with what automated tools catch and what requires manual testing. Published coverage estimates vary with the study and with whether issues or success criteria are counted, so treat a clean automated scan as a floor, not a pass. Most WCAG 2.2 additions (2.4.11, 2.5.7, 3.2.6, 3.3.7, 3.3.8) have no axe rule.

| What Automated Tools Catch | What Requires Manual Testing |
|--------------------------------------|---------------------------------------|
| Missing alt text on images | Alt text quality and accuracy |
| Missing form labels | Label clarity and helpfulness |
| Color contrast ratios (computed) | Color contrast in context (gradients, images) |
| Missing lang attribute | Correct language identification |
| Duplicate IDs referenced by ARIA or labels (`duplicate-id-aria`) | Logical reading order |
| Missing ARIA roles on custom widgets | Correct ARIA role for the interaction pattern |
| Heading hierarchy violations | Heading text meaningfulness |
| Empty links and buttons | Link/button text descriptiveness |
| Missing table headers | Table caption and header association quality |
| Syntax errors in ARIA | Screen reader announcement correctness |

## Browser + Screen Reader Compatibility Matrix
Read the full skill on GitHub

Details

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

FAQ

What does the Kb Testing Strategy skill do?

Reference data, not a reviewer. Accessibility testing decision trees, browser/AT compatibility matrices, manual vs. automated test coverage, regression testing patterns, and acceptance criteria templates for user stories.

How do I install the Kb Testing Strategy 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 Kb Testing Strategy 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.