PDF Accessibility Tools: Four Categories Compared

Updated · 4 min read

On this page
  1. The four kinds of PDF accessibility tools
  2. What each category is actually for
  3. What to look for before you buy
  4. What a “PDF/UA ready” claim is worth
  5. Where TagRight fits

PDF accessibility tools fall into four categories, and which one you need depends on whether you are creating a document, checking one, or repairing one you did not author. Choosing wrong is common: people buy a checker expecting a fixer and find out on deadline that it only tells them what is broken. Here is what each category does, what to look for, and what a “PDF/UA ready” claim is worth.

The four kinds of PDF accessibility tools

Authoring tools produce a tagged PDF when you export. Microsoft Word, Google Docs and Adobe InDesign all have an export path that writes structure into the file. They are the best route when you control the source, because the structure is correct at the moment of creation.

Checkers and validators read a finished PDF and report problems. PAC 2024, veraPDF and Adobe’s free online checker live here. They are accurate and, in the case of PAC and veraPDF, standards-based. They do not change the file.

Remediation tools write tags into a PDF you already have. Adobe Acrobat Pro is the reference example, with its automatic tagging, reading order tool and tags panel. This is the category for the files nobody can re-export.

Browser-based fixers do a narrow slice of remediation without installing anything: you upload a file and download a tagged copy. TagRight sits here, and so do a few generic converters.

What each category is actually for

CategoryJob it doesExamplesDoes it repair a PDF you did not author?
Authoring exportWrites tags at creationWord, Google Docs, InDesignNo, it needs the source
Checker / validatorReports what is wrongPAC 2024, veraPDF, Adobe online checkerNo
Remediation toolWrites tags into an existing fileAcrobat Pro, dedicated suitesYes
Browser-based fixerUpload, tag, downloadTagRight and similarYes, with limits

The free landscape is almost entirely checkers. That matters because the PDF accessibility checker category is what ranks, and a coordinator who searches for a tool often lands on a checker without realising the fixing half is missing.

What to look for before you buy

Four questions separate a useful tool from a frustrating one.

First, does it fix or only report? If it only reports, you still need a route to repair, whether that is a remediation tool or a human.

Second, what does it do with images? Automatic tagging cannot write meaningful alternative text, because a machine cannot know what a photo conveys. A good tool flags images for a human instead of inventing descriptions.

Third, how does it handle scans? A scanned page with no text layer cannot be tagged until it has been through OCR, and OCR output needs correction. A tool that claims otherwise is overpromising.

Fourth, does it produce a report you can keep? For compliance work, a record of what was done and what was left for a human is as valuable as the tagged file, because it is what you show when someone asks.

A fifth question is whether the tool speaks to the standard you are actually held to. A tool that checks PDF/UA is useful if your obligation is a PDF/UA audit, but if your rule names WCAG, you want one that maps to the success criteria in WCAG PDF. The two overlap, and knowing which your auditor cites keeps the report you save relevant.

What a “PDF/UA ready” claim is worth

PDF/UA is ISO 14289, and the failure conditions are catalogued in the Matterhorn Protocol. A tool that says it is “PDF/UA ready” is claiming its output can conform. Treat that as a question rather than a promise. Ask which validator the vendor tests against, and verify a sample yourself with veraPDF or PAC 2024 before you commit.

A worked example shows why this matters. A school district uploads a 30-page policy document with a two-column layout. The tool tags it, but the reading order runs across the columns instead of down them. The file is tagged and still unusable. A validator catches the reading-order failure; a plain “tagged” badge does not. The lesson is that automatic tagging always needs review, and the Acrobat accessibility checker or a free validator is how you do that review.

Where TagRight fits

TagRight is a browser-based fixer. You upload an untagged PDF and get back a copy with a real structure tree, correct reading order, the document language, a title, and the MarkInfo and DisplayDocTitle flags, plus a plain report naming the heading outline it inferred and everything it could not fix. It does not write alt text, does not support interactive forms, and cannot tag a scan with no text layer, and it says so rather than pretending.

It is a remediation aid and a triage tool, not a PDF/UA certification, so verify anything that has to pass an audit. That honesty matters, because a tool that overpromises costs you time you do not have when a deadline is close. If you want the categories compared against real jobs and real prices, see PDF accessibility without Acrobat, and if you are weighing a paid tool against doing it in-house, remediate PDF walks through the manual route. You can start with a free document; the plans and pricing are a fraction of a desktop suite.

Frequently asked questions

What is the difference between a PDF checker and a PDF fixer?

A checker reads a PDF and reports what is wrong, such as missing alt text or an untagged table. A fixer writes the tags and structure back into the file. Most free tools are checkers, and that is the single most common buying mistake.

Are free PDF accessibility tools enough?

For checking, yes. PAC 2024 and veraPDF are accurate validators. For fixing a PDF you did not author, no free tool writes reliable tags into it. You either export from the source document or use a remediation tool.

Does exporting from Word make an accessible PDF?

It makes a tagged PDF, which is a strong start, but only if you still have the source and the document was structured well. Most PDFs a coordinator receives, such as scans and vendor files, have no source to go back to.

What does PDF/UA ready mean for a tool?

It should mean the tool produces output that conforms to ISO 14289 and passes a validator such as veraPDF. Treat the claim as a question, not a promise: ask which validator they test against, and verify the output yourself.

Can one tool do authoring, checking and remediation?

Adobe Acrobat Pro can, which is why it costs $19.99 a month and has a learning curve. Most other tools do one job well and are best combined with a validator.

Tag a PDF free