accessibility-testing
把自动化工具和手动检查结合进 CI，弥补工具盲点并生成可复现报告。
结合 axe-core 与 Playwright 做 WCAG 规范的自动化与人工辅助无障碍测试。
自动跑 axe-core + Playwright 做 WCAG 2.2 AA 的检测，同时覆盖键盘导航、屏幕阅读器和 ARIA 模式的人工核查，把可访问性检查放进 CI。适合需要满足 ADA/WCAG 合规或把无障碍作为开发流程一部分的团队。特点是把自动扫描和必要的人工作业结合起来，因为自动工具只能发现大约三成问题。
▸ 展开 SKILL.md 英文原文
Test for WCAG 2.2 AA compliance with axe-core + Playwright, keyboard navigation audits, screen reader testing, ARIA pattern validation, and legal compliance mapping (ADA, EAA, Section 508). Automated tools catch 30-40% of issues — this skill covers automated and manual testing together. Use when: "accessibility," "a11y," "WCAG," "screen reader," "axe," "keyboard navigation," "ARIA," "ADA compliance." Not for: cookie-consent/GDPR compliance — use compliance-testing; pixel-diff visual regression — use visual-testing. Related: playwright-automation, compliance-testing, visual-testing, ci-cd-integration.
帮我安装这个 skill：https://raw.githubusercontent.com/petrkindlmann/qa-skills/main/skills/accessibility-testing/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/petrkindlmann/qa-skills/main/skills/accessibility-testing/SKILL.md"<objective> Make an application usable by people who rely on keyboards and assistive technology, and prove it with tests that run in CI. A button that passes `toBeVisible()` can still be unreachable by keyboard; a page with zero axe violations can still be impossible to operate with a screen reader. Automated tools catch 30-40% of accessibility issues — this skill covers the automated scan plus the keyboard, screen reader, and ARIA-state testing that catch the other 60-70%. </objective> ## Discovery Questions Check `.agents/qa-project-context.md` first — if it exists, use it as the foundation and skip anything already answered. **Requirements and compliance** (sets the target level and au