Equidox
Cloud PDF remediation service: upload a document, tag it in a browser with automated detectors, export accessible PDF, HTML or ePub.
Jobs Accessibility
Opens the vendor's own site.
Jobs covered
Open a task to see exactly what the vendor documentation supports.
Accessibility
Browse all accessibility toolsremediating an existing PDF for accessibility with Equidox Software, using the AI Smart Zone Detector to detect and tag text and headings, the List Detector for lists including nested lists and the Table Detector for rows, columns and complex cell structures, correcting reading order with the one-click re-order tool, adding image alt text or marking decorative images as artifacts, entering form field tooltips in the Form Pane, and checking the structure in an HTML preview before export, with the software available as cloud SaaS for PC or Mac or as an on-premises web appliance
Where your files are processed
Files leave your device
We observed a file upload to app.equidox.co. This covers the web service. We have not checked desktop app processing or self-hosted instance, and we do not extend the finding to them.
The default deployment is a hosted SaaS application, and both sides of the flow happen on Equidox's infrastructure: the user guide states Equidox is a cloud-based application where all remediation is done online and the FAQ states original PDF documents are stored in a Google Storage instance in Google regional data centres. Documents are selected with the browser's own file picker, which is why the upload host is recorded from the application URL the vendor publishes rather than from a documented API endpoint.
There is one genuine exception, sold separately: an on-premises edition ships as a virtual appliance - a pre-configured Linux .ova image for VMware or VirtualBox - which runs the core application, the AI engine and the datastore inside the customer's own network with no cloud dependencies and no internet access required. That deployment is self-hosted, not local-processing on a desktop.
What it does
Equidox is a hosted PDF remediation tool: you upload a PDF to its cloud application, and it uses computer vision and machine learning to detect text zones, headings, lists, tables, images and form fields, which you then confirm or correct in the browser. It exports tagged, accessible output as PDF, HTML or ePub, and its HTML preview shows how a screen reader would read the page so the reading order can be checked as you work.
A separately sold on-premises edition runs the same application, its AI engine and its datastore as a Linux virtual appliance inside the customer's own network, and Equidox AI offers fully automated batch remediation of templated documents.
Best for
Accessibility and compliance teams that need a browser-based, collaborative remediation tool staff can learn quickly, and organisations with a steady flow of similar documents such as statements, invoices or provider directories.
Worth knowing
In the default cloud deployment your document leaves your network: the vendor's user guide says remediation is done online, and the FAQ says original PDFs are stored in a Google Cloud Storage instance, hosted in Google regional data centres in Iowa, Las Vegas, South Carolina or Montreal. The company publishes no retention period and no automatic deletion guarantee - it says stored files may be archived or backed up and can be destroyed on request, with deletion driven by a written request rather than by a timer, so treat retention as something to settle contractually before uploading confidential documents.
The remedy is the on-premises .ova appliance, which the vendor sells on the promise that no data leaves your network, but that is a second deployment rather than a setting.
Details, and where each comes from
Vendor statements, our own reading of their pages, and the things nobody has established yet, each answered separately. Where we have not confirmed something it says so rather than guessing, and a row nobody has established is greyed out.
- Versions covered
- Web · Windows · macOS · Linux · Self-hosted
- Website
- equidox.co
- Requires an account
- Yes
- Free tier
- No
- Watermark on trial output
- Not verified
- Maximum file size
- Not verified
- Batch processing
- Yes
- Data residency
- Multiple regions
- Open source
- No
- Self-hostable
- Yes
- Licence
-
commercial
commercial; annual subscription with concurrent-user licensing, or an unlimited organisation-wide licence; SaaS or on-premises virtual appliance
- Redaction
- No redaction feature
- Programmatic access
- Browser JavaScript · HTTP API
- Last availability check
- Responded in 333 ms 21 October 2026
Checked automatically by our own runner, not reported by the vendor. 100% of our last 30 checks got a response.
What the redaction verdict rests on
From the vendor's own documentation, read 22 September 2026. Not tested by us.
What that does not establish
The vendor’s own site was read on 22 September 2026 and contains no mention of redaction, sanitisation, blackout or whiteout. Absence from a vendor’s own material is not proof that a feature does not exist - it may be undocumented, or on a page the reading did not reach - but for a NEGATIVE claim it is the strongest evidence available, and it is weaker than a positive quote.
Recorded as such rather than presented as certainty.
What the vendor says
Claims are labelled rather than repeated as fact. Where we have checked something ourselves, it says so and shows when. Checked means we read the vendor's own page and it says what we recorded - not that we tested the behaviour, unless the note says we did.
-
“Original PDF documents are stored in a Google Storage instance. These files may be "archived," or "backed-up," but can also be destroyed, upon request. The Equidox Google (GCP) instance can be deployed in regional data centers: Iowa, Las Vegas, South Carolina, and Montreal in Canada.”
Checked by us - the source says this Read 22 September 2026
Confirmed verbatim: the three sentences of the claim appear as three consecutive lines, unaltered. The retention fact a reader needs is in the middle sentence, and it is a weak promise rather than a policy: original PDFs sit in a Google Storage instance and "may be 'archived,' or 'backed-up,' but can also be destroyed, upon request".
There is no automatic expiry anywhere in the statement, so files persist until somebody asks - the opposite of the bounded-window claims elsewhere in this tier. The third sentence is also easy to misread as a location guarantee, and it is not one: the Google instance "can be deployed in regional data centers" in Iowa, Las Vegas, South Carolina and Montreal, which describes what is offerable rather than where a given customer's documents are, and no European region is named at all.
Recorded as the vendor's description of a commercial accessibility remediation service; we have not submitted a document and no control was run.
Standing: Re-read and matched byte for byte
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- d66148163b21ee57d241e899a325bcf0c36e0794989988964ce6e7955cca1359
How we checked
Re-verified verbatim on 2026-09-22: https://equidox.co/resources/accessibility-education-tools/faq/ re-rendered in headless Chrome with scripts/render-page.mjs and the claim's wording found in the rendered text. Originally verified on 2026-09-21. sourceHash is the SHA-256 of the re-rendered text, held as rv-equidox-co-resources-accessibility-education-tools-faq-ac532898.txt.
-
“Equidox AI is a fully automated PDF accessibility solution for high-volume, templated documents that is cost-effective, accurate, and produces fully accessible and compliant PDFs with no human intervention.”
Checked by us - the source says this Read 22 September 2026
Confirmed, with a wording note because the claim is our paraphrase rather than the vendor's sentence. The page says "Equidox AI is a fully automated accessibility solution for templated PDFs" and, in a later paragraph, "produces fully accessible and compliant PDFs with no human intervention".
The claim renders that as "a fully automated PDF remediation solution for high volumes of templated documents" and "eliminating the need for human remediators". Corrected on 2026-09-21: the claim used to be our paraphrase, joining "remediation solution" to "eliminating the need for human remediators", and it now quotes one of the vendor's sentences in full.
Three claims in this index carried our wording instead of theirs - this, Scanner Pro and PDFsam - and all three now quote what the vendor wrote.
Standing: Re-read and matched byte for byte
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- fc7265170908dd7ff105c56f9158d14b2fdc85034b4fc320c57ca4ab02a647a7
How we checked
Re-verified verbatim on 2026-09-22: https://equidox.co/pdf-solutions/high-volume-solutions/ re-rendered in headless Chrome with scripts/render-page.mjs and the claim's wording found in the rendered text. Originally verified on 2026-09-21. sourceHash is the SHA-256 of the re-rendered text, held as rv-equidox-co-pdf-solutions-high-volume-solutions-ef37ec8e.txt.
-
“Equidox's upload process is encrypted using Google Standards SHA-256-RSA Data stored in Google Cloud Storage is encrypted using Advanced Encryption Standard (AES) in Galois/Counter Mode (GCM) Storage Device data is encrypted with AES128 for hard disks (HDD) and AES256 for solid-state drives (SSD)”
Checked by us - the source says this Read 22 September 2026
Confirmed verbatim: the three lines appear consecutively and unaltered, covering upload encryption, encryption of data in Google Cloud Storage, and disk encryption at rest. One line deserves a plain note because it is the one a technical reader will stumble on.
"Equidox's upload process is encrypted using Google Standards SHA-256-RSA" describes a hash-and-signature construction rather than a bulk cipher, so as written it reads as a statement about the TLS configuration of the upload rather than about any scheme Equidox applies; the actual at-rest claims are carried by the two lines that follow, AES in Galois/Counter Mode for Cloud Storage and AES128 for hard disks against AES256 for solid-state drives.
Those are consistent with Google Cloud's documented defaults and the page itself defers to Google's compliance page rather than to an audit of Equidox's own, which is the honest reading: the encryption described is mostly the platform's, not a measure the vendor has demonstrated. Recorded as the vendor's wording; nothing here was tested and no control was run.
Standing: Re-read and matched byte for byte
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- d66148163b21ee57d241e899a325bcf0c36e0794989988964ce6e7955cca1359
How we checked
Re-verified verbatim on 2026-09-22: https://equidox.co/resources/accessibility-education-tools/faq/ re-rendered in headless Chrome with scripts/render-page.mjs and the claim's wording found in the rendered text. Originally verified on 2026-09-21. sourceHash is the SHA-256 of the re-rendered text, held as rv-equidox-co-resources-accessibility-education-tools-faq-ac532898.txt.
Each claim is quoted from the vendor's own pages. This section describes what we have and have not checked - it is not a judgement about anyone.
Sponsorship is distribution, not an endorsement or a promise of search rankings, AI citations, traffic, or sales. This listing is a free entry, compiled from published sources.
Related reading
- Checking a PDF for accessibility - what makes a PDF accessible, and how it is checked.