DocAccessible
Checking account
Documentation
All documentation

Collaboration

Run an accessibility program hub

Collect client requests, choose a defensible remediation path, coordinate work across workspaces, and record version-bound release evidence.

For
Agencies, accessibility leads, and client service teams
Typical time
12 minutes
Open the program hub

Before you start

  • A workspace owner, admin, or editor account
  • A clear internal owner for client intake and release decisions

Procedure

Step by step

  1. Create the private intake link

    Open Program and create the current workspace's client intake link. The complete bearer link is shown once, so send it through an appropriate private channel. Rotating it immediately revokes the previous intake link.

  2. Review the request and routing recommendation

    Open each request from the queue. Confirm the requested outcome, service impact, source constraints, and the reasons behind the suggested HTML-first, automation-plus-review, or specialist-PDF path.

  3. Assign and record the decision

    Choose a workspace owner, status, priority, and delivery path. A decision note is required when the team overrides the automated recommendation so the reason remains in the request record.

  4. Complete the version-bound release record

    On the linked document, record the human checks, assistive technology and tasks, exceptions, and release outcome for the exact current version. A linked request cannot be marked ready for the client or completed until that version is ready or ready with documented exceptions. Download the evidence record for the client or project file.

Clients can submit without joining the workspace

The intake page accepts one PDF, DOCX, or public source URL. A successful submission creates a private request-specific status link; it does not create an account, workspace membership, or access to other client work.

Intake and status tokens are stored as hashes. Treat the links as bearer credentials: share them privately, rotate intake if it leaks, and rotate an exposed status link from the request detail page.

Use triage to prioritize, not certify

HTML-first is appropriate when responsive content is the primary reading experience and no specialist constraint is visible. Automation plus review is the working path for source uncertainty, tables, images, unresolved findings, or service-critical content. Exact layout, unreliable scans, forms, maps, equations, signatures, and complex tables should move to a qualified PDF specialist.

A confidence percentage describes the strength of the routing signal. It is not a conformance score, legal opinion, or promise that the resulting document is accessible.

What the release record proves

The downloadable record identifies the exact source and output fingerprints, automated findings, selected remediation path, recorded human checklist, assistive-technology notes, review state, and open reader feedback for one immutable version.

Every required check must be passed or marked not applicable before a version can be recorded as ready. A ready-with-exceptions outcome also requires a complete checklist and written exception notes. Creating a newer document version makes the earlier record historical and restores the release gate.

It proves what the team recorded and which version it reviewed. It does not independently certify WCAG, PDF/UA, ADA, or Section 508 conformance.

Operate across client workspaces

The portfolio summarizes open requests, overdue work, documents needing attention, website alerts, and Exchange actions across every workspace you belong to. Open a workspace from the portfolio before changing its request queue or intake settings.

Related guides