Replace informal “looks good” messages with an assigned, version-bound decision that remains useful after the document changes.
Annual-report.pdf
Version 4 approval
Verify reading order, table headers, link purpose, and the two remaining items marked for manual review.
The workflow
Choose the current processed version, assign an eligible workspace reviewer, add instructions, and set an optional due date.
The reviewer can start work, approve the version, request specific changes, or cancel the request with a durable decision note.
Every decision remains tied to its version and appears in the document activity record and central review queue.
Why version binding matters
Accessibility evaluation is useful before release and as part of ongoing monitoring. W3C guidance also recommends clearly assigned responsibility and follow-up procedures. DocAccessible applies that principle at the document level: a decision names the reviewer, identifies the version, records the outcome, and becomes visibly outdated after a new version is saved.
Read W3C planning guidanceQuestions
No. Approval records an accountable internal decision about a specific DocAccessible version. It does not replace expert evaluation, assistive-technology testing, or third-party certification when those are required.
The old approval stays attached to the version that was reviewed. The new current version is shown as needing a new review, preventing a changed document from silently inheriting an earlier decision.
A review can be assigned to an editor, admin, or owner in the workspace. The assigned reviewer or a workspace administrator can record the decision.
Version-bound review and approval is included with Pro and Team. Team adds shared workspace roles so review work can be distributed across multiple people.
After publication