ADA compliance consultants for government and higher education: cost and what to check

The short answer: pick the consultant on scope documents, not on price, because six of the ten providers we priced on 1 September 2026 will not publish a number at all. For a state agency, a city, a school district or a university, the two things that separate a useful engagement from an expensive report are both procurement decisions rather than technical ones: the unit the audit is scoped in, and whether documents are inside the contract or outside it. Get those two right and the price question mostly answers itself.

Public sector buying has a deadline behind it now, which is why this question is being asked so much more than it was two years ago. The Department of Justice Title II rule sets WCAG 2.1 Level AA as the technical standard for state and local government websites and mobile apps. On 20 April 2026 the Federal Register published an Interim Final Rule extending the compliance dates, and as of 1 September 2026 they stand at 26 April 2027 for public entities with a total population of 50,000 or more, and 26 April 2028 for entities under 50,000 and for any special district government. Articles written in 2024 and 2025 still print April 2026, so check the date on anything you are reading.

What a public sector engagement needs that a commercial one does not

A private company buying an accessibility audit usually wants one thing: a list of what is broken. A government or higher education buyer needs four, and three of them are contract terms rather than deliverables.

Section 508 or Title II: know which one you are actually under

These get used interchangeably in sales conversations and they are not the same obligation.

Section 508 applies to federal agencies and to the information and communication technology they buy. If you are a federal program office, or a vendor selling to one, this is your regime, the Revised 508 Standards incorporate WCAG Level A and AA as the technical baseline, and the deliverable your contracting officer expects is an Accessibility Conformance Report on the Section 508 edition of the VPAT template.

Title II of the ADA applies to state and local government: cities, counties, school districts, public universities, transit authorities, special districts. The 2024 web rule and its 2026 extension are what set the April 2027 and April 2028 dates. The standard is WCAG 2.1 Level AA, and no VPAT is required by the rule itself, though many institutions produce one anyway because it is the format their own vendors are asked for.

Private universities are usually under Title III instead, which has no published technical standard and no deadline, which does not mean no exposure. Courts have consistently reasoned from WCAG in Title III website cases, so the practical target is the same.

The reason this matters when hiring is simple. A consultant whose entire practice is Title III ecommerce remediation will produce a perfectly good report that arrives in the wrong format for a federal procurement file. Ask directly which regimes they deliver against and ask to see a redacted ACR they have produced.

The exception that removes more documents than any tool

Before you scope a document remediation project, read the preexisting documents exception in the Title II rule. It is short and it is worth a great deal of money. In the Department of Justice's own words, documents that meet both of the following usually do not need to meet WCAG 2.1 Level AA: they are "word processing, presentation, PDF, or spreadsheet files", and they were "available on the state or local government's website or mobile app before the date the state or local government must comply with this rule."

Two limits keep this from being a blanket amnesty. The exception has situations where it does not apply, and the important one is that a document currently used to apply for or access a service, program or activity is in scope however old it is. A 2011 enrollment form that people still fill in is not preexisting for these purposes. And the exception says nothing about anything you publish after your compliance date.

On a real university backlog that rule typically removes a large majority of the archive and leaves a much smaller, sharper list: active forms, current policies, current course materials, anything still linked from a service page. That list is the one to price. Handing a vendor an undifferentiated count of 40,000 files and asking for a per page quote is how a program spends its entire accessibility budget on documents nobody opens.

Getting an internal read before you go to market

The hardest part of a public sector accessibility program is rarely the testing. It is that the websites, the documents and the purchasing decisions sit in departments that do not report to each other, and the person accountable for the April deadline usually has authority over none of them. A consultant cannot fix that, and a consultant hired before it is understood will produce findings that land nowhere.

So do the boring internal pass first. Inventory who publishes what and in which system, find out which departments have already bought accessibility tooling of their own, and score where each department actually stands on process and capability rather than guessing from the outside. That output does two jobs at once: it tells you which units need help and which only need a checklist, and it becomes the scope annex your bidders quote against. Agencies that skip it end up buying one large audit of a central site while a dozen departmental subsites nobody listed carry most of the risk.

Who publishes rates, and how to build an estimate when nobody will

