Documentation
All documentation

Documents

Review findings and edit accessible content

Interpret the automated score, resolve structure and alt-text issues, and save a new reviewed version.

For
Remediation contributors and accessibility reviewers
Typical time
Varies by document
Open the document library

Before you start

  • A document with a completed processed version

Procedure

Step by step

  1. Open a completed document

    Select the document from the library and begin with critical and needs-review findings rather than the score alone.

  2. Inspect structure and context

    Check headings, reading sequence, lists, links, tables, image purpose, document language, and any item that software could not responsibly decide. When AI source comparison is available, review its exact concerns and route without treating confidence as conformance.

  3. Open Edit

    Use the findings rail to jump to affected blocks, then correct headings, text, alt text, captions, table structure, lists, callouts, and reading order. Switch to Preview to inspect the unsaved accessible output, draft score, heading outline, and reading sequence before creating a version. AI-generated image descriptions are drafts and need contextual review.

  4. Save and recheck

    Saving creates a new immutable version and reruns applicable deterministic checks. If blocks changed, the prior AI source comparison becomes stale because it was bound to the earlier output. Revisit unresolved manual items before publishing or requesting approval.

How to use the score

The score is a prioritization signal based on available automated evidence. It is not proof of WCAG, PDF/UA, ADA, or Section 508 conformance, and it should not be used as the only release gate.

Manual review still matters

Reading order, complex tables, charts, forms, language changes, meaningful image descriptions, and the assistive-technology experience can require a qualified person. Keep those decisions visible in your review record.