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 that are coming fast.

If you work for a city, county, school district, library, or special district government, the clock is ticking. 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.

Critical 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.

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. That's two years from when the rule was published—which means if you're reading this in early 2026, you have very limited time remaining.

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, you should already be in active implementation mode, not still in the planning phase.

April 26, 2028: Smaller entities and all special districts

All government entities with populations under 50,000 get one extra year—they must comply by April 26, 2028. This gives you three 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 get the three-year timeline (April 26, 2028), 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 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 prerecorded and live video (WCAG 1.2.2 and 1.2.4)

• Audio descriptions for prerecorded 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 (no mouse required)

• Users have enough time to read and use content

• Content doesn't cause seizures or physical reactions

• Users can easily navigate, find content, and determine where they are

Understandable: People must be able to understand the content and interface

Your content must be readable and predictable. This includes:

• Text is readable by humans and screen readers

• Web pages appear and operate in predictable ways

• Users are helped to avoid and correct mistakes

This is particularly important for government forms and online services where errors can have significant consequences for citizens.

Robust: Content must work with current and future technologies

Your content must be compatible 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

Yes, your compliance deadline might be April 2027 or April 2027. 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 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 2025 to start planning, you may not be able to get funding approved and solutions procured before your April 2027 deadline.

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

• All active web pages and documents across all departments

• 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. Some agencies have thousands of hours of historical video content sitting on servers or stored in legacy systems.

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 (for larger entities, before April 26, 2027)

• 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 or areas clearly identified as being 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

• Documents like old application forms for programs do not qualify for the exception even if they predate the deadline

• If you maintain content for any purpose other than reference, research, or recordkeeping, it doesn't qualify—even if labeled as archived

• 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. Similarly, if you alter or update content after posting it in an archive, it would need to meet WCAG 2.1 Level AA standards.

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 citizens access to important historical information about government decisions and actions 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 this content to avoid accessibility obligations is both legally questionable and ethically problematic.

Population threshold considerations

Determining which compliance deadline applies to your organization requires understanding how "total population" is defined under the rule. For most local governments, this is straightforward: the population calculated by the U.S. Census Bureau in the most recent decennial census determines your category.

However, certain types of government entities require special consideration:

Independent school districts

Use population estimates from the Census Bureau's Small Area Income and Poverty Estimates (SAIPE) program rather than the decennial census. This data is specifically designed to provide population and poverty estimates for school districts.

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 in the census. In these cases, you must 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 to determine which deadline applies. A state university would use the state's population (which would always exceed 50,000, meaning the April 26, 2027 deadline).

Special district governments

All special district governments default to the three-year compliance timeline (April 26, 2028) regardless of the population they serve. This recognizes that these entities often have specialized, limited budgets focused on specific functions like water service, fire protection, or park management.

Special districts may also lack clear population metrics in census data since they often serve specific geographic areas that don't align with standard census boundaries.

When in doubt

If you're uncertain about how to calculate your entity's total population for compliance purposes, reviewing the full regulatory text and definitions in the DOJ's final rule is advisable. You can also consult with legal counsel or 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 the applicable compliance date, ongoing compliance with the rule is required permanently.

This means that 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 become 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: Teach employees who create and publish content how to make it accessible from the start. This includes writers, designers, video producers, form creators, and anyone else who contributes to your digital presence.

Procurement requirements ensuring vendors deliver accessible products: Build accessibility requirements into RFPs and contracts. Make vendors responsible for delivering accessible solutions rather than assuming your staff will fix accessibility issues after the fact.

Accessibility testing integrated into website publishing workflows: Don't publish content without checking accessibility first. Build testing into your content management system workflows so that accessibility checks happen automatically before content goes live.

Regular audits to identify and address barriers: Even with good processes, accessibility issues can slip through. Schedule regular audits (quarterly or semi-annually) to catch and fix problems before they accumulate.

Clear accountability and ownership: Assign specific people or roles responsibility for accessibility compliance. When everyone is responsible, no one is responsible. Make it clear who owns 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, and permanently thereafter, government entities must continue to:

• Ensure effective communication with people with disabilities

• Provide reasonable modifications to avoid discrimination on the basis of disability

• Ensure equal access to all programs, services, and activities

Accommodation requests don't wait

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. This might include:

• Providing a transcript of a video by email

• Reading web content over the phone

• Sending accessible versions of documents upon request

• Offering in-person assistance to complete online forms

The compliance deadlines don't exempt you from providing accessibility during the transition period—they set the date by which proactive, systematic compliance with technical standards becomes mandatory. You can't tell someone, "Come back after April 2027 when we're compliant." You must accommodate them now.