We checked ten accessibility audit providers on 1 September 2026. Two publish complete rate cards, one publishes a starting price, six publish nothing, and one blocks automated readers. For a public buyer who has to produce an independent government cost estimate before soliciting bids, that is a problem, and the two published cards are the way around it.

Anchor on the per screen rate. Accessible.org publishes $100 to $250 per page or screen, mostly based on complexity, and $25 to $100 for light ones. Count your unique templates and flows, assign each a complexity, and you have a defensible bottom-up estimate in twenty minutes. For most agency sites that lands between $1,250 and $3,500, which is also the band the second published card falls in from the other direction. Treat that as a floor rather than a quote if your site is really an application: the same vendor prices a 15 to 20 screen SaaS product from $4,000, because a screen with several permission states is several screens to test.

Add the version premium correctly. Title II names WCAG 2.1 Level AA. If you are specifying 2.2 anyway, and most institutions are, price it. One published card charges a flat 10% for 2.2 over 2.1. The other does not sell a low cost 2.2 audit at all, putting 2.1 in a $500 product and 2.2 only in a product starting at $1,500. The premium is not a market constant.

Price the documents on their own line. Take the post-exception document list, multiply pages by the published $7.50 to $9.50 simple remediation rate, and put it in the estimate as a separate item so it does not get absorbed into a web audit quote and then discovered later. Do not budget from the $4.00 per page floor that the same vendor quotes on its pricing page; that is the simplest possible file, not an average one.

The full provider by provider breakdown, including who has no pricing page at all and what each one bills per, is on our ADA compliance audit cost comparison.

Questions to ask on the first call

Five, and they take ten minutes.

1. How many unique screens will you test, and can I see the list before we sign? A consultant who answers with a page count rather than a template list is scoping the wrong thing for a database driven site, and a consultant who cannot name the screens cannot be compared with another bid.

2. Who does the manual testing, and with which assistive technology? You want named tools and named browser pairings. Automated scanning alone finds a minority of WCAG failures, and the ones it misses are the ones that stop people from completing a task.

3. Do you produce an ACR, and on which VPAT edition? If the answer is only the WCAG edition and you are selling to or buying for a federal program, that is a mismatch. Our guide to the VPAT and Accessibility Conformance Report covers which criteria actually get decided in your own templates rather than in a vendor product.

4. What is your position on overlays? This one is a useful filter. A consultant who recommends an accessibility widget as a path to Title II conformance is selling something the rule does not accept, and the DOJ has been explicit that a plugin does not substitute for conforming content.

5. What happens to documents we generate after the audit? The honest answer names the generator, not the documents. Most PDFs on a public sector site come out of a CMS, a reporting tool or a forms system, and they all carry the same defects because they all come from the same template. Remediating them one at a time is paying repeatedly for one upstream bug.

The work that stops the bill recurring

An audit is a snapshot. It tells you the state of a set of screens on a date, and it is worth buying. What it cannot do is stop the same findings coming back next quarter, and on document heavy public sector sites they always do, because the generator that produced the noncompliant PDF is still running.

Nearly every accessibility defect in a generated PDF was decided before the PDF existed. Untagged output is a render setting, off by default in a surprising number of libraries. A missing document title is a metadata field. An undeclared language is one attribute. Reading order, heading structure, list semantics and table header cells are all properties of the HTML the renderer was handed, carried faithfully into the PDF by a tool doing exactly what it was told.

So the cheapest thing a public sector program can do after an audit is not to buy more remediation. It is to fix the templates once and switch tagging on at render time, then keep a free validator in the publishing path so nothing untagged ships again. Our comparison of accessible PDF generation covers which HTML to PDF engines emit tagged output and which genuinely target PDF/UA, which is a distinction most of the category collapses. For the historical backlog that is already published, the per page rates four vendors publish are on our PDF remediation services page, and the free tools that validate conformance are covered in our 508 compliance testing software comparison.

Hire the consultant for the judgment work: the keyboard traps, the reading order, the error messages nobody announces, the flows that break for a screen reader user three steps in. Those are the failures no script will ever find. Everything a script can decide should be decided by a script, before the document is published, so the expert hours go where they are worth the money.