ADA Title II and the April 2027 Deadline

In April 2024, the U.S. Department of Justice finalized a rule that changes everything for state and local governments. For the first time, Title II of the Americans with Disabilities Act now includes specific, enforceable technical standards for websites and mobile apps. This isn't guidance—it's federal law with compliance deadlines attached.

If you work for a city, county, school district, library, or special district government, this rule applies to you. Here's what you need to know, when you need to comply, and how to prepare.

What the final rule requires

The DOJ's final rule, published April 24, 2024, says all web content and mobile apps from state and local governments must meet WCAG 2.1 Level AA standards.

WCAG stands for Web Content Accessibility Guidelines. It's the international standard for digital accessibility, developed by the World Wide Web Consortium (W3C). Level AA is the middle tier of compliance—more rigorous than Level A, less demanding than Level AAA. Federal agencies already follow this standard under Section 508 of the Rehabilitation Act.

The rule covers everything your government publishes online:

• Your website and all its pages

• Online forms and permit systems

• PDFs and documents you upload

• Mobile apps

• All video content (meeting recordings, public service announcements, training videos, everything)

If your government posts it online, it must meet WCAG 2.1 Level AA by your compliance deadline. There are no exceptions based on budget, staff size, or technical capacity. The only variables are when you must comply and how you get there.

Compliance deadlines

Your deadline depends on your government entity's population size. The DOJ structured the timeline to give smaller entities more preparation time while recognizing that larger governments typically have more resources to dedicate to compliance work.

The original deadlines from the 2024 final rule were extended by one year through a 2026 Interim Final Rule. The current deadlines are:

April 26, 2027: larger entities (50,000+ population)

Cities, counties, townships, and school districts with populations of 50,000 or more must comply by April 26, 2027—three years from when the original rule was published.

Population is based on the most recent U.S. Census Bureau decennial census. For independent school districts, use the Census Bureau's Small Area Income and Poverty Estimates instead of the decennial census data.

This deadline affects thousands of larger municipalities, urban counties, and major school districts across the country. If you serve a population of 50,000 or more, building accessibility into your ongoing workflows now is far preferable to scrambling to remediate accumulated content later.

April 26, 2028: smaller entities and all special districts

All government entities with populations under 50,000 must comply by April 26, 2028. This gives these entities four years from the rule's publication to achieve full compliance.

The DOJ picked 50,000 as the cutoff because it matches the "small governmental jurisdictions" definition in the Regulatory Flexibility Act. Smaller governments typically have tighter budgets and fewer technical staff, so they get more time to prepare and implement solutions.

All special district governments also fall under the April 26, 2028 deadline, regardless of the population they serve. This includes water districts, fire districts, library districts, park districts, and other single-function governmental units. The DOJ recognized that these entities often have very focused budgets dedicated to specific functions and may not have clear population data in census records.

There are no exemptions. Every local government in America must comply, even tiny villages with populations under 1,000. The extended timeline for smaller entities is not an exemption—it's a delayed implementation date. Compliance is still mandatory.

What WCAG 2.1 Level AA means for your content

WCAG 2.1 Level AA includes dozens of specific requirements organized around four principles, commonly known by the acronym POUR: Perceivable, Operable, Understandable, and Robust.

Perceivable: People must be able to perceive the information. Your content must be presented in ways that all users can perceive, regardless of sensory abilities. For video, this means:

• Closed captions for all pre-recorded and live video (WCAG 1.2.2 and 1.2.4)

• Audio descriptions for pre-recorded video when the dialogue doesn't convey what's happening visually (WCAG 1.2.5)

• Media alternatives for time-based media (WCAG 1.2.3)

For other content, this includes proper text alternatives for images, sufficient color contrast, and content that doesn't rely solely on color to convey meaning.

Operable: People must be able to operate the interface. Your website and apps must be fully navigable and usable without requiring specific input methods. This means keyboard navigation works for all functionality, users have enough time to read and use content, content doesn't cause seizures or physical reactions, and users can easily navigate and find what they need.

