To remediate a confidential PDF without uploading it, use software that runs the tagging, OCR, and validation on your own machine, confirm that claim with a harmless test file, and keep your review records under the same controls as the document. Accessibility work still has to be done in full. Only the place it happens changes.
Decide whether the document really needs it
Hosted tools are often the right choice, and many offer contractual and security controls that suit sensitive work. Local processing makes the most sense when one of these applies:
- A contract, data agreement, or policy limits which processors can receive the file.
- The document is unreleased, such as a draft filing, results not yet public, or material under embargo.
- It holds personal, health, student, or financial information and no approved vendor covers it.
- Your security review for a new processor would take longer than the deadline allows.
Ask your privacy or security owner rather than guessing. This guide is not legal advice, and what counts as a permitted transfer depends on your agreements and jurisdiction.
Check what a local claim actually means
A desktop app is not automatically local. It may call an online service for OCR, for AI descriptions, or to report errors. Before you trust a tool with a sensitive file, work through these checks using a document that contains nothing private.
| Check | How to do it | What you are looking for |
|---|---|---|
| Documentation | Read the privacy policy and data flow notes | A plain statement of what leaves the device, including diagnostics |
| Network activity | Process a test file with a network monitor running | No connections that coincide with opening or processing the document |
| Offline behavior | Disconnect from the network and run the same job | Features that stop working reveal what depended on a service |
| Optional features | List anything that uses AI, OCR, or sync | Each one is either on-device or clearly labeled and can be turned off |
| Storage | Find where projects, caches, and temporary files are kept | Encryption, and a way to delete working copies |
Clean the file as well as the workflow
Keeping a PDF on one machine does not make it safe to publish. It can still hold author names, comments, earlier text, and content hidden behind an image. Inspect it before release using a process like the one in Adobe's sanitization guidance. Visual covering is not redaction, as our redaction guide explains, and tags or replacement text can repeat information that you thought you had removed.
Keep the evidence private too
Remediation produces its own sensitive material: reports that quote headings, alternative text, review notes, and support logs. Store these under the same rules as the document. If you send a diagnostic file to a vendor, read it first and confirm that it contains no document text. Working copies left in a downloads folder undo the benefit of a careful process.
Remember what local processing does not change
The legal and practical accessibility requirements are the same wherever the work happens. A local tool has no better judgment about meaning than a hosted one. You still need correct structure, a validated output, and a person who reviews it against WCAG and tests it with assistive technology. For readers with private documents, also think about how they receive the accessible version, not just how you made it.
Frequently asked questions
Can PDF accessibility remediation be done completely offline?
Yes, if the tool runs tagging, OCR, and validation on the device. Some apps still need the network for activation, updates, or optional AI features, so check what each one does. Disconnecting from the network and repeating a job with a test file is a quick way to find out.
Is a local tool more compliant than a cloud tool?
Not in itself. Local processing changes who receives the file, which can matter for privacy and contracts, but it says nothing about accessibility quality. A hosted service with the right agreements can also be an acceptable choice, so follow your organization's own review process.
How can I verify that an app does not upload my document?
Read its documentation, then process a harmless test file while a network monitor runs, and look for connections at the moment you open or process the document. Repeat the job offline to see which features stop working. On macOS you can also inspect an app's signed entitlements.
Do I still need human review if the work stays local?
Yes. Automated checks cannot tell whether a description is accurate or a reading order makes sense. Only the location of the work changes, so have someone qualified review the document, and keep that person's notes under the same controls as the file itself.
Sources
The statements above rest on the primary sources below. Where a source is a law or standard, the version and date named in the text are the ones checked on the review date. This guide is general information, not legal advice.
- Adobe: Sanitize PDFs . Hidden information a PDF can carry and how it is removed.
- Apple: Vision framework documentation . On-device text recognition available to Mac apps.
- W3C: PDF techniques for WCAG 2.2 . The accessibility techniques that still apply to local work.
Keep reading
How to tag a PDF on a Mac
Preview cannot edit PDF tags. Here is how to tag a PDF on a Mac: fix the source if you can, choose a tool that edits structure, then review order, tables, and alternatives.
Read the guide →How to validate PDF/UA on a Mac with veraPDF
Check a PDF against PDF/UA on a Mac with veraPDF, read the failed rules, understand what a pass does and does not prove, and test the rest with VoiceOver and a person.
Read the guide →