PDF remediation software for universities and government agencies: what to buy before the ADA Title II deadline

If you run documents for a public university, a school district, a county or a state agency, the practical answer is this: buy per seat remediation software for the work you will be doing every month, and buy a per page service for the one time backlog. Of the vendors publishing prices on 29 August 2026, the per seat options are axesPDF at $650 per user per year and PDFix Desktop Pro at EUR350 per user per year, also listed as $599 USD, with a permanently free Lite edition for checking. The per page services that publish are Accessible.org at $7.50 to $11.50 and up and Accessiblu at $10, $15 or $18. Allyant CommonLook, Equidox and Continual Engine will not quote you without a call.

Before you spend any of that, read the section below on the pre-existing documents exception. It is written into the Department of Justice rule, most procurement teams have never heard of it, and on a typical university backlog it removes more documents than any tool will ever fix.

The deadline that sets the budget

The Department of Justice ADA Title II rule sets WCAG 2.1 Level AA as the technical standard for web content and mobile apps at state and local government entities. That includes public universities, community colleges, school districts, transit agencies, libraries and county services. PDFs published by a covered entity fall inside it.

The compliance dates were extended by an Interim Final Rule published on 20 April 2026. They now stand at:

• 26 April 2027 for entities serving 50,000 people or more.
• 26 April 2028 for entities under 50,000 and for special district governments.

Worth saying plainly, because it is costing people money: a great deal of the guidance still circulating online prints April 2026 as the deadline. Those articles were written before the extension. If a vendor is quoting urgency off the old date, they have not updated their materials, and that is a reasonable thing to ask about on a sales call.

What the extension actually bought you is a planning year. The agencies that use it to fix the systems producing their documents will spend far less than the ones that use it to remediate the same documents by hand a second time.

The exception that can cut your backlog

This is the part almost nobody scopes correctly, so it goes early.

The rule carries an exception for pre-existing conventional electronic documents. To qualify, a document has to meet both of these:

1. It is a word processing, presentation, PDF or spreadsheet file.
2. It was available on the entity's website or mobile app before the date that entity has to comply.

And then the limitation that decides most cases: documents currently being used to apply for, access, or participate in the entity's services, programs or activities are excluded from the exception even if they were posted years ago.

Read that against a real university and the shape of the project changes completely. A 2014 conference programme sitting in a departmental archive is very likely covered by the exception. The financial aid appeal form that students download and submit today is not, no matter when it was posted, because it is currently used to apply for a service. Neither is this year's course catalogue if students use it to register.

So the first task is not procurement. It is triage, in this order:

• Anything published after your compliance date. No exception applies. This is your permanent, recurring obligation, and it is the part worth automating.
• Pre-existing documents actively used to apply for or access services. Forms, applications, enrolment packets, benefit summaries, current catalogues. Remediate these.
• Pre-existing documents that are genuinely archival. Exception likely applies. Confirm it with counsel, then leave them alone and note the decision.

A backlog of 40,000 documents that gets sorted this way before anyone requests a quote is a different purchase from 40,000 documents priced at $9.50 a page. Vendors will price the whole pile at the same rate, including the part of it you were never required to fix, and they are not being dishonest when they do. You have to bring the triage.

One practical note on that triage. It spans departments that do not report to each other, it needs a named owner per bucket, and it competes with everything else on the same people's time, which is why it works far better run as a program with prioritized intake and real capacity planning across the departments doing the work than as a spreadsheet somebody updates when they remember. The remediation is the easy half. Knowing which 3,000 of the 40,000 documents to start on is the half that slips.

What the published prices mean at public sector scale

Four vendors in this category publish a number. Every figure below was read off the vendor's own website on 29 August 2026.

The trap here is treating $10 and $9.50 as the same purchase. They are not, and the reason is on our PDF remediation services and software page in full: Accessible.org prices by how hard your document is, while Accessiblu prices by how much you get. Accessiblu's $10 tier does not include alternative text. On an image heavy document, alternative text is most of the labour. Normalize the deliverable before you compare the rates, or you will pick the wrong supplier on a number that was never comparable.

Software or service: the math at public sector volume

