ADA Title II Compliance Guide

The April 24, 2026 Deadline Is Real

The DOJ requires state and local government websites serving 50,000+ people to meet WCAG 2.1 AA standards by April 24, 2026, backed by DOJ enforcement, private lawsuits and federal-funding obligations. Key Facts:

• On April 24, 2024, the DOJ published its final rule under ADA Title II , requiring state and local government websites and mobile apps to conform to WCAG 2.1 Level AA .
• Entities serving populations of 50,000 or more must comply by April 24, 2026 . Entities serving under 50,000 have until April 24, 2027.
• Thousands of digital accessibility lawsuits are filed in U.S. courts every year, most against private businesses under Title III.
• Consequences include DOJ enforcement, private lawsuits and consent decrees , plus attorney fees, remediation costs, and potential loss of federal funding.
• This guide covers who must comply, what the technical requirements are, how to check your compliance status, and how voice AI can help bridge accessibility gaps.

What Is ADA Title II?

ADA Title II prohibits discrimination by state and local governments and now explicitly requires web content and mobile apps to conform to WCAG 2.1 Level AA. Title II of the Americans with Disabilities Act prohibits discrimination by state and local government entities. Originally enacted in 1990, it covered physical spaces — government buildings, public transit, polling places. For decades, the digital extension remained ambiguous. That changed on April 24, 2024, when the Department of Justice published its final rule (28 CFR Part 35) explicitly requiring that web content and mobile applications provided by state and local governments conform to the Web Content Accessibility Guidelines (WCAG) Version 2.1, Level AA. This is not a recommendation — it is a legally binding federal regulation. The rule applies to all content that a government entity makes available through its website or mobile app: information about services, online forms, document downloads, payment portals, scheduling systems, public meeting materials, emergency alerts, and interactive features like chatbots and virtual assistants. What "Web Content" Means Under the Rule:

• All public-facing web pages and subdomains
• Mobile applications (native and web-based)
• PDF documents and downloadable files
• Online forms, payment systems, and portals
• Video and audio content (captions, transcripts)
• Third-party content embedded on government sites
• Interactive features including chatbots and scheduling tools

Who Must Comply?

Every state and local government entity must comply -- more than 90,000 local governments alone, including counties, cities, school districts, public universities, and transit agencies. ADA Title II applies to every state and local government entity in the United States — all 50 states, territories, counties, cities, towns, school districts, public universities, public transit agencies, public libraries, courts, and special-purpose districts. There is no size exemption. April 24, 2026 Deadline State and local governments serving a total population of 50,000 or more . Includes counties, large cities, state agencies, public universities, and large school districts. April 24, 2027 Deadline State and local governments serving a total population under 50,000 . Includes small towns, rural counties, small school districts, and smaller special districts. While Title II directly covers government entities, the practical impact extends further. Private contractors and vendors providing digital services to governments may need to ensure their products are accessible. Educational institutions receiving federal funding face overlapping obligations under Section 504 and Section 508. And Title III — which covers private businesses — continues to drive parallel enforcement through litigation. The sheer volume of affected organizations is staggering: the U.S. Census Bureau counts over 90,000 local government entities. Add state agencies and state public universities, and the number of organizations that must achieve WCAG 2.1 AA compliance is larger still. Add voice AI to your website in 10 minutes

• Try AnveVoice Free
• • 50K tokens free, no card
• • No credit card required
• • One-line embed

WCAG 2.1 AA: What You Must Implement

WCAG 2.1 AA requires 50 success criteria across four principles: Perceivable, Operable, Understandable, and Robust. Alt text and keyboard access are among the most common failures. WCAG 2.1 Level AA includes 50 success criteria organized under four principles (POUR): Perceivable, Operable, Understandable, and Robust. Here are the most commonly failed criteria and what they require: Content must be presentable in ways all users can perceive. All interface components and navigation must be operable by all users. Content and interface operation must be understandable. Content must be robust enough to work with current and future assistive technologies. Check your site right now: Our free WCAG accessibility checker tests 35 criteria across all four POUR categories plus voice and AI accessibility points.

