ADA Title II: Your Government Website Becomes Illegal in 12 Months

On April 26, 2027, every government website in America serving 50,000+ people becomes legally required to meet WCAG 2.1 Level AA standards. We scanned 15 municipal websites in Nevada. 14 of them would fail today.

This is not a suggestion. It is not a best practice. It is a federal rule published by the Department of Justice, and it carries real enforcement teeth: lawsuits, settlement costs, loss of federal funding, and mandatory remediation under court order.

If you run a city website, a county portal, a public school district site, a transit authority page, or any digital property tied to a state or local government entity, this applies to you. The clock started in April 2024. You have 12 months left.

What the Rule Actually Says

On April 24, 2024, the Department of Justice published a final rule under Title II of the Americans with Disabilities Act. Title II covers state and local governments — every city, county, school district, public university, transit authority, water district, and public agency in the country.

The rule does one specific thing: it defines what "accessible" means for government websites and mobile apps. Before this rule, the ADA said government services had to be accessible to people with disabilities, but it never specified a technical standard. Courts were left to figure it out case by case. That ambiguity is over.

The standard is now WCAG 2.1 Level AA. That is the Web Content Accessibility Guidelines, version 2.1, conformance level AA. It is published by the World Wide Web Consortium (W3C) and it is the same standard used by the European Union, Canada, Australia, and most of the developed world.

The Deadlines

• April 26, 2027: All state and local government entities serving populations of 50,000 or more must comply.
• April 26, 2028: All state and local government entities serving populations under 50,000 must comply.

There is no extension mechanism. There is no waiver process. There is no "good faith effort" exception. You either meet WCAG 2.1 AA on the deadline or you are in violation of federal law.

What Is Covered

The rule applies to all web content and mobile applications that a government entity uses to provide services, programs, or activities to the public. That includes:

• Your main website
• Online payment portals (utilities, permits, fines)
• Meeting agendas and minutes (including posted PDFs)
• Job application systems
• Public records portals
• Park and recreation registration systems
• Mobile apps
• Third-party content you embed or link to as part of your services

If a resident needs it to interact with their government, it must be accessible. Period.

What WCAG 2.1 AA Actually Means

WCAG 2.1 Level AA has 50 individual success criteria organized under four principles: Perceivable, Operable, Understandable, and Robust. Here is what that means in plain English, with the specific issues we see on government websites every day.

Every Image Needs Alt Text

Every non-decorative image on your site must have a text description that conveys the same information the image does. A photo of your city council? The alt text should say who is in the photo. A chart showing budget allocation? The alt text (or a nearby data table) must convey the same data. An icon that links to a PDF? The alt text must describe the link destination, not say "icon" or "image." We routinely find government sites with 200+ images missing alt text entirely.

Every Form Needs Proper Labels

Every input field in every form must have a programmatically associated label. That means a <label> element with a for attribute that matches the input's id. Placeholder text inside the field does not count. If your online permit application has 30 fields and none of them have proper labels, a screen reader user cannot fill it out. That is a Title II violation.

Color Contrast Must Meet 4.5:1

Normal text must have a contrast ratio of at least 4.5:1 against its background. Large text (18pt or 14pt bold) must meet 3:1. This sounds obscure until you look at how many government sites use light gray text on white backgrounds, or put text over busy photographs without a solid overlay. A contrast checker takes 10 seconds to run. Most government sites have dozens of failures.

Keyboard Navigation Must Work

Every interactive element — links, buttons, form fields, dropdown menus, modal dialogs, date pickers — must be operable using only a keyboard. No mouse required. Many custom JavaScript components (hamburger menus, tabbed interfaces, accordion panels, custom dropdowns) are completely invisible to keyboard users. They press Tab and the focus jumps right past the interactive element. This is one of the most common and most serious accessibility failures we find.

Videos Need Captions

Every video with audio must have synchronized captions. Not auto-generated captions full of errors — accurate captions that convey the spoken content and identify speakers. Every pre-recorded video also needs an audio description track or a text transcript for visual content that is not conveyed by the audio alone. City council meeting recordings, public hearing videos, instructional content — all of it needs captions. YouTube auto-captions are a start, but they typically have a 10-15% error rate and do not identify speakers.

PDFs Must Be Accessible

