PDF Accessibility Scanning

Use this page as the entry point for PDF-related Accessibility guidance and to understand how PDF workflows differ from standard web or mobile Accessibility testing.

As you read on, you will see where document scanning sits in the broader Accessibility documentation. You will also learn what to verify before treating PDF results as equivalent to DOM-based web testing, because document flows follow different constraints than page markup.

When to use this

Use this page when your team needs to evaluate document accessibility separately from standard DOM-based web accessibility flows.

Important note

PDF accessibility should be treated as its own document-focused workflow. Do not assume that web Accessibility findings automatically cover PDF content.

Onboarding checklist (PDF workflow)

Confirm scope with legal or design: which PDFs are in scope (marketing, invoices, user manuals)?
Upload or target the PDF through the product flow your account supports for document scanning (menus vary by release).
Choose WCAG / PDF-UA expectations aligned with your policy—note that automated checks still require manual reading order and tag inspection for high-stakes filings.
Review findings in the same dashboard patterns as web reports where applicable; export evidence for audits (exporting).
Track remediation in your CMS or document owner tool; re-upload after fixes and re-scan.