Understandable: People must be able to understand the content and interface. Your content must be readable and predictable, users must be helped to avoid and correct mistakes, and pages must appear and operate in predictable ways. This is particularly important for government forms and online services where errors can have significant consequences for residents.

Robust: Content must work with current and future assistive technologies, including screen readers, alternative keyboards, and other tools people with disabilities use to access digital content.

Meeting these standards isn't a one-time project. Every new page you publish, every PDF you upload, every video you post must meet WCAG 2.1 Level AA from day one. Accessibility must become part of your standard operating procedures.

Why you can't wait until the deadline

Your compliance deadline is April 2027 or April 2028. But waiting until then to start accessibility work would be a serious mistake for several reasons.

Lawsuits are already happening

ADA lawsuits against governments with inaccessible websites are already happening at scale—over 4,000 annually, according to industry data. These lawsuits don't wait for the compliance deadlines. Courts have consistently ruled that the ADA applies to government websites even before these new technical standards took effect.

Settlements typically range from $25,000 to $75,000, plus you still have to fix the accessibility problems and often pay plaintiff's attorney fees. Total litigation costs frequently exceed $100,000 when you factor in legal defense, settlement payments, and remediation work.

Good-faith efforts matter legally

If you're sued today, demonstrating good-faith compliance efforts can significantly strengthen your legal position. Documented audits, systematic remediation plans, staff training programs, and measurable progress toward accessibility show courts that your organization takes its civil rights obligations seriously.

Starting now builds that track record. Waiting until the deadline and then scrambling to comply doesn't demonstrate the same institutional commitment to accessibility.

Implementation takes longer than you think

Most agencies significantly underestimate how long accessibility remediation takes. Between conducting audits, prioritizing fixes, training staff, implementing new processes, and actually remediating content, you're looking at months or years of work—not weeks.

If you have decades of archived video without captions, that backlog alone could take a year or more to address, even with automated solutions. Starting now gives you the runway you need.

Budget cycles don't align with compliance deadlines

Most government entities operate on annual budget cycles with long lead times for major purchases. If you wait until late in your deadline year to start planning, you may not be able to get funding approved and solutions procured in time.

Starting now lets you spread costs across multiple budget cycles, making the financial impact more manageable and easier to justify to leadership and budget authorities.

Scope of content requiring remediation

For many government entities, the most daunting aspect of compliance is the sheer volume of digital content that requires review and potential remediation. This includes:

• Your current website—every page, every document, every interactive element

• Online forms and interactive tools (permit applications, service requests, payments)

• Mobile applications

• Archived content that remains publicly accessible

• All video content—recorded meetings, informational videos, public service announcements, live streams, training materials, archived broadcasts

Video presents a particular challenge because many governments have years or even decades of archived meeting recordings that were never captioned or made accessible.

What about archived or older content?

The rule does include a specific exception for some types of archived content, but it's not automatic or blanket. To qualify for the "archived web content exception," all of the following conditions must be true:

• The content was created before your compliance deadline

• It is retained exclusively for reference, research, or recordkeeping—not for ongoing use in services or programs

• It has not been altered or updated after being archived

• It is organized and stored in a dedicated area clearly identified as archived

If any one of these conditions is not met, the content must meet accessibility standards. That means:

• Simply labeling something as "old" or "archived" is not enough

• Archived videos or documents that are still used to provide services or information must be accessible

• Old application forms for active programs do not qualify for the exception

• Content that you update or modify after archiving loses its exception status

The DOJ allows minor adjustments before archiving (like redacting personally identifying information), but substantial changes like adding, updating, or rearranging content would disqualify it from the exception.

The removal trap

Some agencies mistakenly believe they can simply remove old, inaccessible content to avoid compliance requirements. This approach creates several problems.

