ADA Compliance for Government Websites: A Complete Guide to the New 2026-2028 Requirements
The internet has fundamentally changed how government serves the public. From renewing driver’s licenses and applying for benefits to participating in public meetings and paying taxes, digital services have become essential to daily life . But when government websites aren’t accessible, they create barriers that can prevent millions of Americans with disabilities from accessing critical services .
In April 2024, the U.S. Department of Justice (DOJ) published a landmark final rule updating Title II of the Americans with Disabilities Act (ADA). For the first time, the DOJ established specific technical standards that state and local governments must follow to ensure their websites and mobile apps are accessible to people with disabilities .
This guide explains what government agencies need to know, when they must comply, and how to get started.
Why Digital Accessibility Matters
People with disabilities use assistive technologies to navigate the web. Blind individuals may use screen readers that convert on-screen text to speech or Braille. People with mobility impairments may rely on voice recognition software or keyboard-only navigation .
When websites are poorly designed, they create unnecessary barriers—just as stairs prevent wheelchair users from entering a building. A photograph without descriptive text, for instance, is invisible to a screen reader user. An online form that can’t be completed with a keyboard excludes those who can’t use a mouse .
“Just as stairs can exclude people who use wheelchairs from accessing government buildings, inaccessible web content and mobile apps can exclude people with a range of disabilities from accessing government services.” – DOJ Preamble to the Final Rule
Accessible design benefits everyone. When accessibility features are built into web pages, they make websites more convenient for all users—including people using older computers, mobile devices, or those with temporary limitations.
We’re offering a free ADA compliance audit. View more here.
The New Standard: WCAG 2.1 Level AA
The DOJ adopted the Web Content Accessibility Guidelines (WCAG) Version 2.1 Level AA as the official technical standard for government websites and mobile apps .
WCAG is organized around four principles—often called POUR—that require digital content to be:
| Principle | What It Means |
|---|---|
| Perceivable | Information must be presentable to users in ways they can perceive (e.g., alt text for images, captions for videos, sufficient color contrast) |
| Operable | Interface components must be operable by all users (e.g., keyboard navigation, focus indicators, no auto-playing content) |
| Understandable | Information and operation must be understandable (e.g., predictable navigation, error suggestions on forms) |
| Robust | Content must work with a wide range of assistive technologies (e.g., proper semantic HTML, compatibility with screen readers) |
There are 86 success criteria in WCAG 2.1. To meet Level AA compliance, government entities must satisfy all Level A and Level AA criteria . Level AAA criteria—the highest level—are not required .
Examples of WCAG 2.1 Level AA Requirements
Alt text for images: Every non-decorative image must have meaningful alternative text
Color contrast: Text must have a contrast ratio of at least 4.5:1 against its background
Captions: Video content must include captions
Keyboard accessibility: All functionality must be operable through a keyboard alone
Focus indicators: Users must be able to see where they are navigating
Form error suggestions: When input errors are detected, users must be told how to fix them
Compliance Deadlines: When Must Your Agency Act?
The deadline depends on your jurisdiction’s population size . Note that recent Interim Final Rule (IFR) updates have extended these dates .
| Government Type | Compliance Deadline |
|---|---|
| State & local governments with 50,000+ population | April 26, 2027 (extended from April 2026) |
| State & local governments with fewer than 50,000 population | April 26, 2028 |
| Special district governments (e.g., utility districts, transit authorities, mosquito abatement districts) | April 26, 2028 |
How to calculate population: Use the 2020 decennial Census for most entities. Independent school districts should use the 2022 Small Area Income and Poverty Estimates from the Census Bureau .
Important: If your entity is part of a larger government (e.g., a city police department within a city), use the parent jurisdiction’s population—not the number of employees or people served .
What Content Must Be Accessible?
The rule applies to all web content and mobile apps that a public entity “provides or makes available, directly or through contractual, licensing, or other arrangements” .
This includes:
Government websites and all web pages
Mobile applications
Electronic documents (PDFs, Word, PowerPoint, Excel files)
Social media posts made by the agency
Multimedia content (videos with audio)
Content provided by third-party vendors
Crucially, agencies bear full responsibility for third-party content. If a city contracts with a vendor to build its website or provide a mobile payment app, that vendor’s work must meet WCAG 2.1 Level AA standards—and the city is ultimately responsible .
Five Exceptions to Know
Not all content must be remediated. The rule includes five narrow exceptions :
| Exception | Description |
|---|---|
| 1. Archived content | Content created before the compliance date, retained exclusively for reference/research/recordkeeping, not updated, and clearly identified as archived |
| 2. Pre-existing conventional electronic documents | PDFs, Word, PowerPoint, and Excel files created before the compliance date—unless they are currently used to apply for, gain access to, or participate in government services |
| 3. Third-party content | Content posted by third parties not acting at the agency’s behest (e.g., public comments, social media posts from the public) |
| 4. Password-protected individual documents | Documents about a specific person, property, or account that are password-protected (e.g., individual water bills) |
| 5. Pre-existing social media posts | Social media posts created before the compliance date |
⚠️ Important: The archived content exception cannot be used as a loophole. If content is updated for any reason, it loses the exception and must be made accessible. And the exception only applies if content meets all four criteria for archived status .
Action Steps: Preparing for Compliance
Federal guidance recommends a proactive, phased approach :
1. Learn the Requirements
Review the DOJ’s Fact Sheet, Small Entity Compliance Guide, and the full rule text at ada.gov
Understand that WCAG 2.1 Level AA is the minimum standard—not a suggestion
2. Identify Your Compliance Deadline
Calculate your jurisdiction’s population using Census data
Confirm whether you’re a special district government with the later deadline
3. Build Your Team
Think broadly about who needs to be involved: IT staff, web developers, procurement officers, content creators, ADA coordinators, legal counsel
Set clear expectations for each role so there’s no confusion about responsibility
Consider resources—do you have in-house expertise, or will you need to work with accessibility consultants?
4. Develop an Accessibility Policy
Create a written digital accessibility policy that adopts WCAG 2.1 Level AA as the standard
Include a plan for remediation of existing content, with priority given to high-traffic pages and critical services
5. Ensure New Content is Accessible
All new and modified web pages, documents, and content must be accessible from day one
Check HTML, use alt tags for images, ensure forms and tables are accessible
Provide documents in HTML or text-based formats (not just PDF)
6. Train Staff
Ensure all in-house staff and contractors responsible for web content development are properly trained
Build accessibility into content workflows from the start
7. Provide a Feedback Mechanism
Post a telephone number or email address on your homepage for visitors to request accessible information
Establish procedures for quick response to such requests
8. Test with Users
Periodically enlist disability groups to test your pages for ease of use
Use this feedback to continuously improve accessibility
Key Resources for Government Web Developers
| Resource | What It Provides |
|---|---|
| ADA.gov | Official DOJ guidance, fact sheets, compliance tools |
| Section508.gov | Technical assistance, training, and guidance for federal agencies |
| W3C Web Accessibility Initiative (w3.org/WAI) | WCAG guidelines, checklists, and implementation resources |
| USWDS (designsystem.digital.gov) | U.S. Web Design System for building accessible, mobile-friendly government websites |
| Access Board (access-board.gov) | Information on Section 508 standards and ICT accessibility |
Consequences of Noncompliance
While the rule doesn’t list specific penalties, entities that fail to comply may face:
DOJ enforcement actions
Office for Civil Rights complaints
Private lawsuits under the ADA
Loss of federal funding
Note: Even where full compliance would create an undue burden, agencies must still take alternative steps to provide meaningful access to individuals with disabilities .
Final Thoughts
The new ADA digital accessibility requirements represent a significant shift from general obligations to specific, enforceable technical standards. With deadlines approaching in 2027 and 2028, government agencies have a window of opportunity to plan, remediate, and build systems for ongoing compliance.
The goal is clear: ensure that all citizens—regardless of disability—can access government services with substantially equivalent ease of use .
Start now. Assess your current website, identify your compliance team, and begin prioritizing the most critical pages and services. Creating accessible digital content isn’t just about avoiding legal risk—it’s about serving all members of your community equitably and effectively.
We’re offering a free ADA compliance audit. View more here.
This article is for informational purposes only and does not constitute legal advice. Government entities should consult with legal counsel regarding their specific compliance obligations.