This is a decision framework for when to use automated versus manual accessibility testing, which browser and screen reader combinations actually matter, and how to write testable acceptance criteria. The automated versus manual coverage table is genuinely useful because it shows that tools only catch 30-40% of issues while things like alt text quality and logical reading order need human judgment. The browser and screen reader matrix is opinionated in a good way, marking NVDA with Firefox and Chrome plus JAWS with Chrome as must-test combinations. The acceptance criteria template gives you specific checkboxes for user stories rather than vague guidance. If you're tired of guessing which accessibility tests to run or arguing about coverage, this gives you a starting point backed by actual testing patterns.

skills.sh installs
215
GitHub stars
442
last updated
Aug 21, 2026

Install

$ npx -y skills add community-access/accessibility-agents --skill testing-strategy --agent claude-code

Installs into .claude/skills of the current project.

Files

This is a decision framework for when to use automated versus manual accessibility testing, which browser and screen reader combinations actually matter, and how to write testable acceptance criteria. The automated versus manual coverage table is genuinely useful because it shows that tools only catch 30-40% of issues while things like alt text quality and logical reading order need human judgment. The browser and screen reader matrix is opinionated in a good way, marking NVDA with Firefox and Chrome plus JAWS with Chrome as must-test combinations. The acceptance criteria template gives you specific checkboxes for user stories rather than vague guidance. If you're tired of guessing which accessibility tests to run or arguing about coverage, this gives you a starting point backed by actual testing patterns.

Browse the repository on GitHub

Sponsors

Details

Repository
github.com/community-access/accessibility-agents
Categories
Testing & QA, Productivity & Planning, Automation & Workflows, Design & UI/UX
First seen
Jun 3, 2026

More from community-access/accessibility-agents

All 25
1supabase avatare2e-studio-testssupabase/supabaseRun e2e tests in the Studio app. Use when asked to run e2e tests, run studio tests, playwright tests, or test the feature.211skills.sh installs
2personamanagmentlayer avatartesting-expertpersonamanagmentlayer/pclExpert-level software testing with unit tests, integration tests, E2E tests, TDD/BDD, and testing best practices203skills.sh installs
3itechmeat avatarvitestitechmeat/llm-codeVitest testing framework: Vite-powered tests, Jest-compatible API, mocking, snapshots, coverage, browser mode, and TypeScript support. Use when writing or confi201skills.sh installs
4oguzhan18 avatarangular-testingoguzhan18/angular-ecosystem-skillsALWAYS use when writing tests for Angular applications, including unit tests, component tests, service tests, or E2E tests with Jasmine, Karma, Vitest, or Cypre197skills.sh installs
5warpdotdev avatarwebapp-testingwarpdotdev/oz-skillsTest local web applications with Playwright. Use when asked to verify frontend functionality, debug UI behavior, capture browser screenshots, or inspect browser192skills.sh installs
6yonatangross avatartesting-patternsyonatangross/orchestkitRedirect — testing-patterns was split into 5 focused sub-skills. Use when looking for testing-patterns, writing tests, or test automation. Redirects to testing-179skills.sh installs