First, it may violate public records laws that require governments to maintain and provide access to certain types of documents and videos. Second, it undermines transparency commitments and can damage public trust. Third, it denies residents access to important historical information about government decisions that affect their communities.

Citizens have a legitimate interest in accessing historical meeting recordings to understand how and why decisions were made, especially for land use, zoning, budget allocations, and policy changes that have long-term impacts. Removing content to avoid accessibility obligations is both legally questionable and ethically problematic.

Population threshold considerations

Determining which compliance deadline applies requires understanding how "total population" is defined under the rule.

Most local governments: Population from the most recent U.S. Census Bureau decennial census.

Independent school districts: Use the Census Bureau's Small Area Income and Poverty Estimates (SAIPE) program rather than the decennial census. If your district serves 50,000 or more students according to SAIPE data, your deadline is April 26, 2027. If fewer than 50,000, your deadline is April 26, 2028.

Public colleges, universities, and libraries: These entities often don't have population data directly associated with them. Determine your total population by reference to the population of the government entity that operates you. For example, a county library system would use the county's population. A state university would use the state's population, which would always exceed 50,000, placing it under the April 26, 2027 deadline.

Special district governments: All special district governments default to the April 26, 2028 deadline regardless of the population they serve.

When in doubt, reviewing the full regulatory text and definitions in the DOJ's final rule is advisable. You can also contact the DOJ's ADA Information Line at 1-800-514-0301 (voice) or 1-833-610-1264 (TTY) for technical assistance.

Ongoing compliance requirements

The compliance dates are not one-time deadlines after which you can return to business as usual. After your applicable compliance date, ongoing adherence to the rule is required permanently.

Every new web page published, every document uploaded, every video produced, and every mobile app feature added must meet WCAG 2.1 Level AA standards from the moment it goes live. Accessibility cannot be an afterthought or a periodic project—it must be integrated into your organization's content creation and publication workflows.

Building sustainable compliance

Many successful government entities are establishing accessibility governance programs that include:

• Staff training on accessible content creation, so employees who write, design, and produce video know how to make content accessible from the start

• Procurement requirements ensuring vendors deliver accessible products, with accessibility written into RFPs and contracts

• Testing integrated into publishing workflows, so accessibility checks happen before content goes live rather than after

• Regular audits (quarterly or semi-annually) to catch and fix issues before they accumulate

• Clear accountability, with specific people or roles assigned ownership of accessibility in each department

Existing ADA obligations continue

The new technical standards don't replace or diminish any existing ADA Title II obligations. Throughout the transition period before your compliance date, government entities must continue to ensure effective communication with people with disabilities, provide reasonable modifications to avoid discrimination, and ensure equal access to all programs, services, and activities.

If someone requests accommodation to access your digital content before you've achieved full WCAG 2.1 Level AA compliance, you're still required to provide that access through alternative means—providing a transcript by email, reading web content over the phone, sending accessible document versions, or offering in-person assistance to complete online forms. The compliance deadlines don't suspend your obligation to accommodate individual requests during the transition period.

How to prepare: a practical approach

Step 1: Conduct an accessibility audit

Understand your current state before you can improve it. A comprehensive audit should inventory all digital properties (websites, apps, video archives), test a representative sample against WCAG 2.1 Level AA, identify the most critical barriers, estimate the scale of remediation work needed, and document findings for baseline comparison.

Step 2: Prioritize remediation efforts

You can't fix everything at once. Prioritize based on high-traffic content (your homepage, most-visited pages), essential public services (permit applications, emergency information), content used by the most vulnerable populations, legal risk (content most likely to generate complaints), and quick wins that provide maximum impact with minimum effort.

Step 3: Establish governance structures

Build systems that maintain accessibility long-term: an accessibility steering committee with cross-departmental representation, written policies and procedures, clear roles and responsibilities, processes for ongoing monitoring and improvement, and measurable goals with tracked progress.

Step 4: Train your staff

