ADA Website Compliance
Public entities are required to make their websites accessible to people with disabilities. We do that work properly — audit, rebuild, test, and a written record your attorney can actually use.
What the rule requires
The U.S. Department of Justice rule implementing Title II of the Americans with Disabilities Act adopts the Web Content Accessibility Guidelines (WCAG) as the technical standard for state and local government websites and mobile applications.
More than one deadline may apply to your entity. The Title II compliance dates depend on population, and a separate Section 504 rule applies to recipients of federal health and human services funding — with a different date. Both were amended during 2026. Which one governs your entity is a question for your attorney; our job is to hand you documentation clear enough to put in front of them.
What we actually do
- Audit every page and template against WCAG 2.2 Level AA
- Rebuild the templates — we do not patch over a broken foundation
- Test by keyboard alone, at 320 pixels wide, at increased text size, and with a screen reader
- Measure every colour pair rather than eyeballing it
- Review downloadable documents, including PDFs — a scanned document is a blank page to a screen reader
- Write a plain-language accessibility statement that is accurate
- Provide a written compliance record: what was tested, how, what was fixed, and what remains
What we will not do
We will not install an accessibility overlay — one of those floating widgets offering larger text and higher contrast. They do not fix the underlying problems, the DOJ rule requires the content itself to conform, and in January 2025 the Federal Trade Commission imposed a $1 million penalty on one such vendor over deceptive claims that its product made sites compliant. Organisations running overlays have still been named in accessibility litigation.
We also will not tell you that you are “certified compliant”. No vendor can certify that. Accessibility is an ongoing obligation, not a certificate, and anyone selling you one is selling a false sense of security.
Why the honest version matters
We have seen a public website publish an accessibility statement asserting that every colour combination met contrast requirements, that every form field carried a label, and citing a state statute that had nothing whatever to do with accessibility. None of it was true, and the site had no form on it at all.
A published accessibility statement is a written representation your entity can be held to. An inaccurate one is a materially worse position than saying nothing. We would rather write down what is genuinely fixed, disclose what is not, and give you a real process for handling requests in the meantime.
Start with an audit
We can audit your existing site and tell you where you stand before you commit to anything further.