This is where the majority of government websites will fail. Most government sites have hundreds or thousands of PDFs: meeting agendas, budgets, reports, forms, policies, ordinances. If those PDFs were created by scanning a paper document, they are images, not text. A screen reader sees nothing. Even PDFs generated from Word or other software often lack proper heading structure, reading order, alt text on images, and tagged table structures. Remediating a backlog of 500+ inaccessible PDFs is the single most expensive and time-consuming part of compliance for most agencies.

Mobile Accessibility Is Required

WCAG 2.1 added specific criteria for mobile: touch targets must be at least 44x44 CSS pixels, content must work in both portrait and landscape orientation, and functionality that uses device motion (like "shake to undo") must have an alternative. If your mobile site has tiny buttons that are impossible to tap accurately, or if your responsive layout breaks accessibility features that work on desktop, you are not compliant.

Why Most Government Sites Will Fail

We have audited government websites across Nevada and neighboring states. The patterns are consistent. Here are the five issues that appear on nearly every site we review.

PDFs Uploaded as Scanned Images

A staff member scans a printed document and uploads the PDF to the website. It looks like a document. It is actually a picture of a document. A screen reader cannot read it. A search engine cannot index it. A user cannot select or copy the text. We regularly find 60-80% of a government site's PDF library consisting of scanned, inaccessible documents. Some agencies have 10,000+ PDFs in this state.

Custom JavaScript That Breaks Screen Readers

The web developer built a beautiful interactive map, a custom dropdown menu, a tabbed content area, or a modal popup. It looks great. It works perfectly with a mouse. It is completely invisible to screen readers and unreachable by keyboard. Custom interactive components need ARIA attributes (roles, states, properties) and keyboard event handlers to be accessible. Most do not have them.

Videos Without Captions

City council meetings, public hearings, department presentations, promotional videos — uploaded to YouTube or embedded directly, with no captions or only auto-generated captions full of errors. For a Deaf resident trying to follow a public hearing about a zoning change that affects their property, this is not a minor inconvenience. It is exclusion from civic participation.

Color Contrast Failures

Government websites love blue. Light blue text on white backgrounds, dark blue text on medium blue backgrounds, gray text everywhere. Run any government site through a contrast checker and you will find 20-50 contrast failures on the homepage alone. Navigation links, footer text, form helper text, button labels — all below the 4.5:1 minimum.

Inaccessible Meeting Agendas and Public Documents

The documents that matter most to civic engagement — meeting agendas, budgets, planning documents, public notices — are typically the least accessible. They are posted as untagged PDFs, or as Word documents that were never checked for accessibility, or as scanned images. A resident using assistive technology cannot read the agenda for tonight's city council meeting. They cannot review the proposed budget. They cannot access the public notice about a construction project on their street.

What Happens When You Miss the Deadline

The consequences are not hypothetical. ADA web accessibility lawsuits have been filed against government entities for years, even without this specific rule. Now that the standard is defined, enforcement will accelerate.

ADA Lawsuits

Federal ADA lawsuits related to web accessibility have increased roughly 300% since 2018. The majority have targeted private businesses, but government entities are not immune. Advocacy organizations like the National Federation of the Blind and local disability rights groups regularly file complaints and lawsuits against municipalities with inaccessible websites. Once the April 2027 deadline passes, the legal standard becomes clear-cut: either your site meets WCAG 2.1 AA or it does not. There is no ambiguity for a court to interpret.

DOJ Enforcement Actions

The Department of Justice can investigate and take enforcement action against any state or local government entity that violates Title II. This can result in consent decrees — court-supervised agreements that require you to remediate your site on a specific timeline, hire accessibility consultants, conduct regular audits, train staff, and report compliance progress. You do not get to set the terms. The DOJ does.

Settlement Costs

Typical ADA web accessibility settlements for government entities range from $50,000 to $300,000, depending on the scope of violations and the size of the entity. That figure includes damages, plaintiff attorney fees, and the cost of remediation that the settlement requires. Some settlements have exceeded $500,000. The irony: proactive compliance costs a fraction of what a single lawsuit settlement costs.

Federal Funding at Risk

