The April 2026 ADA Deadline: What Municipal Contractors Need to Know Right Now

The Rule That Changes Everything

On April 24, 2024, the Department of Justice published a final rule under Title II of the Americans with Disabilities Act that, for the first time, ties digital accessibility obligations for state and local governments to a specific technical standard and a hard deadline.

The standard is WCAG 2.1 Level AA. The deadline is April 24, 2026 — less than four months from today — for any public entity serving a population of 50,000 or more. Smaller entities and special district governments have until April 26, 2027.

Most of the coverage around this rule has focused on what it means for government IT departments and procurement officers. That makes sense — they are the entities directly regulated. But if you are a contractor who builds, manages, or delivers digital assets on behalf of a municipality, the rule affects you just as directly. You just might not realize it yet.

Why Contractors Are in Scope

Here is the language that matters: the DOJ has made clear that a public entity cannot delegate away its ADA obligations. If a municipality hires you to build a project portal, maintain a public-facing website, manage a document repository, or develop a mobile application, the accessibility of that deliverable is the municipality's legal responsibility — and by extension, yours.

The DOJ's own guidance explicitly recommends that public entities review existing vendor contracts and update them to require WCAG 2.1 AA conformance. It goes further, suggesting municipalities should require vendors to provide detailed accessibility information before signing contracts, include accessibility warranties, prohibit vendors from disclaiming those warranties, and require indemnification for any breach.

In practical terms, this means the municipality is being told — by the federal government — to make your compliance their contract language.

What WCAG 2.1 AA Actually Requires

WCAG stands for Web Content Accessibility Guidelines, published by the World Wide Web Consortium. Version 2.1 at the AA conformance level includes requirements across four principles, often abbreviated as POUR:

Perceivable — Content must be presentable in ways all users can perceive. This includes providing text alternatives for images, captions for video, and sufficient color contrast between text and backgrounds.

Operable — Users must be able to navigate and interact with all functionality using a keyboard alone, without requiring mouse input. Time limits must be adjustable, and content cannot be designed in ways that cause seizures.

Understandable — Text must be readable, navigation must be predictable, and input assistance must help users avoid and correct errors in forms.

Robust — Content must be compatible with current and future assistive technologies, including screen readers, magnification software, and alternative input devices.

Meeting AA conformance requires satisfying all Level A and Level AA success criteria — 50 specific, testable requirements in total. This is not a subjective standard. Every criterion has documented testing procedures, and failures are binary: a page either passes or it does not.

What Is Actually Covered

The scope of the rule is broader than most contractors assume. It applies to every digital touchpoint used to deliver government programs, services, or activities, including:

• Public-facing websites and web applications
• Mobile applications
• Online forms, including permit applications and bid submission systems
• PDF documents, including engineering drawings, site plans, and project proposals
• Digital document repositories
• Project portals and progress-tracking dashboards
• Video and multimedia content

If you have built it, host it, or manage it on behalf of a public entity, it needs to meet the standard.

The Exceptions Are Narrower Than You Think

The rule does include limited exceptions, but they are tightly defined and rarely apply to contractor-delivered work.

Archived content is exempt only if it was created before the compliance date, is kept exclusively for reference or recordkeeping, has not been altered since archiving, and is stored in a clearly identified archive area. Active project documents do not qualify.

Preexisting conventional electronic documents — PDFs, Word files, spreadsheets — created before the compliance date may be exempt, but only if they are not currently used to carry out government services. If a municipality is still using your specification document from 2023 as part of an active project, it is not exempt.

Third-party content posted by unaffiliated members of the public (like comments on a message board) may be excluded. But content from contractors and vendors is explicitly not third-party content under this rule. Your deliverables are the municipality's deliverables.

The undue burden exception exists but requires formal documentation demonstrating that compliance would result in significant difficulty or expense. It does not exempt the entity from providing the information through an alternative accessible means. This is a last resort, not a strategy.

The Penalties Are Real

Non-compliance with Title II of the ADA carries first-time penalties of up to $75,000, increasing to $150,000 for subsequent violations. Beyond fines, the DOJ can initiate investigations, require mandatory remediation under federal oversight, and impose settlement agreements with ongoing reporting obligations.

Since 2011, at least 142 municipalities have been sued over accessibility non-compliance. In 2024, a federal judge in Louisiana refused to dismiss an accessibility case against state agencies even though the April 2026 deadline had not yet arrived, ruling that the ADA obligations existed independently of the new rule's timeline. The deadline formalizes the standard — it does not create the obligation from scratch.

For contractors, the risk is compounding. If a municipality faces enforcement action because of digital assets you delivered, your next RFP response in that jurisdiction — and potentially others — starts from a deficit.

What This Means for Your Next Bid

Procurement is already shifting. Municipalities across the country are updating their RFP language to explicitly require WCAG 2.1 AA conformance from vendors and contractors. The DOJ's guidance practically writes the procurement language for them.

Expect to see requirements for Voluntary Product Accessibility Templates (VPATs) — standardized documents that report how your digital product meets each WCAG criterion. The completed version, called an Accessibility Conformance Report (ACR), is increasingly a prerequisite just to pass the initial evaluation stage of a government bid.

Contractors who can demonstrate proactive compliance — through documented scans, timestamped remediation logs, and structured audit defense documentation — will have a measurable advantage over competitors who treat accessibility as an afterthought or rely on automated overlay widgets that the FTC has already deemed insufficient.

The Timeline Is Not Generous

April 24, 2026 is 109 days away as of this writing. Accessibility remediation is not a weekend project. A comprehensive compliance process involves inventorying all digital assets, running both automated and manual accessibility scans, prioritizing issues by severity and impact, performing code-level remediation, retesting, and documenting every step.

For contractors managing multiple municipal relationships, the scale compounds quickly. The time to start was months ago. The next best time is today.

What You Should Do This Week

Audit your current deliverables. Run a WCAG scan against every digital asset you have delivered to or manage for a public entity. Identify the highest-severity issues first — missing alt text on images, broken keyboard navigation, insufficient color contrast, and inaccessible PDFs are the most common failure points.

Review your contracts. Check whether your existing municipal contracts include accessibility language. If they do not yet, they likely will at renewal. Getting ahead of that conversation positions you as a proactive partner rather than a reactive liability.

Start documenting everything. A timestamped audit defense log that shows your scanning activity, issue identification, remediation steps, and verification results is the single most valuable document you can produce — both for winning bids and for defending your work if compliance questions arise.

Talk to your municipal contacts. Ask your clients whether they have begun their Title II compliance planning. Understanding their timeline and priorities helps you align your own remediation efforts with their needs.

The April 2026 deadline is not a suggestion and it is not going away. The contractors who treat this as a competitive opportunity — rather than a compliance burden — are the ones who will be winning municipal bids through 2026 and beyond.

---

This post is for informational purposes only and does not constitute legal advice. Consult with qualified legal counsel for guidance specific to your situation.