Use this checklist when deciding whether an Accessibility Audit Toolkit candidate is suitable for an organisation's environment. Record the reviewer, date, application and version, operating system, assistive technology, result, evidence reference and limitation for every completed check. An unchecked item is not evidence of a pass.
The candidate toolkit provides blank review packets, registers and completed examples. Users perform and retain their own review because browser, office-suite, assistive-technology, security and legal requirements vary by organisation. The seller does not receive project data and no hosted validation service is required.
Offline workspace
- [ ] Open the local workspace without an internet connection and create a project.
- [ ] Complete intake, regulatory profile, scope, inventory, sampling and assignments using only the keyboard.
- [ ] Add findings, evidence references, remediation actions, retests, exceptions and approvals.
- [ ] Confirm required-field errors are specific, associated with their controls and recoverable.
- [ ] Export a project, import it into a clean browser profile and compare record counts and identifiers.
- [ ] Create a backup, restore it and verify that no current project data is lost.
- [ ] Confirm the dashboard and status summaries match the underlying registers.
- [ ] Test at 320 CSS pixels, 200% text size and 400% browser zoom without loss of content or horizontal page scrolling.
- [ ] Test visible focus, focus order, reduced motion and Windows forced colours.
- [ ] Review headings, landmarks, instructions, errors and status updates with a screen reader.
Workbooks and documents
- [ ] Open every included workbook in the organisation's supported spreadsheet application.
- [ ] Confirm table filters, controlled lists, formulas, validation messages, charts and print areas work as described.
- [ ] Enter a representative project and confirm dashboard totals reconcile with source sheets.
- [ ] Open every editable deliverable and archive PDF; confirm headings, tables, links, reading order and page breaks remain usable.
- [ ] Export one edited deliverable to PDF and inspect the resulting accessibility and visual quality.
- [ ] Confirm completed examples are clearly distinguished from blank working assets.
Representative assistive technology
- [ ] NVDA with Firefox or Chrome on Windows.
- [ ] VoiceOver with Safari on macOS.
- [ ] TalkBack with Chrome on a physical Android device when mobile use is in scope.
- [ ] Any additional browser, screen reader, magnifier, speech-input or braille combination required by the organisation.
Record unavailable combinations as limitations; do not mark them passed.
Regulatory and professional review
- [ ] A qualified reviewer confirms the selected regulatory profiles match the engagement's jurisdiction, product type, entity and effective dates.
- [ ] A standards reviewer checks normative references, exceptions, evidence expectations and claim boundaries.
- [ ] A procurement specialist reviews Section 508 or ACR material when used for procurement decisions.
- [ ] A legal or regulatory adviser reviews jurisdiction-specific conclusions when legal reliance is intended.
- [ ] An independent accessibility practitioner completes a representative assessment from intake through client report and records usability issues.
- [ ] The authorised approver accepts or rejects each unresolved limitation, exception and residual risk.
Release decision
- [ ] The package manifest and SHA-256 checksums match the downloaded files.
- [ ] The edition identifier and publication date are recorded in the project.
- [ ] Compatibility, accessibility, regulatory and practitioner review records identify named reviewers and dated evidence.
- [ ] All critical issues are closed or explicitly rejected for release.
- [ ] The authorised decision is recorded as approved, approved with limitations or not approved.
Structural validation of a record proves that required fields are present; it does not prove that a review occurred or that the conclusion is legally correct.