Technology alone won't achieve compliance. Your staff needs to understand why accessibility matters, what WCAG 2.1 Level AA requires, how to create accessible content in their specific roles, where to get help when they have questions, and how accessibility fits into their regular workflows.

Step 5: Implement solutions

For video content specifically, many governments face a significant backlog of uncaptioned archived meetings. You need technology solutions to process historical content at scale, workflows for making new content accessible from day one, quality assurance processes to ensure accuracy, and documentation of your compliance efforts.

Step 6: Document everything

Maintain detailed records of audit findings and remediation plans, staff training completion, vendor contracts and deliverables, compliance milestones achieved, and ongoing monitoring activities. This documentation serves two purposes: it helps you manage the compliance work internally, and it demonstrates good faith if you face legal challenges.

Government application

The practical reality for most government communications teams is that public meetings are the largest source of video content—and the most pressing compliance concern.

A mid-size city with weekly city council meetings, twice-monthly planning commission hearings, monthly parks board meetings, and quarterly budget workshops might generate 60–80 hours of meeting video per year. Each of those recordings needs synchronized captions before it can be considered accessible under the rule.

For many agencies, the challenge isn't understanding what's required—it's finding a sustainable, affordable way to deliver captions at that volume without burdening already-stretched staff. Manual captioning services can cost $150–$300 per hour. For a city captioning all its public meetings, that could represent a significant annual expense. AI-assisted captioning tools have changed the economics considerably, making it realistic for even small agencies to caption every public meeting—not just the highest-profile ones.

MediaScribe integration

MediaScribe Live is purpose-built to address the video compliance challenge described in this article. It provides real-time AI-powered captions for live government meetings—city council sessions, planning commissions, public hearings, budget workshops—with a workflow designed for non-technical staff.

MediaScribe Narrate, a separate cloud-based tool, handles audio descriptions for pre-recorded video content. Together, they address the two primary WCAG video requirements (captions and audio descriptions) that the ADA Title II rule mandates.

Both products generate caption files and documentation that support your agency's compliance recordkeeping. Human review of AI-generated captions is always recommended before publishing, particularly for content with technical terminology, proper names, or specialized vocabulary.

Official resources and guidance

The Department of Justice provides extensive resources to help government entities understand and implement the new requirements:

• ADA.gov — Full text of the final rule, fact sheets, technical assistance documents, and guidance on web accessibility

• w3.org/WAI — Complete WCAG 2.1 specification, understanding documents explaining each success criterion, and implementation techniques

• Federal Register IFR (April 2026) — Official notice of the extended compliance dates

Many state and local government associations also offer resources, training, and peer support. Organizations like the National League of Cities, U.S. Conference of Mayors, National Association of Counties, and International City/County Management Association often provide webinars, templates, and guidance specific to their members.

Summary

• The DOJ's 2024 final rule requires all state and local government web content and mobile apps to meet WCAG 2.1 Level AA standards

• Compliance deadlines were extended by one year in April 2026: entities with 50,000+ residents must comply by April 26, 2027; smaller entities and special districts by April 26, 2028

• The rule covers all online content, including video—both live and pre-recorded; there are no exemptions based on size, budget, or technical capacity

• Archived content may qualify for an exception, but only under four specific conditions; content in active use does not qualify

• ADA legal exposure exists regardless of the deadline—lawsuits are already being filed; documented good-faith effort strengthens your legal position

• Video requirements include synchronized captions, audio descriptions for pre-recorded content where visual information isn't conveyed in the audio, and accessible media alternatives

• A phased approach—audit, prioritize, govern, train, implement, document—is the most practical path forward

• Ongoing compliance after your deadline is required permanently; accessibility must become part of standard operations

What's next

Now that you understand the regulatory framework and what your agency is required to do, the next article in this foundation module walks through the specific WCAG 2.1 success criteria that apply to video—mapping each requirement to the real-world content types you're most likely working with.