What problem does it solve? Teams that complete accessibility audits often struggle to decide which findings deserve automated regression tests, which checks must stay manual, and where each check belongs, leading to brittle, duplicated, or coverage-driven test suites. ## Core Features & Use Cases - Layer and method selection: Maps each confirmed finding to the narrowest reliable test layer, from unit and component tests through browser automation, axe integrations, keyboard checks, and visual regression. - Candidate dispositions: Classifies every candidate as covered-existing, automate-now, automate-after-enabler, manual-recurring, or do-not-add, with explicit rationale. - Manual and assistive-technology planning: Defines repeatable procedures, environments, evidence, cadence, and ownership for checks that require human judgment or screen reader smoke tests. - Use Case: After an audit confirms a focus-trap defect in a modal dialog, use this Skill to produce a source-to-coverage map that assigns a component-level keyboard test, a browser focus-restoration check, and a release-cadence screen reader smoke test. ## Quick Start Use the accessibility-regression-test-planner to turn my confirmed audit findings into a regression test plan covering automated and manual checks.