To validate PDF/UA on a Mac, run a copy of the file through a validator such as veraPDF, choose the PDF/UA profile that the document claims, and work through the failed rules grouped by cause. Then review what a machine cannot judge. The validator tells you where the file breaks the testable rules, and only a person can tell you whether the document makes sense.
Pick the right profile
PDF/UA has two parts. PDF/UA-1 is based on PDF 1.7, and the PDF/UA-2 overview describes the newer part, which is based on PDF 2.0. Test against the one you are targeting. Changing a metadata claim does not upgrade a file, and a validator will report a mismatch when a version claim and the file do not agree. Our PDF/UA-2 guide goes further on choosing between them.
Run veraPDF from the command line
veraPDF has a graphical interface and a command-line tool, and its validation documentation lists the options. A typical run on a copy of a file looks like this:
verapdf --flavour ua1 --format text report.pdfUse ua1 or ua2 to match your target. Text output is handy for a quick look, while XML or JSON suits a saved record. veraPDF needs Java, so if you would rather not manage that yourself, use an app that bundles it. DocAccessible for Mac includes veraPDF and runs it on a separate output file.
Read failed rules by cause
A long report does not always mean a long job. Rules refer to clauses in the standard, and the Matterhorn Protocol groups PDF/UA failure conditions into checkpoints in plainer language. Start with whatever could be causing many of the others.
| Failure | What it usually means | First response |
|---|---|---|
| Missing PDF/UA identification | The file does not declare the standard | Add it only when you intend to make the claim, after the other work |
| Content neither tagged nor an artifact | Some of the page was missed | Tag the content, or mark true decoration as an artifact |
| Figure without alternative text | An image has no description | Have a person write one, or mark decoration as an artifact |
| Font not embedded or no Unicode mapping | Text cannot be reliably rendered or read | Export from the source with embedded fonts, or repair the mapping if supported |
| Annotation not tagged | A link, field, or comment sits outside the structure | Associate it with the tag tree, or remove what should not be there |
Know what a pass does not prove
A file can pass every machine rule and still fail its readers. The validator can see that a figure has alternative text, but it cannot see that the text says 'image1'. It can see a heading tag, but it cannot tell you the heading is the wrong level, or that the reading order runs across two columns. The Matterhorn Protocol marks many of its failure conditions as requiring human judgment for this reason. Record machine results and human findings separately, as described in our testing guide, so that nobody reads one as the other.
Finish with a screen reader
- Turn on VoiceOver and read the document from the start without looking at the screen.
- Use its rotor to move by headings, links, and tables, and check that each list makes sense.
- Tab through any form and listen for each label, required state, and hint.
- Open the file in the viewer your readers actually use, because results can differ between viewers.
- Test with JAWS or NVDA on Windows if your audience relies on them, since a Mac cannot show you those results.
Frequently asked questions
Does veraPDF work on a Mac?
Yes. veraPDF is a Java application with graphical and command-line interfaces that runs on macOS, and you need a suitable Java runtime unless it comes bundled with another app. DocAccessible for Mac, for example, includes both, so there is nothing separate to install.
If veraPDF passes, is my PDF accessible?
Not necessarily. A pass means the file met the rules a machine can test for that profile. It cannot confirm that headings, reading order, table relationships, or descriptions are right. Treat it as one piece of evidence, and add human review and screen reader testing.
Can I run PAC on a Mac?
PAC is built for Windows, so on a Mac you would need a Windows machine or virtual environment to run it. veraPDF runs natively on macOS. The two tools do not always report the same results, so if a customer asks for a PAC report, run PAC itself rather than assuming a veraPDF pass will match.
Which should I test, PDF/UA-1 or PDF/UA-2?
Test the part your document targets. PDF/UA-1 is based on PDF 1.7, and PDF/UA-2 on PDF 2.0, so the file's version needs to match. Most existing workflows and requirements still refer to PDF/UA-1, but check what your contract or policy actually asks for before you choose.
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.
- veraPDF . The open-source validator used in this guide.
- veraPDF: Validating from the command line . Options for profile selection and report format.
- PDF Association: Matterhorn Protocol 1.1 . PDF/UA failure conditions, including those that need human judgment.
- PDF Association: PDF/UA-2 overview . How the newer part of the standard relates to PDF 2.0.
- Apple: VoiceOver User Guide for Mac . Testing with the screen reader built into macOS.
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 test a PDF with a screen reader
A repeatable screen reader test for PDFs with NVDA, JAWS, or VoiceOver: which viewer to open the file in, the keystrokes to use, what to listen for, and independent data on which viewers expose tags.
Read the guide →