Allyant PDF Validator
Free Acrobat plug-in accessibility checker that tests a PDF against WCAG and PDF/UA and guides manual testing.
Jobs Accessibility
Operated by Allyant
Opens the vendor's own site.
Jobs covered
Open a task to see exactly what the vendor documentation supports.
Accessibility
Browse all accessibility toolsvalidating PDF accessibility as an Adobe Acrobat plugin that reports issues and guides manual tests, covering tagging and reading order, alternative text, headings, lists, links, form tags, tooltips, tables, metadata, font embedding and Unicode mapping, with the vendor naming Section 508, WCAG, PDF/UA and HHS guidelines, on Windows with Acrobat Standard or Pro X or higher
Where your files are processed
No server involved
An Acrobat plug-in: the document is opened and checked inside your own copy of Acrobat, on your own machine. The form the vendor requires gates the download and collects contact details, not the document.
An Acrobat plug-in: the document is opened and checked inside your own copy of Acrobat, on your own machine. Nothing is uploaded, including when you request the download - though that request does collect your contact details, which is a different kind of data leaving and is recorded in watchOutFor.
What it does
A free plug-in for Adobe Acrobat that checks a PDF's accessibility and then walks you through the parts a machine cannot decide. It reports on the mechanical failures - metadata, whether the title is visible, font embedding, Unicode mapping, tag nesting, heading levels, list and link tags, untagged content - but its distinct feature is the pairing of each finding with the document: selecting a tag highlights the content it applies to, and selecting content shows where it sits in the tag tree.
It produces a certification report for each document tested.
Best for
Accessibility specialists and document authors who have to sign off a PDF and want the check and the evidence in one place. It is also the sensible free starting point for an organisation that has Acrobat already and needs to know how bad a document is before paying anyone to fix it.
Worth knowing
It is Windows only, and it runs inside a paid Adobe Acrobat rather than standing alone. The vendor's download page describes it as an Acrobat Pro plug-in, while the system requirements on the same site list Standard or Pro from Acrobat X (10) onwards; a current supported-version matrix would settle which of those holds, and until one is found the wider scope is unconfirmed.
The download is behind a form asking for a name, work email, phone number, job title and organisation. The phone field is not marked as required, so the named fields are not all mandatory.
A plug-in architecture is not by itself proof that nothing is sent anywhere during normal operation: the documented workflow is what we can describe, and no independent network test backs an absolute claim either way.
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
- Windows
- Website
- allyant.com
- Requires an account
- Not verified
- Watermark on the free tier
- Not verified
- Maximum file size
- Not verified
- Batch processing
- Not verified
- Data residency
- Self-hosted
- Open source
- No
- Self-hostable
- Yes
- Licence
- Free to download and use; requires Adobe Acrobat Standard or Pro on Windows
- Redaction
- No redaction feature
- Programmatic access
- None
- Last availability check
- Responded in 166 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.
“Our Adobe Acrobat Pro plugin, the Allyant PDF Validator, will test the accessibility of individual PDFs, identifying any issues that may be blocking users from access-and compromising your organization's compliance.”
What that does not establish
Recorded as `none` on absence: the tool's own feature list is entirely about examining a document - metadata, titles, fonts, Unicode mapping, tag structure, alternative text, untagged content - and nothing in it modifies or removes content. It inspects and reports.
What it does not establish: that nothing else in the Allyant suite edits documents. The same vendor sells remediation software and services, which are separate products and would need their own records.
https://allyant.com/free-pdf-accessibility-checker-validator/
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.
-
“And our PDF Validator is more than automated scanning. It will guide you through manual testing, giving you the confidence to meet the most stringent accessibility standards, like WCAG or PDF/UA, providing a certification report for each tested document.”
Checked by us - the source says this Read 1 October 2026
Confirmed. The quoted text appears in the rendered page as read on 2026-10-01.
This claim was carried as reported rather than checked until this read.
Standing: Not re-read against the live source
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- 23f8f06245cd29ac0bd2f8cbe6d70340be719eb67f543e7ed0c31dafa020d289
How we checked
Read as rendered text in headless Chrome on 2026-10-01 and saved to the evidence archive, so the read can be repeated against the same file. Comparison ignores case, punctuation and hyphenation, which is why "open-source" on the record matches "open source" on the page.
-
“Tag-based content highlighting: Easily highlight content in the PDF, and the PDF accessibility checker will immediately show you where that content is in the tags.”
Checked by us - the source says this Read 1 October 2026
Confirmed. The quoted text appears in the rendered page as read on 2026-10-01.
This claim was carried as reported rather than checked until this read.
Standing: Not re-read against the live source
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- 23f8f06245cd29ac0bd2f8cbe6d70340be719eb67f543e7ed0c31dafa020d289
How we checked
Read as rendered text in headless Chrome on 2026-10-01 and saved to the evidence archive, so the read can be repeated against the same file. Comparison ignores case, punctuation and hyphenation, which is why "open-source" on the record matches "open source" on the page.
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.
- Which PDF tools keep your file on your machine - what we count as processing on your own device.