What Is PDF Remediation? The Complete Guide for 2026

PDF remediation is the process of transforming an inaccessible PDF document into one that meets accessibility standards — typically WCAG 2.1 Level AA and PDF/UA-1. This involves adding structure tags, setting a logical reading order, writing alternative text for images, tagging tables and headings, ensuring proper color contrast, and making form fields accessible to assistive technologies like screen readers.

For most organizations, PDF remediation has become urgent. The Department of Justice's Title II rule requires all state and local government web content and documents to meet WCAG 2.1 AA by April 24, 2026 — that's weeks away. Penalties start at $75,000 per violation. Over 2,000 ADA accessibility lawsuits were filed in the first half of 2025 alone, and enforcement is accelerating.

The challenge? An estimated 67% of PDFs currently in circulation are partially or fully inaccessible to people using screen readers. That's millions of government forms, financial statements, educational materials, and legal documents that an entire population cannot read. PDF remediation fixes this — either manually, with software tools, or through fully automated platforms like Foresera.

Why are most PDFs inaccessible?

PDFs were originally designed to preserve visual layout, not semantic structure. When you create a PDF from a Word document, InDesign file, or scanner, the result is typically a flat visual representation of the page. Without explicit intervention, the PDF lacks the hidden structure that assistive technologies need to make sense of the content.

The most common accessibility issues in PDFs include:

• •Missing structure tags. Without tags, a screen reader cannot distinguish headings from body text, tables from paragraphs, or captions from content. The document is just a stream of characters.
• •Incorrect reading order. Multi-column layouts, sidebars, and floating elements often read in the wrong sequence. A screen reader might jump from column one to a sidebar before finishing the paragraph.
• •Missing alternative text. Images, charts, and graphics without alt text are invisible to screen reader users. They hear nothing, or at best, a meaningless filename.
• •Untagged tables. Data tables without proper header associations become incomprehensible when read linearly. A screen reader user cannot determine which column or row a cell belongs to.
• •Scanned documents. PDFs created from scans are just images of text. Without OCR (optical character recognition) and subsequent tagging, the entire document is inaccessible.
• •Inaccessible forms. Form fields that aren't tagged or labeled can't be filled in using a keyboard or screen reader, locking people out of applications, registrations, and submissions.

What does PDF remediation actually involve?

PDF remediation addresses each of these issues systematically. The process varies by method — manual, semi-automated, or fully automated — but the core steps are consistent across all approaches.

1. Structure tagging

Every element in the document — headings, paragraphs, lists, tables, figures — gets assigned a semantic tag. These tags create a logical document tree that assistive technologies can navigate. Think of it as giving the PDF a table of contents that a screen reader can use.

2. Reading order correction

The order in which content appears visually on the page doesn't always match the logical reading order. Remediation establishes a left-to-right, top-to-bottom flow that makes sense when the document is read aloud, even for complex layouts with multiple columns, callout boxes, and footnotes.

3. Alternative text for images

Every informational image, chart, graph, and diagram needs descriptive alt text. Purely decorative images get marked as artifacts so screen readers skip them. This is one of the most time-consuming steps in manual remediation, and one of the areas where AI has the most impact.

4. Table structure repair

Data tables need proper header cells, row and column associations, and scope attributes. Complex tables with merged cells or nested headers require especially careful tagging so that each data cell can be announced with its context.

5. Heading hierarchy

Headings must follow a logical hierarchy — H1 through H6 — without skipping levels. This allows screen reader users to scan the document structure and jump to relevant sections, similar to how sighted readers scan headings visually.

6. Form field accessibility

Interactive form fields need labels, tab order, and keyboard accessibility. Required fields need indicators. Error messages need to be programmatically associated with their fields.

7. Color contrast and visual accessibility

Text must maintain a minimum contrast ratio of 4.5:1 against its background (3:1 for large text). This isn't always fixable in a PDF without altering the design, but remediation flags issues and adjusts where possible.

8. Language and metadata

The document needs a declared language (so screen readers pronounce words correctly), a descriptive title (not "Document1.pdf"), and proper bookmarks for navigation.

What standards does remediated PDF need to meet?

Depending on your jurisdiction and industry, remediated PDFs need to comply with one or more of these standards:

• •WCAG 2.1 Level AA — The Web Content Accessibility Guidelines, maintained by the W3C. This is the standard referenced by the DOJ's Title II rule and the most widely adopted benchmark globally. See our WCAG 2.1 AA checklist.
• •PDF/UA-1 (ISO 14289-1) — The Universal Accessibility standard specifically for PDF documents. It defines technical requirements for structure tags, fonts, color, and image alternatives. PDF/UA compliance is a strong signal of thorough remediation.
• •Section 508 — The federal standard for electronic and information technology. Section 508 aligns with WCAG 2.0 Level AA and applies to federal agencies and their contractors.
• •ADA Title II — Applies to state and local governments. The DOJ's 2024 rule explicitly requires WCAG 2.1 AA compliance by April 2026 (50,000+ populations) or April 2027 (smaller entities). Read our compliance guide.

