QA Engineer
dralgorhythm/claude-agentic-framework
Define test strategy and verify quality against WCAG and testing-pyramid criteria — a user-invoked QA Engineer workflow.
Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.
Install Kb Testing Strategy
$ npx skills add Community-Access/accessibility-agents --skill kb-testing-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Community-Access/accessibility-agents kb-testing-strategy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/kb-testing-strategy .claude/skills/kb-testing-strategy && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "kb-testing-strategy" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-testing-strategy into .claude/skills/kb-testing-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kb-testing-strategy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-testing-strategyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Community-Access/accessibility-agents --skill kb-testing-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Community-Access/accessibility-agents kb-testing-strategy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/kb-testing-strategy .agents/skills/kb-testing-strategy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "kb-testing-strategy" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-testing-strategy into .agents/skills/kb-testing-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kb-testing-strategy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Community-Access/accessibility-agents --skill kb-testing-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Community-Access/accessibility-agents kb-testing-strategy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/kb-testing-strategy .cursor/skills/kb-testing-strategy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "kb-testing-strategy" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-testing-strategy into .cursor/skills/kb-testing-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kb-testing-strategy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Community-Access/accessibility-agents.git --path skills/kb-testing-strategy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Community-Access/accessibility-agents --skill kb-testing-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Community-Access/accessibility-agents kb-testing-strategy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/kb-testing-strategy .gemini/skills/kb-testing-strategy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "kb-testing-strategy" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-testing-strategy into .gemini/skills/kb-testing-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kb-testing-strategy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Community-Access/accessibility-agents kb-testing-strategyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Community-Access/accessibility-agents --skill kb-testing-strategy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/kb-testing-strategy .github/skills/kb-testing-strategy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "kb-testing-strategy" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-testing-strategy into .github/skills/kb-testing-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kb-testing-strategy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Community-Access/accessibility-agents --skill kb-testing-strategy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Community-Access/accessibility-agents kb-testing-strategy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/kb-testing-strategy .opencode/skills/kb-testing-strategy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "kb-testing-strategy" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-testing-strategy into .opencode/skills/kb-testing-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kb-testing-strategy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
kb-testing-strategy- GitHub stars
- 422
- Token cost
- ~1.4k tokens
- SKILL.md length
- 463 words
- Files
- 2
- Skills in repo
- 108
- Repo updated
- First seen
- Licence
- MIT
At a glance
Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.
- Works in 4 steps: axe-core scan: Run on every PR. Fail on… → Baseline management: Store known issues… → Lighthouse score threshold: Set minimum… → …
- Tasks that involve Accessibility
- SKILL.md covers Testing Strategy Skill, Automated vs. Manual Testing…, Browser + Screen Reader… and Testing Decision Tree, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Kb Testing Strategy is an agent skill from Community-Access/accessibility-agents. 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.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Testing & QA, covering Accessibility, User stories and QA and bug reports. The repository describes itself as: Accessibility review agents for Claude Code, GitHub Copilot, and Claude Desktop. Eleven specialists that enforce WCAG 2.2 AA compliance so AI coding tools stop generating… The licence is MIT.
When your agent uses it
- Tasks that involve Accessibility
- Tasks that involve User stories
- Tasks that involve QA and bug reports
Example prompts
- “/kb-testing-strategy”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- axe-core scan: Run on every PR. Fail on new critical/serious violations.
- Baseline management: Store known issues in .a11y-baseline.json. Only fail on new issues.
- Lighthouse score threshold: Set minimum accessibility score (e.g., 90). Fail on regression.
- Visual regression: Capture screenshots at 200% zoom. Compare for focus indicator and layout changes.
What it can do on your machine
Read from SKILL.md and the folder at commit decf6ba. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Kb Testing Strategy loads about 1.4k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 463 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Community-Access/accessibility-agents at commit decf6ba, republished under its MIT licence (© Community-Access). 463 words, ~1,434 tokens.
Download SKILL.mdSave it as
.claude/skills/kb-testing-strategy/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- kb-testing-strategy
- description
- 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.
- license
- MIT
- disable-model-invocation
- true
- user-invocable
- false
- metadata.tier
- reference
- metadata.domain
- cross-cutting
- metadata.output
- none
- metadata.effort
- low
- metadata.title
- Testing Strategy
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 (~30-40%) and what requires manual testing (~60-70%).
| What Automated Tools Catch (~30-40%) | What Requires Manual Testing (~60-70%) |
|---|---|
| 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 | 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
Primary Test Combinations (Required)
Each screen reader, with its browser, OS and priority.
| Screen Reader | Browser | OS | Priority |
|---|---|---|---|
| NVDA | Firefox | Windows | Must test |
| NVDA | Chrome | Windows | Must test |
| JAWS | Chrome | Windows | Must test |
| VoiceOver | Safari | macOS | Must test |
| VoiceOver | Safari | iOS | Must test |
| TalkBack | Chrome | Android | Should test |
Secondary (Nice to Have)
Each screen reader, with its browser and OS.
| Screen Reader | Browser | OS |
|---|---|---|
| Narrator | Edge | Windows |
| JAWS | Edge | Windows |
Testing Decision Tree
Is it a new component or page?
├── Yes → Full test coverage (automated + manual)
│ ├── Run axe-core / Lighthouse scan
│ ├── Keyboard-only navigation test
│ ├── Screen reader announcement test (NVDA + VoiceOver minimum)
│ └── Visual check at 200% zoom
└── No → What changed?
├── Colors/styling → Contrast check + visual review
├── Interactive behavior → Keyboard + screen reader test
├── Content/text → Screen reader announcement check
├── Layout/order → Reading order + focus order test
└── Dependencies updated → Regression scan (axe-core)Regression Testing Patterns
CI Pipeline Accessibility Gates
- axe-core scan: Run on every PR. Fail on new critical/serious violations.
- Baseline management: Store known issues in
.a11y-baseline.json. Only fail on new issues. - Lighthouse score threshold: Set minimum accessibility score (e.g., 90). Fail on regression.
- Visual regression: Capture screenshots at 200% zoom. Compare for focus indicator and layout changes.
Show full SKILL.md (185 more words)Show less
Preventing Regressions
- Add accessibility assertions to existing component tests (see
testing-accessibility.instructions.md) - Include keyboard navigation in E2E test suites
- Track accessibility score trends over time (not just pass/fail)
Acceptance Criteria Template
For User Stories
Given [context],
When [action by keyboard/mouse/screen reader],
Then [accessible outcome]:
- [ ] Component has an accessible name (via label, aria-label, or aria-labelledby)
- [ ] Component has the correct ARIA role
- [ ] Component is reachable and operable by keyboard (Tab, Enter, Space, Escape, Arrows as appropriate)
- [ ] Focus is visible when the component receives focus
- [ ] State changes are announced to screen readers (aria-expanded, aria-selected, aria-checked, etc.)
- [ ] Error messages are associated with their inputs (aria-describedby or aria-errormessage)
- [ ] Content is readable at 200% zoom without horizontal scrolling
- [ ] Color is not the only means of conveying informationCommon Testing Tools
Each tool, with type and best for.
| Tool | Type | Best For |
|---|---|---|
| axe-core / @axe-core/cli | Automated | CI/CD integration, broad violation scan |
| Lighthouse | Automated | Performance + accessibility combined score |
| WAVE | Semi-automated | Visual overlay of accessibility features/issues |
| Accessibility Insights | Semi-automated | FastPass (automated) + Assessment (guided manual) |
| pa11y | Automated | CI/CD, HTML CodeSniffer rules |
| jest-axe | Unit test | Component-level axe scans in jest |
| cypress-axe | E2E test | Page-level axe scans in Cypress |
| playwright + @axe-core/playwright | E2E test | Page-level axe scans in Playwright |
Screen Reader Testing Quick Reference
NVDA (Windows)
Each key, with its action.
| Key | Action |
|---|---|
| Insert + Space | Toggle focus/browse mode |
| Tab | Move to next focusable element |
| H | Next heading |
| D | Next landmark |
| F | Next form field |
| T | Next table |
| Insert + F7 | Elements list (links, headings, landmarks) |
VoiceOver (macOS)
Each key, with its action.
| Key | Action |
|---|---|
| VO (Ctrl+Option) + Right | Move to next element |
| VO + Space | Activate current element |
| VO + U | Open rotor (navigate by type) |
| VO + Cmd + H | Next heading |
© Community-Access, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/kb-testing-strategy of Community-Access/accessibility-agents.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit decf6ba
Compare with similar skills
Kb Testing Strategy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Kb Testing Strategy this skillCommunity-Access/accessibility-agents | 422 | — | ~1.4k | Automated safety check: Pass | MIT | |
| QA Engineerdralgorhythm/claude-agentic-framework | 125 | — | ~631 | Automated safety check: Pass | None | |
| Build Scenario Teststamdogood/builder-essential-skills | 219 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Scoutqa Testgithub/awesome-copilot | 40k | 1 repos | ~3.5k | Automated safety check: Pass | MIT | |
| QA Testingespennilsen/pi | 122 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Test Specgustavscirulis/snapgrid | 117 | 1 repos | ~12k | Automated safety check: Notes | Custom licence |
Similar skills
Build Scenario Tests
tamdogood/builder-essential-skills
Inspect an unfamiliar repository, turn a focused Markdown behavior scenario into a deterministic test in the repository's native test stack, run it, and preserve traceability between intent and code.
- Official
Scoutqa Test
github/awesome-copilot
This skill should be used when the user asks to "test this website", "run exploratory testing", "check for accessibility issues", "verify the login flow works", "find bugs on this page", or requests…
QA Testing
espennilsen/pi
Perform QA testing on running web applications using cmuxbrowser.
Test Spec
gustavscirulis/snapgrid
Generates comprehensive test specification with unit tests, UI tests, accessibility testing, and beta testing plan.
Sfdipot Product Factors
proffesor-for-testing/agentic-qe
James Bach's HTSM Product Factors (SFDIPOT) analysis for comprehensive test strategy generation.
More from Community-Access/accessibility-agents
All 108 skills in this repoA11y Core
Community-Access/accessibility-agents
Shared contract for the Accessibility Agents skills - dispatch, findings schema, report rules.
Kb Web Scanning
Community-Access/accessibility-agents
Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.
Accessibility Lead
Community-Access/accessibility-agents
Web UI accessibility lead. An agent skill from Community-Access/accessibility-agents.
Alt Text Headings
Community-Access/accessibility-agents
Alt text, SVGs, figures, charts, heading order, page titles and landmarks.
Aria Specialist
Community-Access/accessibility-agents
ARIA roles, states and properties for custom widgets and dynamic content.
Cognitive Accessibility
Community-Access/accessibility-agents
Plain language, WCAG 2.2 cognitive criteria, COGA guidance and auth UX.
Related
Questions about Kb Testing Strategy
What does Kb Testing Strategy do?
Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents. Kb Testing Strategy is an agent skill from Community-Access/accessibility-agents. Reference data, not a reviewer.
When should I use Kb Testing Strategy?
Kb Testing Strategy fits situations like: tasks that involve Accessibility; tasks that involve User stories; tasks that involve QA and bug reports.
How do I install Kb Testing Strategy in Claude Code?
Run `npx skills add Community-Access/accessibility-agents --skill kb-testing-strategy -a claude-code`. Or copy the skill folder (skills/kb-testing-strategy in Community-Access/accessibility-agents) into .claude/skills/kb-testing-strategy in your project. Claude Code loads it when a task matches its description.
How do I install Kb Testing Strategy in Codex?
Run `npx skills add Community-Access/accessibility-agents --skill kb-testing-strategy -a codex`. Or copy the skill folder (skills/kb-testing-strategy in Community-Access/accessibility-agents) into .agents/skills/kb-testing-strategy in your project. Codex loads it when a task matches its description.
Can I use Kb Testing Strategy in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Community-Access/accessibility-agents --skill kb-testing-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/kb-testing-strategy, .gemini/skills/kb-testing-strategy, .github/skills/kb-testing-strategy and .opencode/skills/kb-testing-strategy in your project.
What does Kb Testing Strategy need to run?
SKILL.md names no scripts, command-line tools or credentials: Kb Testing Strategy is instructions for the agent only.
Does Kb Testing Strategy access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Kb Testing Strategy safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Kb Testing Strategy use?
Kb Testing Strategy is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Kb Testing Strategy use?
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Kb Testing Strategy?
Skills that share tags, products or a category with Kb Testing Strategy: QA Engineer (dralgorhythm/claude-agentic-framework, 125 stars), Build Scenario Tests (tamdogood/builder-essential-skills, 219 stars), Scoutqa Test (github/awesome-copilot, 40k stars) and QA Testing (espennilsen/pi, 122 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Kb Testing Strategy?
Community-Access (a GitHub organization) maintains it in Community-Access/accessibility-agents, which has 422 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on September 23, 2026.
Source: Community-Access/accessibility-agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.