accessibility-conformance-program-reviewlisted

# Accessibility Conformance Program Review Build an evidence-backed program that can support product decisions without turning a scanner result into a conformance claim. ## Workflow 1. Define the decision: internal readiness, release gate, procurement response, VPAT/ACR input, remediation portfolio, or claim review. 2. Inventory in-scope products, platforms, user roles, languages, content, third-party surfaces, and representative end-to-end tasks. Record exclusions. 3. Read `references/accessibility-conformance-program-patterns.md`. 4. Run the current-authority-at-use protocol before citing standards, templates, laws, or platform requirements. Mark unresolved authority as a blocker rather than filling it from memory. 5. Build the requirement-to-evidence matrix. Combine automated checks with keyboard, screen reader, zoom/reflow, contrast, target size, motion, captions/audio, cognitive, and platform-native testing as applicable. 6. Triage findings by user-task impact, reach, workaround quality, recurrence, and evidence confidence. Assign remediation, prevention, and retest owners. 7. Decide release and claim status independently. A product may ship with a recorded exception without earning an unqualified conformance claim. 8. Produce the conformance program, claim ledger, issue portfolio, release decision, exception register, and evidence-refresh cadence. ## When not to use - For a component or flow design critique, use the relevant interface or