Build an accessibility issue register for document teams

A document accessibility programme needs more than a list of general recommendations: it needs a register people can discuss and verify. Accessibility Remediation Pack helps turn a single PDF or scan into working material for that review.

Give content and delivery teams a shared issue register

This article focuses on teams that manage policies, reports, forms, learning material or customer documents. The service produces a CSV issue register alongside a Markdown remediation brief and a JSON artifact. Those files give different roles a practical format for sorting, assigning and checking possible accessibility work.

The register includes structured fields for severity, WCAG criterion, issue, evidence, remediation and verification, so a reviewer has context before deciding whether a finding belongs in the delivery plan.

A practical document-to-remediation workflow

Choose the document, report language and target standard in the interface. When the process completes, download the deliverables from the action results area and keep them with the source version that was assessed.

• Upload one PDF, PNG, JPG/JPEG or TIFF document, up to 80 MB.
• Choose the report language and set an accessibility target, such as WCAG 2.2 AA.
• Review the downloaded brief, issue register, source text and JSON before assigning work.

Use the API in an existing review process

The same workflow is available through the documented multipart API. Submit one permitted file, request asynchronous processing, then use the returned action identifier to monitor progress and retrieve the text, Markdown, CSV and JSON results.

A CMS, records platform or service desk can use that pattern to create a review task without treating an automated output as an automatic approval.

Keep human testing and content rights in the workflow

A CSV register is not proof of conformance. A qualified reviewer should check evidence against the actual document, confirm priorities with affected users and perform manual accessibility testing before closing work items.

The organisation remains responsible for source permissions, the chosen accessibility target and the release decision.

Start with a document your team can review

Accessibility Remediation Pack gives document teams a consistent starting format for a human-led accessibility register.