Accessibility testing decision trees, browser/AT compatibility matrices, manual vs. automated test coverage, regression testing patterns, and acceptance criteria templates for user stories.
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeNot declared
CursorNot declared
CodexNot declared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Repository health
Stars405
LicenseLICENSE
Default branchmain
Open issues18
Status
Active
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md5,322 B
docsSUMMARY.md4,022 B
History
First seen on skills.sh
First recorded snapshot · 211 installs
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
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)
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)
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.
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 information
