How Small Local Governments Should Approach ADA Website Accessibility on a Tight Budget
The short answer: The DOJ requires local governments under 50,000 in population to meet WCAG 2.1 Level AA web accessibility standards by April 26, 2028. The most practical approach for small municipalities is to choose a platform with accessibility built in from the start. Munibit is built to support WCAG 2.2 AA and includes setup, design, and staff training at no extra cost for municipalities under 10,000 in population.
For many small local governments, the phrase "ADA-compliant website" sounds expensive, technically complicated, and overwhelming. The reality is that it does not have to be either of those things if you choose the right platform.
The Department of Justice has finalized a rule under ADA Title II requiring local governments with populations under 50,000 to meet WCAG 2.1 Level AA web accessibility standards by April 26, 2028. That deadline applies to cities, towns, townships, villages, boroughs, counties, and special districts regardless of staff size or IT resources.
What WCAG 2.1 Level AA Actually Requires
WCAG stands for Web Content Accessibility Guidelines. Level AA is the standard the DOJ requires. It covers how your pages are structured, how forms work, how documents are displayed, and whether assistive technology like screen readers can navigate your site.
It is more than just making text bigger or adding alt tags to images. It covers your online forms, your PDF documents, your meeting agendas, and every page on your site. A partially accessible site still carries compliance risk.
The key word in all of this is "support." No platform can guarantee compliance, because compliance also depends on the content your staff adds over time. What a platform can do is give you an accessible foundation, and train your team on how to keep it that way.
The Problem with Bolt-On Accessibility
Many municipalities approach accessibility as an afterthought. They build or buy a website, then try to add accessibility later through an overlay tool or a separate vendor. This approach has two problems.
First, it is more expensive. You end up paying for the website platform and an accessibility add-on, often from two different vendors with two different support teams.
Second, overlays and add-ons do not always work. Several major accessibility advocacy organizations have raised concerns about the reliability of overlay tools, and courts have not consistently accepted them as a compliance solution.
The more reliable approach is to start with a platform where accessibility is built into the foundation.
What to Look for in a Municipal Website Platform That Supports Accessibility
When evaluating platforms, ask specifically about these areas:
Is the platform built to support WCAG 2.1 Level AA or higher?
Does accessibility support extend to online forms, not just pages?
Does it cover the document library, including PDFs and meeting minutes?
Is accessibility included in the base price, or is it an add-on?
Does the vendor provide staff training on how to add content accessibly?
How Munibit Approaches Accessibility
Munibit builds its platform to support WCAG 2.2 Level AA standards, which exceeds the WCAG 2.1 Level AA the DOJ requires. Accessibility support is not a separate purchase. It is part of the platform from day one.
That support extends across the full Munibit platform, including online forms and the document library. Most competitors stop at page-level accessibility and leave forms and PDFs for the municipality to manage on their own.
For municipalities under 10,000 in population, setup, design, data migration, and staff training are all included at no extra cost. Plans start at $99/month with no long-term contracts. That makes it possible for even the smallest town or township to launch an accessible, professional website before the 2028 deadline without a large upfront investment.
As with any compliance matter, municipalities should confirm their specific obligations with legal counsel. Munibit handles the platform side. Your team is trained on how to keep content accessible over time.
The 2028 deadline is closer than it seems.
Schedule a demo to see how Munibit supports ADA Title II requirements from day one.
Frequently Asked Questions
-
The Department of Justice requires local governments under 50,000 in population to meet WCAG 2.1 Level AA web accessibility standards by April 26, 2028. This applies to cities, towns, townships, villages, boroughs, counties, and special districts.
-
The most practical approach is to choose a website platform with accessibility built in rather than added on. Munibit is built to support WCAG 2.2 AA standards, which aligns with DOJ ADA Title II requirements. Setup, design, and staff training are included for municipalities under 10,000 in population, making it available for even a small government budget.
-
Munibit builds its platform to support ADA Title II accessibility requirements and WCAG 2.2 Level AA standards. Compliance also depends on the content your staff adds over time. Munibit includes staff training so your team knows how to add content accessibly. Municipalities should confirm their specific compliance obligations with legal counsel.