PDF Remediator

About

PDF Remediator is an assisted accessibility remediation copilot. Upload a PDF to get an automated first pass, clear remediation-mode labeling (content-bound vs analysis-only), and guided next steps for final manual validation before publishing. It is designed to streamline the work you do before final QA in Acrobat or PAC, not replace that desktop handoff.

Release Notes

Updated with each deployment to summarize shipped enhancements and quality improvements. The newest entry reflects what is in the current build.

Release 2026.03.10 (March 10, 2026)

Build stability issues were fixed and the remediation workflow now reports real user progress more accurately.

  • Fixed report generation helpers so optional veraPDF summary data no longer trips TypeScript in manual next steps or revision-delta comparisons.
  • Changed the veraPDF API route max duration export to a static literal so Next.js recognizes the route config during production builds.
  • Changed the remediation workflow so Step 1 completes only after the user actually downloads the remediated PDF instead of merely landing on the compare screen.
  • Kept every remediation step openable even when the user has not completed prior steps, so the workflow recommends order without hard-gating navigation.
  • Retitled browser-based planning steps so the UI distinguishes in-app preparation from the actual Acrobat or PAC edits that still happen outside the app.
  • Updated the workflow and state panels to prioritize download first, then in-browser review, before alt-text, structure, re-validation, and publish guidance.

Release 2026.03.09 (March 9, 2026)

Scanned-PDF OCR is more reliable and the uploaded-file report now explains when OCR affected remediation.

  • Aligned browser OCR timeouts with the longer server OCR processing window so large scans are less likely to fail early.
  • Added post-OCR validation so a returned PDF only counts as OCR-applied when it actually exposes usable searchable text.
  • Fell back to local browser OCR when upstream OCR output cannot be parsed or does not improve text extraction.
  • Added original-report messaging so OCR activity is visible even though the uploaded-file baseline still shows the source PDF.
  • Removed redundant explanatory copy from the accessibility status banner so the status chips carry the detail.
  • Stopped draft-edit persistence from rewriting large PDF assets on every keystroke so alt-text entry stays responsive.
  • Removed the redundant red accessibility status banner from the report screens so the workflow-state panels remain the primary status surface.
  • Hardened veraPDF integration with Render wake-up handling, API retries, and clearer verdict fallback when the service returns incomplete metadata.

Release 2026.03.08 (March 8, 2026)

The Upload PDF screen is easier to clean up after repeat runs, failed attempts, and revised validations.

  • Moved the newest uploaded PDFs to the top of the Upload PDF list.
  • Added Remove from list actions for completed remediated PDFs so saved reviews can be cleared from this browser.
  • Added Remove from list actions for failed uploads marked Needs attention.
  • Removing a saved upload also clears linked revised uploads from the local Upload PDF list to avoid orphaned entries.
  • Hardened PDF byte handling so scanned uploads stay reusable across parse, OCR, remediation, and verification steps.

Release 2026.02.25 (February 25, 2026)

Scoring and remediation outputs are now more conservative and easier to trust.

  • Added score guardrails so critical structural risks cannot be reported as fully accessible.
  • Added explicit remediation mode labeling: content-bound vs analysis-only.
  • Added source-type assessment to flag checker/report artifacts vs source content PDFs.
  • Added Structural Integrity, Alt Text, and Manual Structure workspaces on compare view.
  • Added QA Evidence Pack export for audit-ready before/after reporting.
  • Moved to compact immutable remediation metadata to reduce second-pass drift.
  • Hardened table and image heuristics to reduce synthetic structures and better flag true image elements.
  • Expanded regression coverage with PDF Accessibility agent fixture checks.

2-Minute Quick Start

  1. Go to the App page and upload your PDF.
  2. Wait for the review to finish (usually under a few minutes, depending on file size).
  3. Download the remediated PDF.
  4. Use the “What To Do Next” checklist to complete remaining manual fixes.
  5. Re-upload the revised PDF for a final validation check before publishing.

What This Tool Is Best For

  • Fast first-pass remediation of common PDF accessibility issues.
  • Identifying where manual edits are still required before publication.
  • Reviewing updated output and QA evidence before handoff to Acrobat or PAC.
  • Reducing remediation effort while keeping humans in control of final compliance decisions.

What Happens After You Upload

The app runs a step-by-step workflow and shows progress as each phase completes:

  1. Read the file — Reviews text, headings, links, forms, and metadata.
  2. Read scanned pages — If the PDF is image-based, OCR is used to add searchable text.
  3. Check for issues — Looks for common problems in headings, images, tables, lists, links, and form fields.
  4. Fix what it can safely — Applies supported automatic fixes and builds an updated PDF.
  5. Check again and compare — Runs the checks again and shows before/after results side by side.
  6. Set remediation mode — Marks output as content-bound when structural bindings are reliable, or analysis-only when manual structural tagging is still required.
  7. Optional standards check — If veraPDF is enabled in your environment, the app runs an additional standards check.
  8. Next steps — Produces a practical checklist of remaining manual fixes.

Accessibility Features Applied

  • Preserves and evaluates document tag structure, then flags where manual tag repair is required.
  • Detects unbound structure conditions and prevents those files from being treated as fully remediated.
  • Updates language and file details used by accessibility tools.
  • Keeps or creates bookmarks from detected headings when possible.
  • Rewrites vague link text (like “click here”) to clearer wording.
  • Adds missing form labels based on field names when possible.
  • Detects real PDF image content from page rendering data and flags missing alt text.
  • Stores compact immutable remediation metadata to improve repeat-run consistency.
  • Adds searchable text support for scanned PDFs.
  • Tries to improve reading order in some multi-column layouts.
  • Checks the updated file again and shows a before/after comparison.

How To Interpret Results

  • Automated baseline reflects this app's internal checks, not a legal/compliance guarantee.
  • veraPDF status is an independent external PDF/UA technical verification when enabled.
  • 100% is only shown for remediated output when critical internal findings are clear and external verification is compliant.
  • Unbound structure detection applies a strict score ceiling and routes output to analysis-only mode.
  • Analysis-only mode means manual structural tagging remains required before release.

What You Should Still Review Manually

  • Heading order and document structure in long or complex files.
  • Table headers, merged cells, and reading order in complex tables.
  • Meaningful alt text for charts, diagrams, and instructional images.
  • Color contrast and visual-only cues that automated checks may miss.
  • Final usability with assistive technology before publishing.

Privacy

This app is browser-first: uploaded PDFs are processed in your browser session by default, and the app does not store files in an app database.

  • Files stay in browser memory during your session and are cleared when you refresh or close the page.
  • If an OCR backend is configured, the file is sent through /api/ocr and forwarded to that OCR service.
  • If backend OCR is unavailable, local OCR fallback can run in your browser using Tesseract.
  • If veraPDF verification is enabled, the remediated PDF is sent through /api/verapdf and forwarded to the configured veraPDF service.
  • When you export a remediated PDF, worksheet, or evidence pack, it is downloaded locally to your device.

Limitations

Automatic fixes can solve many common issues, but they do not guarantee full WCAG or PDF/UA compliance. Some checks are best-effort only (especially color contrast, infographic layouts, and complex tables), and many files still need manual edits. If content-bound structural tagging cannot be verified, the output is treated as analysis-only. If veraPDF is enabled, it adds an independent technical check, but you should still complete manual review with desktop tools and assistive technology before publishing.

Start remediating