acceptance-patterns

Reviews test coverage and audits WCAG 2.1 AA accessibility using JS/TS testing patterns.

2|Updated Jul 25, 2026
One-click install
npx skills add https://github.com/ankaboot-source/boucle --skill acceptance-patterns-ankaboot-source
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acceptance-patterns
Source: https://github.com/ankaboot-source/boucle/tree/main/.jcode/skills/acceptance-patterns
Command: npx skills add https://github.com/ankaboot-source/boucle --skill acceptance-patterns-ankaboot-source

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams shipping features often lack a consistent way to verify acceptance criteria are actually tested and that pages meet WCAG 2.1 AA accessibility requirements, leading to coverage gaps and compliance violations discovered late. ## Core Features & Use Cases - Testing Patterns Reference: Arrange-Act-Assert structure, naming conventions, assertions, mock discipline, React Testing Library, Supertest API testing, and Playwright E2E patterns for JavaScript/TypeScript. - Accessibility Checklist: WCAG 2.1 AA checks covering keyboard navigation, screen readers, contrast, forms, ARIA live regions, and common anti-patterns, plus tools like axe-core, pa11y, and Lighthouse. - Structured Findings Report: Produces a test coverage assessment across the unit→integration→E2E ladder, severity-rated accessibility violations with remediation, and a PASS/FAIL/UNPROVEN verdict. - Use Case: Before merging a feature, load this Skill to verify every acceptance criterion has a corresponding test and audit the deployed page for critical accessibility violations. ## Quick Start Review the test coverage and accessibility of the new task creation feature and produce a findings report with a verdict.

Frequently Asked Questions about acceptance-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write acceptance tests with Playwright?

Playwright E2E tests simulate real user flows: navigate, fill forms via getByRole and getByLabel locators, click buttons, and assert visible outcomes. Prefer accessible locators over CSS selectors so tests verify behavior rather than implementation details.

How to check a website for WCAG 2.1 AA compliance?

Run automated audits with axe-core, pa11y, or Lighthouse, then manually verify keyboard navigation, focus visibility, form labels, and contrast ratios of 4.5:1 for text. Screen reader testing with VoiceOver or NVDA catches issues automation misses.

What is the Arrange-Act-Assert pattern in testing?

Arrange-Act-Assert structures each test into three phases: set up test data and preconditions, perform the action being tested, then verify the outcome. It keeps tests readable and makes failures easy to diagnose.

Should I use getByRole or CSS selectors in Playwright tests?

Use getByRole and getByLabel locators, which query elements the way users and assistive technologies perceive them. CSS selectors couple tests to styling and DOM structure, breaking on refactors without indicating real regressions.

What are common accessibility anti-patterns to avoid?

Common anti-patterns include using divs as buttons, missing alt text, color-only state indicators, removing focus outlines, empty links, and tabindex values greater than zero. Each breaks keyboard or screen reader access and has a semantic HTML fix.