A PDF accessibility workflow
Source-backed explanations and practical guidance. Educational information, not a legal determination.
Define the task and target
Identify the document’s purpose, audience, applicable standard, responsible owner, and available authoring source. The Title II web rule adopts WCAG 2.1 AA. A PDF workflow or tool result alone is not a conformance determination. Read the federal requirement.
Correct the source where practical
Suggested workflow: use meaningful headings, lists, table structure, link text, and image alternatives in the source, then export with accessibility-supporting settings. Inspect the output; do not assume export success means every feature is correct. If only a PDF is available, assess the file before selecting a remediation approach. Use the Section508.gov PDF resources.
Check text and structure
For image-based content, assess whether optical character recognition (OCR) is needed and check recognized text for errors. Review tags, reading order, language, headings, tables, and image alternatives. For interactive files, also inspect accessible names, instructions, keyboard order, and errors. W3C’s OCR technique addresses one part of this work.
Combine automated and human checks
Run appropriate document checks, then inspect content and structure manually. Exercise keyboard tasks and test meaningful reading and task completion with a screen reader. Reading-order inspection, visible content review, and assistive-technology use provide different evidence; none should be represented as a universal standalone proof. W3C’s reading-order technique includes a test procedure.
Publish, retest, and maintain
Verify the final downloadable file and its surrounding page, not just an intermediate editor view. Record the version, target, checks performed, findings, and unresolved issues. Retest after changes. Estimate time from actual document complexity and review needs; this guide promises no fixed turnaround, per-page price, or “compliant in an afternoon” outcome.