• Perceivable
• 1.1.1 Non-text Content: All images, icons, and graphics must have meaningful alt text. Decorative images must be marked as such. Missing alt text is one of the most common failures found on the web.
• 1.3.1 Info and Relationships: Use semantic HTML (headings, lists, tables, landmarks) so screen readers can convey document structure. Do not rely solely on visual styling to convey meaning.
• 1.4.3 Contrast (Minimum): Text must have a contrast ratio of at least 4.5:1 against its background. Large text (18pt+ or 14pt bold) needs 3:1. This applies to all text including placeholder text in form fields.
• 1.4.4 Resize Text: Text must be resizable up to 200% without loss of content or functionality. Fixed pixel sizes that prevent browser zoom fail this criterion.
• 1.4.11 Non-text Contrast: UI components (buttons, form fields, icons) and graphical objects require 3:1 contrast against adjacent colors.
• Operable
• 2.1.1 Keyboard: All functionality must be operable through a keyboard interface. No keyboard traps — users must be able to navigate away from every component. Keyboard problems are another frequent failure.
• 2.4.1 Bypass Blocks: Provide a mechanism to skip repeated navigation blocks (skip-to-content links). Screen reader users should not have to tab through 50 navigation links on every page.
• 2.4.6 Headings and Labels: Headings and labels must describe the topic or purpose of the content they introduce.
• 2.5.1 Pointer Gestures: Any functionality using multipoint or path-based gestures must also be operable with a single pointer without path-based gestures.
• Understandable
• 3.1.1 Language of Page: The default human language of each page must be programmatically determined. Set the lang attribute on the HTML element.
• 3.2.1 On Focus: When a UI component receives focus, it must not trigger an unexpected change of context (like a page redirect or form submission).
• 3.3.1 Error Identification: Form errors must be detected and described to the user in text. Color alone cannot indicate an error.
• 3.3.2 Labels or Instructions: Labels or instructions must be provided when content requires user input.
• Robust
• 4.1.2 Name, Role, Value: All user interface components must have accessible names and roles. Custom widgets must use ARIA correctly so screen readers can announce their state and purpose.
• 4.1.3 Status Messages: Status messages (like "form submitted" or "3 results found") must be programmatically determined so assistive technologies can present them without receiving focus.

Penalties for Non-Compliance

Non-compliance triggers DOJ enforcement actions, private lawsuits, consent decrees, and potential loss of federal funding. The consequences of failing to meet ADA Title II web accessibility requirements are severe and multi-dimensional: Civil Monetary Penalties (Title III) Title II itself has no civil-penalty schedule. The DOJ's civil penalties ($75,000 for a first violation and $150,000 for later ones under 28 CFR 36.504, adjusted for inflation since) apply to Title III cases against private businesses. Private Lawsuits Individuals can file lawsuits seeking injunctive relief (court orders to fix the website), compensatory damages, and attorney fees. Defense and settlement costs add up even when a case never reaches trial. DOJ Enforcement Actions The DOJ can investigate complaints, initiate compliance reviews, and enter consent decrees requiring organizations to remediate all issues within a set timeline under court supervision. Loss of Federal Funding Government entities receiving federal funds face potential funding termination under Section 504 of the Rehabilitation Act, which has overlapping accessibility requirements. The litigation landscape has shifted dramatically. AI-driven scanning tools enable plaintiffs' attorneys and pro se filers to identify violations at scale. Automated accessibility scanning generates detailed violation reports usable as evidence, and repeat plaintiffs file many lawsuits each, targeting the most common and easily-detected violations: missing alt text, insufficient contrast, and keyboard inaccessibility. Need help choosing? Book a free 15-minute consultation

How to Check Your Compliance Status

Check compliance through four steps: automated scanning, manual keyboard testing, screen reader testing, and ongoing monitoring with monthly automated scans. A comprehensive accessibility evaluation combines automated testing, manual testing, and assistive technology testing. No single tool catches all issues — automated scanners find only part of the WCAG problems on a page, so manual testing is still required. Start with an automated scan to identify the most common and easily-fixable issues. AnveVoice's free Accessibility Checker tests 35 criteria across all WCAG categories including voice and AI accessibility — areas many checkers don't cover. Run it on your homepage, key landing pages, and most-visited pages first. Navigate your entire site using only a keyboard. Can you reach every interactive element? Can you see where focus is? Can you operate all menus, forms, and widgets? Check that all images have meaningful alt text, headings follow a logical hierarchy, and form fields have visible labels. Test with at least one screen reader: NVDA (free, Windows), VoiceOver (built into macOS/iOS), or JAWS. Navigate key user flows — finding information, completing forms, making payments. Screen readers expose issues that visual inspection and automated tools miss: unlabeled buttons, confusing reading order, and missing live region announcements. Accessibility is not a one-time fix. Every content update, design change, and third-party widget addition can introduce new violations. Establish a regular testing cadence (monthly minimum) and integrate accessibility checks into your deployment pipeline.