The crossover is easy to compute and almost always misread.

On raw arithmetic, a $650 licence pays for itself against roughly 70 pages of outsourced work at $9.50. That makes the licence look obviously correct for any entity with a real backlog, and it is why so many public sector accessibility programs start by buying seats.

The part the arithmetic hides is that remediation is a skill. A capable person takes weeks to get fast and months to become genuinely reliable on nested tables, scanned forms and reading order in multi column layouts. The licence is cheap. The trained person is not, and in an environment with hiring freezes and staff turnover, the person is also the part you cannot guarantee.

So use cadence rather than volume as the tie breaker:

• A one time historical backlog with no ongoing production: buy the service. There is nothing to build a capability around.
• Steady monthly output across several departments: buy seats, train named owners, and outsource the overflow and the genuinely hard files.
• High volume generated output, such as statements and transcripts: neither. Fix the system that produces them, which is the next section.

Most public entities have all three at once, and the budget request that survives review is the one that separates them into three lines instead of one. If an outside firm is going to help you build that request, our guide to hiring an ADA compliance consultant for government and higher education covers what to require in the scope before you take a single call.

The documents you generate are a different problem

A significant share of what a university or agency publishes is not authored by hand at all. Transcripts, financial aid award letters, benefit summaries, enrolment confirmations, board packets exported from a reporting system, utility statements. These are produced by software, on a schedule, and they are regenerated every cycle.

Remediating those by hand is a recurring bill with no end. The file you fixed in September is replaced by a new file in October, and nothing you did carries forward. Put numbers on it: a 5,000 page catalogue of generated documents at $9.50 a page is about $47,500 once. Regenerate it quarterly and the same work is roughly $190,000 a year, permanently.

When the source is HTML your team controls, the accessibility of every future document is decided in the template. Real heading elements produce real heading tags. Table header cells with a scope attribute produce an associated header structure. An alt attribute becomes alternative text. A lang declaration becomes the document language. Fix that once, in a template that lives in version control and gets reviewed like the rest of the code, and every render from then on arrives structured. Our page on accessible PDF generation covers which rendering engines emit tagged output and which actually target PDF/UA, because those are not the same claim.

Two caveats, because this gets oversold. Tagged is not the same as conformant, and no browser based engine currently promises PDF/UA conformance. And none of this helps with scans, supplier PDFs or twenty year old archives, which need real remediation and always will.

What to put in the RFP

Public procurement rewards specificity, and remediation quotes are only comparable if the scope behind them is. Name these:

• The standard, by name and level. WCAG 2.1 Level AA is what the Title II rule sets. If federal money is involved, Section 508 comes with it. PDF/UA-1 is the PDF specific conformance standard and is stricter than a clean checker report.
• Whether alternative text is in scope. The single largest cost variable, and one published ladder charges $5 a page more for it.
• How a page is counted. Covers, blank pages and full page images are counted differently by different suppliers.
• What a revision costs. If you send version 2 with three paragraphs changed, do you pay the full rate again? Settle it before the first invoice.
• Whether a conformance report is a deliverable. If it is, say so, because one vendor prices it and most do not. Our VPAT and ACR guide covers what that document has to contain, and what VPAT services cost covers the going rate.
• The acceptance test. A clean automated checker report is a minimum bar, not proof. Require human review of reading order and alt text quality. Testing PDF accessibility explains why the automated pass covers a minority of the requirements.

And ask for a paid sample of three pages from your genuine worst case before you award anything. Judge the supplier on the tag tree they hand back, not on the proposal.

The short version

Triage first, buy second. Sort your documents into published after the compliance date, pre-existing but actively used to access a service, and genuinely archival, because the third bucket is very likely covered by the rule's exception and it is usually the largest one. For steady departmental output, buy seats: axesPDF at $650 a year or PDFix Desktop Pro at EUR350, with PDFix Lite free if you want to pilot before committing. For a one time backlog, buy pages from a vendor that publishes a rate, and normalize the deliverable before you compare $10 against $9.50. For anything your own systems generate on a schedule, fix the template instead. You have until 26 April 2027 or 26 April 2028, and the cheapest document to remediate is the one that comes out right the first time.