Use this checklist to prepare for an accessibility requirement without assuming that one date or standard applies to every organization.
Scope
- Identify which law, policy, contract or procurement requirement is driving the work.
- Confirm the digital products, websites, apps, documents and workflows in scope.
- Record what is out of scope and why.
Ownership
- Assign owners for product, engineering, design, content, QA, procurement and compliance coordination.
- Identify who can approve fixes and release changes.
Inventory
- List templates, page types, components and user journeys.
- Include documents, embeds, authentication, payment flows and third-party services.
Testing
- Use manual keyboard, screen reader, zoom, reflow and code review where appropriate.
- Keep automated checks as one input, not the whole audit.
Remediation
- Prioritize blockers, high-impact barriers and reusable component fixes.
- Track issue IDs, affected components, expected behavior and verification steps.
Design system
- Review shared components, focus styles, form patterns, dialogs, menus, tables and notifications.
Content
- Check headings, link text, image alternatives, media, page titles, instructions and error messaging.
Documents
- Identify PDFs and other digital documents that are public-facing or otherwise in scope.
Third parties
- Review embeds, payment systems, booking systems, chat, maps, authentication providers, video players, cookie consent tools and widgets.
Retesting
- Verify fixes in the same workflow and environment that produced the finding.
Documentation
- Preserve scope, methods, findings, remediation status, known limitations and source requirements.
Ongoing governance
- Add accessibility checks to design, development, QA, content and release management.