What problem does it solve? Playwright tests often ship without any accessibility coverage, letting WCAG violations and broken keyboard navigation reach production unnoticed. This Skill enforces a consistent pattern so every new page or component test includes automated axe-core scans plus keyboard interaction checks that axe cannot detect. ## Core Features & Use Cases - Standardized axe-core pattern: Enforces AxeBuilder with wcag2a/wcag2aa tags and await expect(results.violations).toEqual([]) assertions in every UI spec. - Keyboard navigation testing: Adds tab-to-focus and Enter-to-activate checks for primary controls, covering gaps axe cannot detect. - Violation reporting workflow: When real violations appear, the Skill records formatted output, writes a snapshot report, and offers Jira bug filing instead of silencing rules. - Use Case: When generating a Playwright spec for a new modal, the Skill automatically includes an axe scan scoped to the dialog and a keyboard test verifying focus and activation, with no inline locators. ## Quick Start Generate a Playwright test for the new programs page and include accessibility coverage.