Three approaches to PDF remediation

Organizations typically choose between three approaches, each with different tradeoffs in cost, speed, and quality.

Manual remediation

A trained accessibility specialist opens each PDF in Adobe Acrobat Pro (or a similar tool), manually tags every element, writes alt text, fixes reading order, and validates against WCAG checkpoints. This produces high-quality results but is painfully slow and expensive.

Semi-automated remediation

Desktop software like CommonLook, Equidox, or Continual Engine's PREP provide tools that speed up manual work — auto-detecting headings, suggesting reading order, and generating initial structure tags. A human operator still reviews and corrects everything. This is faster than fully manual work but still requires trained staff and per-seat licensing.

Fully automated remediation

Platforms like Foresera process documents end-to-end without human intervention. The document is uploaded, analyzed by an automated engine that identifies structure, generates tags, writes alt text, and produces a compliant output — typically in under 60 seconds. The best automated platforms achieve remediation rates above 95% and can process thousands of documents per day.

How much does PDF remediation cost?

The cost of PDF remediation varies dramatically depending on the method and the complexity of the documents. Here's a realistic breakdown for an organization with 10,000 pages to remediate:

Compare that to the cost of non-compliance: the average government accessibility lawsuit settlement is $52,000 — and that's before attorney fees, website takedowns, and reputational damage. Seattle Public Schools paid $815,000. One Texas county faces $52,000 per incident. The math isn't close.

The April 2026 deadline: what you need to know

On April 24, 2024, the Department of Justice published its final rule under ADA Title II, establishing specific technical requirements for web and digital content accessibility. For the first time, the rule explicitly names WCAG 2.1 Level AA as the standard, and it covers documents — not just websites.

The compliance timeline is straightforward:

• •April 24, 2026: Entities serving populations of 50,000 or more must comply.
• •April 24, 2027: All other state and local government entities must comply.
• •Penalties: $75,000 for first violations, $150,000 for subsequent violations.

This applies to every public-facing digital document: meeting minutes, budget reports, agendas, permits, forms, notices, policies, and more. Most government agencies have thousands of legacy PDFs on their websites that have never been remediated. Read our full deadline analysis.

Who needs PDF remediation?

While the Title II deadline applies specifically to government entities, PDF accessibility is a legal and ethical requirement across many sectors:

• •State and local government — Covered by Title II. Every public-facing document must comply by April 2026 or 2027. See our municipal compliance solutions.
• •Higher education — Title II (public institutions) and Title III (private institutions) both apply. Acceptance letters, financial aid documents, syllabi, and course materials all need to be accessible. Read about the university document crisis.
• •Financial services — Banks and insurance companies face ADA Title III requirements and increasing regulatory scrutiny. Account statements, disclosures, and customer communications must be accessible. Learn about financial document compliance.
• •Healthcare — Patient communications, explanations of benefits, and insurance documents are covered under Section 504 and ADA requirements.
• •Federal contractors — Section 508 requires all electronic documents to be accessible. Non-compliance can jeopardize contracts.

Frequently asked questions about PDF remediation

How long does PDF remediation take?

It depends entirely on the method. Manual remediation takes 15–60 minutes per page. Semi-automated tools reduce that to 5–20 minutes per page. Fully automated platforms like Foresera process documents in under 60 seconds regardless of page count, with no daily throughput limit.

Can I remediate PDFs myself with Adobe Acrobat?

Yes, Adobe Acrobat Pro has accessibility tools for manual tagging, reading order adjustment, and alt text. However, it requires significant training and expertise. For a small number of documents, it's viable. For hundreds or thousands, it's not practical without either a dedicated team or automated tooling.

What's the difference between PDF remediation and PDF accessibility testing?

Testing (or auditing) identifies accessibility issues. Remediation fixes them. Most organizations need both: an initial audit to understand the scope of the problem, followed by remediation to resolve it. Foresera does both — the platform scans for issues and remediates them in a single workflow.

Does remediation change how the PDF looks?

No. PDF remediation adds invisible structure to the document — tags, reading order, metadata — without changing the visual layout. The document looks identical to sighted users while becoming fully navigable for assistive technology users.

What if my PDFs are scanned images?

Scanned PDFs require OCR (optical character recognition) before they can be remediated. OCR converts the image of text into actual text characters, which can then be tagged and structured. Most modern remediation tools, including Foresera, handle OCR as part of the pipeline.

Is automated remediation as good as manual?

For the vast majority of documents, yes. Foresera achieves a 98% remediation rate across 85+ WCAG checkpoints. The 2% of edge cases that require human review are typically documents with unusually complex layouts or specialized content. For organizations with thousands of documents facing a deadline, automated remediation delivers the best balance of quality, speed, and cost.