⚠️ Deadline Alert

April 24, 2026: Deadline for government entities serving 50,000+ people. April 24, 2027: Deadline for smaller entities. These are federal requirements under the Americans with Disabilities Act.

What Is ADA Title II?

Title II of the Americans with Disabilities Act (ADA) prohibits discrimination against people with disabilities by state and local governments. In April 2024, the U.S. Department of Justice (DOJ) published a final rule clarifying that this includes digital accessibility — specifically, websites and mobile applications.

The rule adopts WCAG 2.1 Level AA as the technical standard that government websites must meet. This is the first time the federal government has set a specific technical standard for web accessibility under the ADA.

Who Must Comply?

The ADA Title II rule applies to state and local government entities, which include:

State agencies and departments
City and county governments
Public school districts and universities
Public libraries and transit authorities
Courts, jails, and other government facilities
Any entity that receives federal financial assistance and is considered a public entity

Private businesses are not directly covered by this specific rule, but they remain subject to ADA Title III, which has its own accessibility requirements. Private companies doing business with government entities may also face contractual obligations.

What Does WCAG 2.1 Level AA Require?

WCAG 2.1 Level AA is a set of 50 success criteria organized around four principles, known as POUR:

Perceivable: Information must be presentable in ways users can perceive. This includes providing text alternatives for images, captions for videos, and sufficient color contrast.
Operable: All functionality must be accessible via keyboard navigation. Users must be able to navigate without a mouse, and there must be no content that causes seizures.
Understandable: Content must be readable and predictable. Error messages must be clear and helpful.
Robust: Content must be compatible with assistive technologies including screen readers, magnification software, and voice control.

Key Compliance Deadlines

Entity Type	Population Served	Compliance Deadline
State/local government (large)	50,000 or more	April 24, 2026
State/local government (small)	Under 50,000	April 24, 2027

What Happens If You Miss the Deadline?

Non-compliance with ADA Title II can result in:

DOJ enforcement actions: The Department of Justice can investigate complaints and initiate enforcement proceedings.
Private lawsuits: Individuals can sue under Title II for injunctive relief and attorney's fees.
Federal funding consequences: Non-compliant entities may risk their federal funding.
Reputational damage: Public entities face scrutiny from advocacy groups, journalists, and constituents.

Common Accessibility Failures to Fix First

Based on automated scans of thousands of government websites, these are the most common WCAG 2.1 AA failures:

Missing alternative text on images — Every non-decorative image needs an alt attribute describing its content.
Insufficient color contrast — Body text must have a 4.5:1 contrast ratio against its background. Large text requires 3:1.
Forms without proper labels — Every form input must have an associated <label> element or aria-label.
Missing skip navigation links — A "skip to main content" link at the top of every page helps keyboard users bypass repetitive navigation.
Videos without captions — All pre-recorded video content needs accurate closed captions.
Non-keyboard-accessible interactive elements — Dropdowns, modals, and custom widgets must work with keyboard alone.
Missing page language — Every HTML document should have a lang attribute on the <html> tag.
Focus indicators removed — Never set outline: none without providing an alternative visible focus indicator.

How to Audit Your Website Before the Deadline

A comprehensive accessibility audit involves both automated testing and manual review. Automated tools can catch approximately 30–40% of accessibility issues, so both approaches are necessary.

Step 1: Run an Automated Scan

Start with a free automated accessibility scanner to get an overview of issues. FixMyWeb provides a free WCAG 2.1 AA scan with 201 automated checks across your entire page. The scan runs in under 60 seconds and generates a prioritized list of issues with fix recommendations.

Step 2: Conduct Keyboard Testing

Navigate your entire website using only the Tab, Shift+Tab, Enter, Space, and arrow keys. You should be able to reach every link, button, and form field. Focus should always be visible. If you get stuck anywhere, that is an accessibility barrier.

Step 3: Test with a Screen Reader

Use a free screen reader such as NVDA (Windows), VoiceOver (Mac/iOS), or TalkBack (Android) to navigate your website. Listen to how content is announced. Check that images have meaningful descriptions, that form fields are properly labeled, and that the page structure makes logical sense when read linearly.

Step 4: Check Color Contrast

Use a browser extension or the built-in contrast checker in browser developer tools to verify all text meets the required contrast ratios. Pay special attention to:

Gray text on white backgrounds (very commonly fails)
Colored text on colored backgrounds
Text over images or gradients
Placeholder text in form fields

Step 5: Review Videos and Documents

Audit all video content for captions, audio descriptions for visual-only content, and ensure PDF documents are tagged for accessibility. Government entities often have large libraries of documents that require remediation.

Creating an Accessibility Remediation Plan

Given the volume of issues most government websites have, a systematic remediation approach is essential:

Prioritize high-traffic pages first — Fix your homepage, main service pages, and contact pages before less-visited content.
Address barriers, not just failures — Focus on issues that prevent users from completing key tasks (applying for services, accessing information, submitting forms).
Fix templates and components — Fixing a shared header or navigation component fixes the issue across every page at once.
Document your progress — Maintain an accessibility statement on your website describing your current conformance level and remediation timeline.
Test with real users — Involve people with disabilities in testing for issues that automated tools cannot detect.

Accessibility Statements and Documentation

The DOJ rule requires covered entities to provide a way for individuals to request accessible versions of content or report accessibility problems. Best practice includes:

An accessibility statement page describing conformance status
Contact information for accessibility issues (email or phone)
A process for responding to requests within a reasonable timeframe
A grievance procedure for formal complaints

Get a Free Accessibility Scan Today

The April 2026 deadline is here. If your government website has not yet been audited for WCAG 2.1 AA compliance, start immediately. Use FixMyWeb to run a free 201-point scan and get a clear picture of where you stand.

Scan your website free now →

The scan takes under 60 seconds, requires no sign-up, and gives you a detailed report of every accessibility issue found — along with specific, actionable recommendations to fix each one.

ADA Title II Web Accessibility Deadline 2026: Is Your Website Ready?