• Step 1: Automated Scanning
• Step 2: Manual Testing
• Step 3: Screen Reader Testing
• Step 4: Ongoing Monitoring

How Voice AI Improves Accessibility

Voice AI provides alternative input methods, reads content aloud, guides form completion, and supports 50+ languages -- supporting the goals behind several WCAG principles. Voice AI represents a paradigm shift in web accessibility. Rather than relying solely on screen readers interpreting DOM structure, voice AI provides a direct conversational interface that bypasses many traditional accessibility barriers. Alternative Input Method (WCAG 2.5) Voice commands provide an alternative to mouse and keyboard for users with motor disabilities. AnveVoice's agentic DOM actions let users navigate pages, fill forms, click buttons, and complete multi-step workflows entirely through voice. Content Accessibility (WCAG 1.1, 1.3) Voice AI can read and explain page content aloud, describe images and charts, and answer questions about content — helping users with visual impairments, cognitive disabilities, and low literacy access information without relying on complex assistive technology setups. Form Completion Assistance (WCAG 3.3) Many government forms are complex and inaccessible. Voice AI can guide users through form completion step by step, explain field requirements, validate inputs in real-time, and submit forms on behalf of users who cannot interact with traditional form controls. Multilingual Support (WCAG 3.1) Government services must serve diverse populations. AnveVoice supports 50+ languages with automatic detection, enabling non-English speakers to interact with government websites in their preferred language — a critical accessibility need that goes beyond WCAG technical requirements. Voice AI does not replace the need for proper HTML semantics, keyboard accessibility, and screen reader compatibility. It provides an additional accessibility layer that complements traditional accessibility measures and can make some tasks easier for people with disabilities. Add voice accessibility to your website: AnveVoice installs in 2 minutes with one line of code. No technical expertise required. Free: $0 | Growth: $39/month | Scale: $129/month | Enterprise: custom.

Compliance Action Plan

Start with an audit now, fix critical Level A issues first, address Level AA requirements by April, then establish ongoing monitoring and maintenance. With the April 24, 2026 deadline approaching, here is a recommended timeline for organizations that have not yet started or are mid-way through compliance efforts: Now (March 2026) — Audit Run automated scans on all public-facing web properties. Use AnveVoice's free checker for a quick assessment. Conduct manual keyboard testing on top 20 most-visited pages. Document all findings. March-April 2026 — Remediate Critical Issues Fix Level A issues first (highest severity): missing alt text, keyboard traps, missing form labels, missing language declaration. These are the most commonly targeted in lawsuits and the easiest to detect. April 2026 — Address Level AA Issues Fix contrast ratios, ensure proper heading structure, add skip navigation, fix focus indicators, remediate PDF documents. Deploy voice AI as an alternative access method for complex interactions. Ongoing — Monitor and Maintain Establish monthly automated scans, quarterly manual audits, and accessibility testing as part of your CI/CD pipeline. Train content creators on accessibility requirements. Document your accessibility policy and conformance statement.

Frequently Asked Questions

Answers about Title II scope, compliance deadlines, WCAG levels required, mobile app coverage, voice AI benefits, costs, overlays, and Title II vs III differences.

• • 50K tokens free, no card
• • No credit card required
• • One-line embed

Take Action Before April 24, 2026

Invest in accessibility now to avoid costly litigation, serve constituents better, and build digital infrastructure that works for everyone. The ADA Title II deadline is not a suggestion — it is a legally binding federal requirement backed by DOJ enforcement, private litigation, and federal-funding obligations. More than 90,000 local governments, plus state agencies, must achieve WCAG 2.1 AA compliance, and the plaintiff's bar is more equipped than ever to identify and litigate violations. Start with a free accessibility check using our WCAG Accessibility Checker . Then consider adding voice AI as an accessibility layer — AnveVoice provides hands-free navigation, form completion, and multilingual support that complements your WCAG work while improving the experience for all users. The organizations that invest in accessibility now will avoid costly litigation, serve their constituents better, and build digital infrastructure that works for everyone.