PDFCarry

The client sent a new version. Which checks still stand?

PDFCarry carries your PDF accessibility work forward. When the client's revision arrives, it keeps the checks you already justified where nothing they depend on has changed, reopens the changed or uncertain ones for fresh review, and exports the evidence with the file.

Try the interactive example Get the synthetic sample PDFs

Private preview of a local Windows application. Nothing is for sale yet; the planned offer is described under Availability.

One number changes. Five checks keep their evidence. Two reading-order checks reopen; the changed paragraph needs three new checks. A synthetic example, not a customer result.

See it happen on a synthetic example

Two fixed examples generated from verified engine runs. This runs in your browser on prepared data; it does not process a PDF, and nothing you type leaves the page.

Example

    The document

    Items and their checks

      ✓ reviewed on this version ✓ reviewed earlier, still applies ! reopened – not yet reviewed

      Baseline

      Who it is for

      People who review the same documents more than once: independent remediators with returning clients, small agencies handling recurring reports and guides, and in-house teams that publish revised editions. If a document is remediated once and never comes back, PDFCarry has little to offer.

      It is not a general PDF editor and does not replace one.

      Alongside your editor

      You keep remediating in the tools you already use. PDFCarry sits beside them and looks after the record.

      • Import the reviewed baseline and record which checks you completed, per item, under your own name.
      • Import the client's revision. Checks whose content and context are unchanged keep their evidence. Changed or uncertain checks need fresh review, with the reason shown.
      • Fix titles, language, descriptions and text roles in the app, or download the file, edit it elsewhere and reimport it.
      • Export the PDF with a manifest of every check, who recorded it, when, and on which version.

      Nothing is ever approved on your behalf. Saving a correction, importing a file or passing a machine check never records a review.

      What it supports today

      The envelope is deliberately narrow and stated plainly. Outside it, the app refuses rather than guesses.

      Handled in the app

      • Born-digital PDF 1.x up to 50 MB, 200 pages and 20,000 structure elements.
      • Tagged and untagged revisions with ordinary text, images, web links, supported drawings and grouped graphics.
      • Complete, uniquely matched simple tables and lists.
      • Corrections to text roles, title, language, image descriptions and link descriptions. Supported graphics without text can be marked decorative; appearance stays unchanged.
      • Immutable version history, scoped review records, reimport from an external editor, machine validation, and ZIP export of PDF plus evidence.

      Needs an external editor

      • Scanned documents.
      • Encrypted or signed files, interactive forms and XFA, PDF 2.x, and unsupported encodings.
      • Complex or changed tables, mixed or stream-scoped structure, and content the engine cannot bind with confidence.
      • Untagged grouped graphics that contain text.
      • Recompressed files, changed resources or broad page dependencies may conservatively reopen review.

      A validator pass covers the machine-checkable PDF/UA-1 rules. It is not accessibility certification and not a substitute for the checks you record.

      How it runs

      Where
      On your Windows computer, as a local application. The PDF engines and the validator are bundled; there is no cloud account and no document upload.
      Your data
      Projects, versions and review records live in one data folder on your machine. Quit the app before copying the data folder to make a backup.
      Originals
      Every file you import is kept exactly as received. Corrections create new versions; nothing is overwritten.
      Evidence
      Reviewer names are local labels, recorded with each check. They are not authenticated identities, and the export says so.
      Now
      An unsigned test-mode build. Its installer passed installation, real PDF work, restart, update and uninstall on the development machine and on a fresh hosted Windows Server runner. Trusted public distribution is still to come, so there is no download yet.

      Availability

      PDFCarry is in private preview. Customer trials and purchases are not open yet. Release details will appear here.

      Try the interactive example and sample files while we prepare customer trials. PDFs will be processed locally in the Windows app. The customer guide describes the first revision, the trial and the licence as built.

      Planned early-access offer

      US$349 per reviewer, per year

      with a 14-day full trial and no card required to start.

      This is the offer we intend to test at release. It is not for sale today and may change before it is.

      Synthetic sample PDFs

      The first pair changes an amount from 100 to 900. The control pair keeps the same visible content; its incoming heading tag is restored during transfer.

      Generated for testing. They contain no customer content and no personal data. Sample provenance and embedded font licence.