PDF Accessibility Scan vs Manual Remediation: What Each One Actually Does

Part of the problem is language. Vendors use the same words for different things. A software company might say their product "makes PDFs accessible." Read the fine print – it only scans for issues. A remediation agency might say they "audit" your PDFs, when what they deliver is hand-remediated files. A compliance firm might say they "certify" accessibility – what they really mean is a trained expert reviewed the file, not that a government body endorsed it. Here's the breakdown: Scanning = detection. A tool checks the PDF programmatically and reports what it found. Remediation = repair. A human expert opens the PDF and fixes what's broken. Auditing = formal evaluation. A qualified assessor tests against WCAG 2.1 AA or PDF/UA criteria and documents the results. Certification = attestation. An organization asserts that the document meets accessibility standards – but no central authority grants PDF accessibility certificates. Different activities, costs, and outputs. Treating them as the same thing leads to mismatched expectations.

An automated PDF accessibility scan is a programmatic check of a PDF's internal structure. The scanner reads the file's tags, properties, and document tree. It looks for patterns that suggest the document will or won't work well for assistive technology users. Here's what a scan typically checks: Document tagging. Is the PDF tagged? Untagged PDFs have no structure for screen readers to navigate. Document title and language. Does the PDF have a meaningful title in its metadata? Is the primary language declared? Heading hierarchy. Are headings present, properly nested, and logically ordered? Alt text fields. Do images have alternative text entries? A scan can detect whether an alt text field exists – not whether the text itself is meaningful. Table structure. Are tables tagged with proper headers and scope? Reading order. Does the tag order follow a logical sequence? Form fields. Are form controls properly labeled and tagged? Link annotations. Are hyperlinks tagged with meaningful destination text? The output is a findings report. It lists detected issues, usually with severity indicators and location references. It tells you where to look and what kind of problems exist. It does not fix anything. It does not produce a compliant document. It does not certify WCAG 2.1 AA conformance. It surfaces issues so humans can decide what to do next. Think of it like a home inspection before you buy a house. The inspector checks the foundation, tests the wiring, flags the water damage. They don't fix the roof. They give you a report so you know what you're dealing with before you spend money. Automated scans are fast. A single document takes seconds. A batch of thousands takes minutes. That speed makes them useful for triage. But automation has blind spots. A scanner cannot judge whether alt text is accurate or placeholder junk. It cannot evaluate whether a heading is meaningful. It cannot determine whether a color combination is readable for someone with low vision. That requires human judgment – which is exactly what manual remediation provides.

Manual PDF remediation is hands-on work by a trained accessibility specialist. The remediator opens the PDF in Adobe Acrobat Pro or a specialized accessibility platform. They rebuild the document's internal structure from the inside out. Tagging the document from scratch if the source file exported a flat, untagged PDF. Adding or correcting tags so every element – paragraphs, lists, tables, figures – has the correct semantic role. Fixing reading order so screen readers process content in the same order a sighted reader would see it. Writing meaningful alt text for images, charts, and diagrams. This requires understanding the image's purpose and writing a concise, useful description – not just filling in a field. Restructuring tables with proper header cells and scope definitions so screen readers can navigate them effectively. Setting document properties including title, author, subject, and language. Testing with assistive technology – often JAWS, NVDA, or VoiceOver – to verify the document reads correctly. The deliverable is a remediated PDF – a file that has been manually repaired and tested. Some vendors also include a report summarizing what was fixed. But the main output is the working file, not a list of findings. Remediation is skilled labor. An experienced remediator might spend 15 minutes on a simple one-page document to several hours on a complex report with tables and charts. Large volumes add up fast. A library of 500 documents can represent weeks of work. The cost reflects this. Remediation is priced per page, per document, or per hour. Complex documents – financial reports, forms with hundreds of fields – cost more than simple text documents. Organizations with large PDF backlogs sometimes face remediation quotes in the tens or hundreds of thousands of dollars.

Scans find problems. Remediation fixes them. The gap between them is where most organizations get stuck. A scan might report that 200 of your 1,000 PDFs are missing document titles. But it doesn't tell you which documents are customer-facing, which are internal-only, or which are required for an upcoming compliance review. A human still has to make those decisions. A scan might flag 50 PDFs with table structure issues. Remediation will fix them – but only after someone prioritizes the work, assigns budget, and sends the files to a vendor. The scan shortens the discovery phase. It doesn't eliminate the project management phase. The other gap is accuracy. Scanners sometimes flag false positives – issues that aren't actually problems. They sometimes miss real issues – false negatives. A human remediator catches what the scanner misses and validates whether flagged issues matter. There's also the question of scope. A scan tells you what's technically wrong with a file's structure. Remediation fixes the file. But neither one, by itself, guarantees that your overall accessibility program is sound. You might have perfectly remediated PDFs on a website with inaccessible navigation. The document is fixed. The experience around it might not be.

The organizations that handle PDF accessibility well don't choose between scanning and remediation. They use both, at different stages, for different purposes. Scans work at scale. If you have 5,000 PDFs, you can't manually review all of them in a week. An automated scan can. It shows you the full picture – which documents have problems, which issue categories are most common, where your biggest risks are. That data drives smart decisions about where to spend remediation budget. Remediation works for precision. Once you know which documents matter most and what's wrong with them, manual remediation produces the actual fix. A remediated PDF is a tangible deliverable. It goes on your website, gets sent to customers, gets filed with regulators. Scans support procurement. If you're getting quotes from three remediation vendors, you want to send them actual sample files with known issues. A scan report gives you that data. Vendors can estimate effort more accurately when they know what they're working with. Remediation supports compliance. If you need to demonstrate that your PDFs meet WCAG 2.1 AA or Section 508 standards, remediation is how you get there. A scan alone won't satisfy an accessibility complaint or legal review. The two aren't competitors – they're sequential. One reveals the work. The other does it.

If you're starting from zero – you have a collection of PDFs and no idea what state they're in – here's a workflow that actually works. Step 1: Generate your inventory. Collect all your PDFs. Many organizations discover files they forgot about – old reports, archived forms, product sheets from years ago. Crawl your website, check shared drives, ask departments what they're publishing. Get the full list before you start assessing. Step 2: Run an automated accessibility scan. Use an automated PDF accessibility scanner to check every file. The scan should produce a findings report for each document with severity levels. Run this at scale. Don't cherry-pick documents. You want the full picture. Step 3: Review the findings report. Look at the results in aggregate. Are missing titles your biggest problem, or untagged documents? Are tables consistently broken? Aggregate patterns tell you something about your source files or publishing process – and fixing the process prevents future problems. Step 4: Prioritize by severity and volume. Not every PDF matters equally. A broken internal memo from 2019 is different from a customer-facing form you're legally required to provide. Sort by: Regulatory or legal exposure Public visibility Frequency of use Severity of accessibility barriers Step 5: Get remediation quotes based on actual scope. Now you have data. You know how many documents need work and what kinds of problems they have. Send sample files and scan reports to remediation vendors and ask for scoped quotes. This is much better than asking "how much to fix our PDFs?" without context. Accurate scope means accurate pricing. Step 6: Remediate highest-impact documents first. Start with the documents that matter most. Get them remediated, tested, and republished. Then work down the priority list. This shows progress fast where it counts, rather than spreading effort across files nobody reads. Step 7: Add scanning to your ongoing workflow. Every new PDF you publish is a potential liability. Run new files through an automated scan before they go live. Catch problems before they reach users or auditors. This workflow treats scanning and remediation as connected phases. The scan reduces uncertainty. The remediation produces the fix. Together, they make your PDF program systematic instead of reactive.