Why an accessibility overlay will not make your government website compliant

The pitch you have probably heard

Somebody emails the village hall or the fire station: paste one line of JavaScript into your website and it becomes ADA compliant overnight, for a subscription of a few thousand dollars a year. There is a toolbar, a badge for your footer, and a promise that the lawyers will go away.

Why it does not hold up

The DOJ's ADA Title II rule requires web content to conform to WCAG 2.1 Level AA. Conformance is a property of the page itself: the contrast of the text as rendered, the structure of the headings, whether a form input has a real label, whether every control can be reached and operated with a keyboard. An overlay is a script that runs after the page loads and tries to patch symptoms. It cannot rebuild a heading structure that does not exist, it cannot add meaning to an unlabeled form, and it frequently interferes with the screen readers and browser tools disabled visitors already use and prefer.

This is not a fringe opinion. Accessibility practitioners have documented overlay failures at length, hundreds of disability advocates have signed an open letter asking sites to drop them, and organizations using overlays have continued to face ADA lawsuits. Paying for an overlay can end up funding a false sense of security.

What conformance actually looks like

• Text colors chosen, and checked, to meet a 4.5:1 contrast ratio against their backgrounds.
• Semantic HTML: real headings in order, landmarks, lists, and buttons that are buttons.
• Full keyboard operability with a visible focus indicator.
• Alt text on meaningful images, and labels and error messages on every form field.
• Respect for reduced-motion preferences.
• Verification: automated scans plus human judgment, repeated whenever the site changes.

The structural fix

The reliable way to get there is not to audit one template once. It is to publish with a platform where the rendering engine itself enforces the rules, so every page any staff member publishes inherits conformance. That is how Mainfolk is built: contrast-aware theming for any brand palette, semantic markup on every block, keyboard and focus behavior baked in, generated alt text, and automated WCAG audits across the platform and our own site. The receipts are public in our accessibility statement, and the full story, including the federal deadlines, is on our ADA compliance page.

If your current site leans on an overlay, the deadline clock makes this a good year to fix the foundation instead. We will rebuild your site first, and you approve it before paying a dollar.

Free download: grab our government website checklist: the short, plain-English list of what your site needs, including the accessibility items the rule cares about. No cost, no obligation.