What ADA Title II website compliance actually costs

Our own pricing first, because a page about cost that hides its own is not worth reading: $299 flat for public entities serving a population under 50,000, and $499 flat for special districts and entities serving 50,000 or more. One fee, the audit and the remediation instructions and the evidence record included, no hourly meter. A preliminary report is free if you want to see where the site stands before spending anything.

The more useful thing this page can give you is a way to read anyone else’s number. If you have collected quotes and they disagree wildly, the questions below are what they disagree about.

The site templates are the small, predictable half

A small municipal site is usually a handful of templates — home, department landing, news item, staff directory, agenda listing, a form or two — repeated across a few hundred URLs. Fixing colour contrast, focus order, form labels, heading structure and keyboard traps in six templates fixes them everywhere at once. This part of the work is bounded, it is similar in size across most entities, and it is the part every vendor prices roughly the same way.

If a quote is large, the templates are not why.

You can size the template half before you pay anyone. CivicBinder runs the Municipal Web Accessibility Index, an automated axe-core scan of US local-government homepages against the WCAG 2.0/2.1 A and AA rule set the DOJ rule references, graded A–F and published as open data under CC BY 4.0 with a page per entity. An automated scan catches a minority of WCAG 2.1 AA criteria and never replaces a manual audit — but the defects it does find are real ones, and seeing them named on your own homepage is a cheaper starting point than a discovery call.

The document backlog is the unbounded half

A decade of agendas, minutes, budgets, notices and permit forms posted as scanned images of text is the single biggest variable in any Title II estimate. Remediating a scanned PDF is per-document work: it does not benefit from a template fix, and a thousand of them cost roughly a thousand times one of them. This is where a four-figure quote and a six-figure quote come from — not from different rates, but from different answers to “how many of these are in scope?”

The rule answers that question, and it answers it more narrowly than most people expect.

Two exceptions decide most of your bill

The Title II web rule carries explicit exceptions. Two of them do the heavy lifting on cost, and both are conditional in ways that catch entities out.

Archived web content is excepted only where all four conditions hold: it was created before your compliance date (or reproduces pre-compliance physical media), it is kept only for reference, research or recordkeeping, it is stored in a designated archive area, and it has been unchanged since archiving. Fail one and the exception is gone. In practice the condition entities fail is the third — content is old, but it is still sitting on the live department page rather than in anything that functions as an archive.

Preexisting conventional electronic documents — word processing, presentation, PDF and spreadsheet files already available on the site before your compliance date — are excepted, but not where they are currently used to apply for, access, or participate in a service. That clause is the one that costs money. An old set of minutes is a record. An old permit application form still linked from the permits page is a live service document, and its age does not protect it.

A vendor who has not walked your document tree cannot know which column your PDFs land in, which means they cannot know what the work costs. That is worth asking about directly before you sign anything.

Three more exceptions worth knowing before you pay for the work

• Third-party content posted by third parties on your site is excepted — but the exception does not cover content your entity posts, content a contractor or vendor posts, or the platform or tool that enables third-party posting. If your agenda portal is a vendor product, the portal is yours to answer for.
• Individualized password-protected documents are excepted where all three conditions hold: the file is a conventional electronic document, it is about a specific person, property or account, and it is password-protected or otherwise secured. Utility bills and individual tax statements typically qualify.
• Preexisting social media posts are excepted. ADA.gov states it without conditions: social media posts made by a state or local government before its compliance date do not need to meet WCAG 2.1 Level AA. Posts made on or after that date do. This one matters to the quote because a vendor pricing a social backlog into the job is pricing work the rule does not ask for — ask which side of your date they have drawn the line on.

What an overlay does not buy you

The cheapest quotes are usually a subscription to a script that claims to fix accessibility at page load. The rule requires the content itself to conform to WCAG 2.1 Level AA. Conforming alternate versions are permitted only in very limited circumstances, where technical or legal limitations prevent making the original accessible — that is a narrow allowance, not a general substitute for remediation. A widget also produces no evidence of what was tested, which is the thing you actually need when a complaint arrives.

What your deadline does to the price

Entities serving 50,000 or more have until 26 April 2027; entities under 50,000 and all special district governments have until 26 April 2028. Special districts take the later date regardless of the population they serve. Both dates come from the interim final rule DOJ issued on 20 April 2026, which moved the original dates back by one year. The extension is worth reading in full if you are still planning against 2026.

The extension did not reduce the work; it changed when the work has to be finished. What it does affect is price, indirectly: document remediation compresses badly. The same backlog handled over eighteen months and handled in the last six weeks before a deadline are not the same purchase, and the second one is where rush pricing lives.

What CivicBinder’s flat fee covers

One fee covers the audit against WCAG 2.1 Level AA across the templates, the forms and the documents; remediation instructions written for the specific templates and documents you have rather than generic guidance; and a dated, attributable evidence record showing what was tested, when, and what was found. Our own accessibility statement is public, which is a reasonable thing to require of anyone selling you this.

We publish a flat fee because the alternative — an hourly rate against an unknown document count — transfers the entire scoping risk to you. Request the free preliminary report and it will tell you the document count before either of us commits to anything.

If you are weighing us against a specialist audit firm rather than deciding on price alone, how to compare Title II vendors for local government sets out the six shapes of provider, what each one prices on, and the cases where a specialist firm is the right purchase and we are not. If what you want is simply the numbers, which Title II vendors publish a price surveys five of them on one day and reports what each one discloses. And if your site is run by a govtech platform rather than by you, who is responsible for making a city website Title II compliant quotes the exception language that decides whether your vendor’s work counts as yours.

Compliance dates, the technical standard and all five of the rule’s exceptions re-read verbatim from the ADA.gov fact sheet on 6 August 2026. Pricing is our own and current as of that date. Nothing here is legal advice, and whether a specific document falls inside an exception is a judgement for your counsel.