Title II compliance is tied to eligibility for federal funding. Agencies that receive federal financial assistance — which includes virtually every city, county, and school district in America through one program or another — can face funding reviews and potential loss of funds for ADA violations. This is the risk that gets the attention of elected officials faster than anything else.

Public Embarrassment

ADA lawsuits are public record. Consent decrees are public record. When your city gets sued because a blind resident cannot pay their water bill online, that makes the local news. When the settlement terms include an admission that your website was inaccessible to people with disabilities, that is not a good look for any elected official. The political cost is real.

The Fix: What It Actually Takes

Here is the honest assessment. Accessibility compliance is not a one-time checkbox. It is a process. But it is a manageable process with predictable costs and timelines if you start now.

Step 1: Audit (2-4 Weeks, $2,500-$7,500)

A comprehensive accessibility audit combines automated scanning tools with manual testing by accessibility specialists, including testing with actual assistive technologies (screen readers, keyboard-only navigation, voice control). Automated tools catch about 30-40% of WCAG violations. The rest require human judgment — reading order, meaningful alt text, logical heading hierarchy, usable focus management. The deliverable is a detailed report of every violation, prioritized by severity and page traffic, with specific remediation instructions.

Step 2: Remediation (4-12 Weeks, $10,000-$50,000)

The cost range is wide because it depends on what you find. A well-built site with minor contrast issues and missing alt text? Four weeks, lower end. A site built on a 15-year-old CMS with 2,000 inaccessible PDFs, custom JavaScript components with no ARIA support, and embedded third-party widgets? Twelve weeks, upper end. Common remediation tasks include:

• Adding alt text to all images
• Fixing color contrast across the entire site
• Adding proper form labels and error handling
• Rebuilding navigation and interactive components for keyboard access
• Adding ARIA attributes to custom widgets
• Remediating PDF documents (or replacing them with accessible HTML)
• Adding captions to all video content
• Fixing heading hierarchy and page structure
• Ensuring mobile touch targets meet size requirements

Step 3: Ongoing Monitoring ($500-$2,000/Month)

Every time someone on your staff uploads a new PDF, adds a page, embeds a video, or updates content, they can introduce new accessibility violations. Ongoing monitoring includes automated scanning on a weekly or monthly schedule, manual spot checks of new content, and alerts when violations are detected. This is what prevents you from fixing everything once and then slowly drifting back into non-compliance as your site evolves.

Step 4: Staff Training (Included in Any Good Engagement)

The people who create and publish content on your website need to understand accessibility basics: how to write alt text, how to create accessible PDFs, how to use heading levels correctly, how to check contrast before publishing. This is not a full-day workshop. It is 2-3 hours of practical, role-specific training. Without it, your remediation work degrades within months as new inaccessible content is published daily.

Realistic Timeline

If you start today, here is what the next 12 months look like:

• Month 1: Audit completed. Prioritized remediation plan in hand.
• Months 2-4: Critical violations fixed (keyboard navigation, form labels, major contrast issues). Highest-traffic pages compliant.
• Months 5-8: Full site remediation. PDF backlog addressed. Video captions completed.
• Months 9-10: Staff training. Ongoing monitoring implemented. Policies updated.
• Months 11-12: Final audit to confirm compliance. Documentation prepared for any future inquiries.

That is a comfortable timeline. It is not rushed. But it only works if you start now. If you wait until October 2026, you are in crisis mode. If you wait until January 2027, you are likely going to miss the deadline.

Start Here: Free Accessibility Scan

We work with government agencies and public entities across Nevada to audit, remediate, and monitor website accessibility. We know what the DOJ rule requires because we have read the 192 pages of regulatory text and the 1,600+ public comments. We know what auditors look for because we do this work every day.

Here is what we offer to get you started:

• Free initial scan: We run your site through our accessibility scanning tools and deliver a summary of critical violations — no cost, no commitment. You will know within a week where you stand.
• Full audit: A comprehensive manual + automated audit with a prioritized remediation roadmap.
• Remediation: Our team fixes the violations. We work with your CMS, your content, your vendor ecosystem.
• Ongoing monitoring: Monthly scanning, new content checks, and staff support to keep you compliant after remediation.

The deadline is April 2027. Twelve months from now, your website either meets the standard or it does not. The cost of compliance is predictable. The cost of a lawsuit is not.