At a glance
A handoff record connects the agreed source, required output and reader task with actual delivery and review evidence. This template does not pre-fill a pass or conformance claim. It leaves delivered revision, evidence and decision fields for the responsible team to complete when those events occur.
State requirements before asking a supplier or teammate to fix the document.
| Reader task | Required output | Constraint | Decision |
|---|---|---|---|
| Read example policy | Reviewed HTML | Original PDF retained | Await owner review |
| Complete example application | Scoped form output | Submission path | Requirements need confirmation |
Scroll sideways to see all columns. Use arrow keys when the table is focused.
Agree on the source and constraints
Identify the exact PDF and authorized authored source, if available. Define required formats, languages, original-layout needs, signatures and interactive behavior. A vendor should not have to guess which file is current or whether a rebuilt layout is acceptable.
Describe important reader tasks and acceptance scope. Include automated checks, manual semantic review and assistive-technology tasks as appropriate, with a declared environment. These evidence types should remain distinguishable.
- Replace the examples with agreed deliverables before work starts.
- Identify the exact source and requirements; do not infer the current version.
- Set review scope and correction responsibilities explicitly.
- Record actual delivered revisions and evidence before an approval decision.
- Do not replace all acceptance checks with one conformance checkbox.
Complete evidence fields only when it exists
Record the actual delivered revision and authorized evidence location. Keep open findings visible. An empty cell is not a passed test, and a completed delivery is not necessarily an approved publication.
If a source or output changes, update its identity and repeat affected checks. Keep the correction responsibilities and responsible owner in the record so unresolved questions have a clear destination.
Share only the authorized package
A public example worksheet is safe to reuse; a populated handoff may contain private document references or review records. Use scoped access for real collaboration and remove private capability links before broader circulation.
Worksheet fields
The records sheet has 10 columns. Keep a stable ID and source evidence when sorting or extending it.
| Column | How to use it |
|---|---|
| Deliverable ID | Stable ID for each agreed output or review item. |
| Source revision | Exact original and authorized authored-source references. |
| Reader task | Intended use and essential interactions. |
| Required output | Reviewed HTML, tagged PDF or other explicitly scoped format. |
| Constraints | Layout, signatures, language, forms and source-owner restrictions. |
| Acceptance checks | Specific automated/manual/assistive-technology review scope. |
| Delivered revision | Actual immutable output version, filled on delivery. |
| Evidence | Authorized review record; no private capability URLs in public copies. |
| Open findings | Known gaps; blank does not automatically mean all checks passed. |
| Decision / owner | Recorded approval, further correction or escalation by the responsible team. |
Scroll sideways to see all columns. Use arrow keys when the table is focused.
The original worksheet schemas and fictional rows are offered under CC0. You can adapt them without a required backlink. This reuse statement covers the template assets, not the third-party references.
Sources and scope
Methods, worksheets and illustrative examples are DocAccessible editorial contributions. These references support the technical or product details described above. W3C techniques are informative guidance; they are not a certification scheme.
- DocAccessible remediation options
The different output paths and their review requirements.
- W3C: evaluating web accessibility
Automated tools and knowledgeable human evaluation serve different roles.
Written by the DocAccessible team under our editorial policy. Suggest a correction if a source or product detail needs updating.