generate-a11y-tests

Generates comprehensive Playwright accessibility tests with axe-core integration for any UI component or page. Use this skill to create automated accessibility regression tests that verify WCAG 2.1 Level AA compliance.\\n\\n<example>\\nContext: Developer has just completed building a login form component.\\nuser: \\\"Generate Playwright accessibility tests for the login form.\\\"\\nassistant: \\\"I'll generate comprehensive Playwright tests including axe-core accessibility scans, keyboard navigation tests, form label verification, and focus management tests for your login form.\\\"\\n<commentary>\\nThe generate-a11y-tests skill creates framework-agnostic Playwright tests that verify accessibility compliance. Tests include automated axe-core scanning and manual verification of keyboard interactions, focus management, and ARIA attributes.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Developer needs to add accessibility tests for a modal dialog component.\\nuser: \\\"Create accessibility tests for src/components/Modal.tsx. Focus on keyboard trapping and ARIA attributes.\\\"\\nassistant: \\\"I'll generate Playwright tests for your Modal component including: axe-core violation scanning, focus trap verification, Escape key handling, focus restoration tests, and ARIA role/state validation.\\\"\\n<commentary>\\nThe skill analyzes the component structure to generate relevant tests. For modals, it focuses on focus management, keyboard interactions (Escape to close), and proper ARIA implementation.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Developer wants to test an entire page for accessibility.\\nuser: \\\"Generate accessibility tests for /checkout page.\\\"\\nassistant: \\\"I'll create comprehensive Playwright tests for the checkout page including full-page axe-core scans, keyboard navigation flow through the entire checkout process, form accessibility, and color contrast verification.\\\"\\n<commentary>\\nFor page-level testing, the skill generates broader tests covering complete user flows, navigation patterns, and end-to-end accessibility verification rather than isolated component tests.\\n</commentary>\\n</example>