Agency document handoff

PDF batch preflight

Find structural review tasks across a batch of PDFs, then download a handoff report.

Limited structural checks. Human review is required; this report does not certify WCAG or PDF/UA conformance.

Choose your batch

Files stay in this browser

Up to 20 PDFs · 20 MiB each · 100 MiB per batch · 200 pages each

No PDF uploads, document storage or remote AI. Processing uses browser memory. Exports include filenames and metadata, so check them before sharing.

Three synthetic documents with different review tasks, plus an unreadable file.

Choose files or try the sample batch.

What this checks

  • Page count, document title and default language
  • The document’s tagged flag and retrievable page structure
  • Pages without extractable non-whitespace text

Tags and text can be present but unusable. A blank page can legitimately have neither. Findings are starting points for inspection.

Continue the review

Reading order, tag quality, image alternatives, forms, links, contrast and OCR accuracy are not tested here.

For broader checks, use PAC, axesCheck or veraPDF, and inspect the document with assistive technology. Check each tool’s privacy terms before sharing client files.

How to interpret the findings

Mozilla PDF.js reads the document structure. The Marked flag is a declaration; a page structure tree is a presence signal. Neither establishes correct tagging. Text extraction does not confirm OCR accuracy, visible text, or reading order.

Document language is the catalog’s /Lang value, not a detected language. A title’s presence does not confirm its usefulness or that a viewer displays it. A parser limitation can prevent a property from being retrieved.

Each file has a 60-second time limit. Password-protected files and unsupported XFA forms need a different tool. Limits, cancellations and parser errors remain in the exported report.

Primary references: PDF.js document API, PDF.js page API, and W3C techniques for document titles, language and reading order.