Resource / Practical, ungated guidance
Accessibility acceptance checklist
Questions and test scenarios to put accessibility evidence into a software procurement.
Put the target and evidence in scope
Specify the accessibility standard, important workflows, test devices, and evidence required for acceptance. Define responsibility for third-party widgets, generated documents, and content entered by customer staff. A target is different from a completed assessment.
- Agreed WCAG target
- Workflow and document inventory
- Third-party component responsibilities
- Assessment report and issue register
- VPAT/ACR deliverable if required
Test the actual journey
Walk intake, validation errors, uploads, review, payment handoff, and confirmation using only a keyboard. Review names, instructions, status announcements, focus order, contrast, zoom, and reduced motion. Pair automated checks with manual review.
- Keyboard-only completion
- Visible focus and logical order
- Labels and error associations
- Screen-reader status updates
- 200% zoom and responsive layout
- Reduced-motion behavior
Plan remediation and ongoing ownership
Record issues by workflow and impact, name an owner, and agree retesting before acceptance. Train content administrators to preserve headings, link descriptions, and document accessibility. Keep a contact route for reports of barriers.
- Named remediation owner
- Retest evidence
- Content authoring guidance
- Accessible document process
- User feedback and triage route