StillTrue

A conformance statement your website vendor won't sign.

Under the ADA, your website and the documents on it must meet an accessibility standard (WCAG 2.1 AA) by April 26, 2027 if you serve 50,000 or more people — April 26, 2028 for smaller cities, towns, school districts, and special districts.

What your web platform actually covers

Most municipal web platforms are built to WCAG 2.1 AA and say so, and that claim is usually fair. Read it closely and it is a claim about the platform. The content — your agendas, minutes, budgets, forms and PDFs — is listed as the customer's responsibility.

The wording is careful, too: aligns with, helps achieve compliance, compliance is a fluid measurement. That is accurate drafting, not evasion. But it means the obligation still sits with you, and nobody signs anything.

Automatic PDF conversion has a limit worth knowing

Some platforms publish an accessible HTML version alongside an inaccessible PDF. That is a conforming alternate version, and the rule allows it narrowly:

"A public entity may use conforming alternate versions of web content, as defined by WCAG 2.1, to comply with § 35.200 only where it is not possible to make web content directly accessible due to technical or legal limitations." 28 CFR § 35.202(a)

An agenda, a budget, or a fillable form can usually be made accessible directly. Where that is possible, the rule asks for the document itself.

What you get

• A plain-language list of what fails, document by document, naming the WCAG criterion each item misses.
• We fix the documents themselves — not a parallel version of them.
• A signed statement: what was tested, by what method, on what date, and the result. Something you can hand to your board, your attorney, or someone who asks.

Start free

We'll audit one high-traffic page and your ten most-downloaded PDFs, by hand, and send you the findings plus a sample of the signed statement. Free, and no obligation after.