How to prepare: a practical approach

Given the comprehensive requirements and approaching deadlines, start preparing now. Here's a practical roadmap:

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

• 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 or lawsuits)

• Quick wins (fixes that provide maximum impact with minimum effort)

Step 3: Establish governance structures

Build systems that maintain accessibility long-term:

• Create an accessibility steering committee with cross-departmental representation

• Develop written policies and procedures

• Assign clear roles and responsibilities

• Establish processes for ongoing monitoring and improvement

• Set measurable goals and track 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

• How accessibility fits into their regular workflows

Step 5: Implement solutions

For video content specifically, many governments face a massive 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

• 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

• Ongoing monitoring and maintenance activities

This documentation serves two purposes: it helps you manage the compliance work internally, and it demonstrates good faith if you face legal challenges.

Meeting the challenge: technology and process

Understanding the requirements is one thing—meeting them is another. For video accessibility specifically, you need both the right technology and the right workflows.

Technology solutions should handle:

• Live captioning for real-time meetings

• Archive processing to remediate historical content at scale

• Quality assurance tools for reviewing and correcting captions

• Multi-language support for communities with limited English proficiency

• Audio description generation for video where visual content is essential

But technology alone isn't enough. You also need:

• Staff who understand accessibility requirements

• Workflows that integrate accessibility from the start

• Governance structures that maintain compliance over time

• Documentation proving your good-faith efforts

How MediaScribe supports compliance

MediaScribe is designed specifically to help government agencies meet WCAG 2.1 Level AA requirements for video content:

• Real-time captioning for live meetings meets WCAG 1.2.4 (Captions - Live)

• Automatic caption generation for archived content meets WCAG 1.2.2 (Captions - Prerecorded)

• Caption editor and quality tools ensure accuracy and corrections

• 72+ language support helps you serve limited English proficiency communities

• Compliance documentation built into the system for audit readiness

The system is designed to work within government budgets and workflows, making compliance achievable without hiring expensive vendors for every meeting.

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 and the ADA

• w3.org/WAI - Complete WCAG 2.1 specification, understanding documents explaining each success criterion, and techniques for meeting requirements

Many state and local government associations also offer resources, training, and peer support networks focused on accessibility compliance. 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.

Connecting with other agencies facing similar challenges can provide valuable insights and proven strategies. Consider joining accessibility-focused groups or attending conferences where practitioners share lessons learned and best practices.

Key takeaways

• April 26, 2027 is the deadline for entities with populations of 50,000 or more

• April 26, 2028 is the deadline for entities under 50,000 plus all special districts

• WCAG 2.1 Level AA is the mandatory standard for all government web content and mobile apps

• No exemptions exist for small municipalities—every government must comply

• All video content must have captions and audio descriptions where applicable

• Archived content exception exists but requires four specific conditions to be met

• Ongoing compliance is required after your deadline—this isn't a one-time project

• Lawsuits are happening now—waiting until the deadline increases legal risk

• Good-faith efforts documented today can protect you legally tomorrow

• Start preparing immediately regardless of your deadline

The path forward

The deadlines may seem distant, but the work required is substantial. Agencies that start now—auditing content, training staff, remediating critical materials, building sustainable processes—will be far better positioned than those that delay.

Beyond legal compliance, digital accessibility is fundamentally about equal access and civil rights. When government services and public participation opportunities move online, ensuring digital content is accessible to people with disabilities isn't optional—it's a core obligation of democratic governance.

The approximately 61 million Americans who have disabilities deserve full access to their government's digital services. People who are deaf or hard of hearing who can't access uncaptioned meeting videos, people who are blind who can't navigate websites with screen readers, people with mobility impairments who can't use mouse-dependent sites, people with cognitive disabilities who need clear and simple language—they all depend on governments taking accessibility seriously.

This isn't about checking boxes or avoiding lawsuits, though those are real considerations. It's about ensuring that all community members can participate fully in civic life, access the services they need, and hold their government accountable.

The DOJ's final rule provides clear standards and reasonable timelines. Every state and local government entity now faces a choice: lead in providing accessible digital services to all community members, or wait until legal and regulatory pressure forces action.

With strategic planning, appropriate resources, and organizational commitment, achieving WCAG 2.1 Level AA compliance is entirely achievable. The agencies that succeed will be those that start now, treat accessibility as an ongoing commitment rather than a checkbox exercise, and recognize that equal digital access is both a legal requirement and a moral imperative.