April 2024, the DOJ issued a final rule under ADA Title II, requiring state and local government websites to meet WCAG 2.1 Level AA standards. The rule's compliance deadline is April 2026 — meaning enforcement is either active or imminent depending on your jurisdiction. If you run a government-affiliated or publicly-facing site and haven't touched accessibility since the ruling dropped, you're already exposed.
This guide is for founders, product managers, and web teams who need a plain-English breakdown of what the ADA's website requirements actually are, what the 2026 deadline means in practice, and — most importantly — what to do about it right now.
What Is the ADA Title II Rule?
The Americans with Disabilities Act (ADA) is a civil rights law from 1990 that prohibits discrimination against people with disabilities. Title II of the Act has always applied to state and local governments — public agencies, courts, schools, transit authorities. What changed in April 2024 is that the DOJ finalized specific web accessibility standards for the first time.
Until the Title II rule, there was no legally codified technical standard for "ADA-compliant websites." Courts used the vague standard of "effective access" and the informal WCAG 2.0 guidelines as a reference. That ambiguity is gone. The rule explicitly references WCAG 2.1 Level AA as the compliance benchmark. That's 38 success criteria across four principles (Perceivable, Operable, Understandable, Robust) — and the bar is not optional.
The rule covers all digital services a government entity offers: websites, mobile apps, online portals, self-service tools. If your product or company has any government affiliation, contracts with government agencies, or receives public funding, the rules may apply to you.
Who Does the ADA Website Requirements Apply To?
Primary targets: State and local government agencies, public schools, municipal utilities, state courts, transit authorities, and any organization receiving government funding that offers a public-facing digital service.
For those organizations, the April 2026 deadline is real and not optional. Failure to comply risks losing federal funding and faces DOJ enforcement actions.
The broader risk for private businesses: The ADA Title III applies to "places of public accommodation" — which courts have interpreted broadly to include websites. Over 4,000 ADA web accessibility lawsuits are filed each year, and the trend is up sharply. There is no "small business exception." The legal standard is applied to your website, not your building.
If you serve the public — retail, SaaS, healthcare, finance, education — you're at risk. The 2026 deadline hasn't created a grace period for private businesses. The lawsuits haven't stopped waiting.
What Is the WCAG 2.1 Level AA Standard?
WCAG (Web Content Accessibility Guidelines) is the technical standard that defines what "accessible" means on the web. It's maintained by the W3C and updated on a published roadmap. The ADA Title II rule references WCAG 2.1 Level AA as the minimum requirement.
The "Level AA" designation means compliance requires meeting all Level A criteria plus all Level AA criteria. Level A is the minimum floor — it's not optional, but it's also not sufficient for compliance. You need both.
Here are the most common WCAG 2.1 Level AA criteria that determine whether your site passes or fails an accessibility audit:
- 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. Most design tools enforce this — until someone exports a custom color without checking.
- 1.4.4 Resize Text — Text must be resizable up to 200% without loss of content or function. Fixed font sizes (px instead of rem/em) are the most common violation.
- 2.1.1 Keyboard — All functionality must be operable by keyboard alone. No mouse required. This catches interactive components built without keyboard navigation in mind — modals, dropdown menus, custom controls.
- 2.4.7 Focus Visible — Keyboard focus indicators must be clearly visible. Default browser outlines are often overridden by CSS resets or custom styling that removes them entirely.
- 3.1.2 Language of Parts — The language of multi-language pages must be programmatically determinable. A page with English body copy and French headings needs a lang attribute on each section.
- 3.3.1 Error Identification — Input errors must be programmatically identified and described in text. "Invalid field" is not a compliant error — it must specify what went wrong.
- 3.3.2 Labels or Instructions — Form inputs must have visible labels. Placeholder text is not a label — it disappears when a user starts typing and is invisible to screen readers.
That's a partial list. WCAG 2.1 has 38 success criteria at Level AA. A comprehensive audit checks all of them.
The Practical 2026 Compliance Checklist
Legal requirements are abstract until you turn them into fix-it lists. Here's the checklist most auditors start with — the issues that account for the majority of failures found on government and commercial sites alike.
1. Add alt text to every image
Every non-decorative image needs a text alternative that conveys the same information or function. Product photos need descriptive alt text ("Blue ceramic mug, 12oz capacity"), not filenames ("img_1247.jpg"). Decorative images can use an empty alt attribute so screen readers skip them.
2. Make your entire site keyboard-navigable
Test: press Tab on your homepage. Can you reach every link, button, form field, and interactive element without touching your mouse? If you hit a dead end, that's a failure. Common culprits: dropdown menus that close on Tab instead of staying open, modals that trap focus, and image carousels with no keyboard controls.
3. Fix your color contrast ratios
Run your primary pages through a contrast checker. Target 4.5:1 for body text, 3:1 for large text and UI components. Pay special attention to: button text on button backgrounds, link text on page backgrounds, placeholder text (which also needs to be legible), and error states on form fields — these are often missed even on sites that pass a general contrast check.
4. Label every form field
Every input needs a visible label — not placeholder text, not a heading above the field. The label must be programmatically associated with the input via a for/id relationship or a wrapped label. Password fields, email inputs, search boxes — every one of them needs a label visible at all times.
5. Make focus indicators visible
Find your CSS rule that sets outline: none on focusable elements. Remove it or replace it with a custom focus style that meets the 3:1 contrast requirement. This is the single most common "unintentional" accessibility violation — it happens when a CSS reset for visual consistency removes the browser's default focus indicator without providing a replacement.
6. Add captions to all video content
All pre-recorded video needs captions. Live video needs captions or a real-time text equivalent. Captions must include dialogue, speaker identification when multiple speakers are present, and relevant non-speech audio (sound effects, music cues that carry meaning).
7. Provide a text equivalent for audio-only content
Podcasts, audio guides, recorded interviews — anything that conveys information through audio must have a text transcript. This isn't just for screen reader users — it's required for users in loud environments, non-native speakers, and anyone who prefers reading.
8. Check for keyboard traps in interactive components
Modals, lightboxes, and custom dropdowns are the most common keyboard traps. A trap is any interaction that doesn't allow Tab to continue through the interface in a logical order. Test every modal and interactive widget with keyboard only before launch.
9. Write in plain language
WCAG 3.1.5 (Reading Level) recommends content written below the advanced reading level. For government sites especially, plain language is a legal standard in many states. Avoid jargon, unexplained acronyms, and passive voice. Readability tools are free — use them.
10. Validate your code for programmatic correctness
Accessibility is not just a content problem — it's a code problem. Missing lang attributes, malformed tables, improperly nested headings, and missing form labels all fail programmatically even when they look fine visually. Automated tools catch code-level issues; manual review catches content and interaction issues.
What Happens If You Miss the ADA Deadline?
For government entities: the DOJ can pursue enforcement actions, including demand letters, negotiated settlements, and court orders requiring compliance. Federal funding can be reviewed or withheld. The reputational cost in a public procurement context is also significant.
For private businesses: the more immediate risk is litigation. ADA website lawsuits have been filed against companies of every size, across every industry. The legal standard — "effective access" — is applied by courts, and plaintiffs' attorneys are well-versed in using WCAG criteria as a checklist to document violations. Settlement costs are typically $10,000–$75,000 for a documented case. The cost of an audit and fix is a rounding error in comparison.
There is no grace period. The deadline sets the enforcement timeline — it doesn't create a safe harbor before the lawsuits stop coming.
How to Audit Your Website for ADA Compliance in 60 Seconds
Before you hire an accessibility consultant, run a free automated audit. Parallax crawls your website against WCAG 2.1 Level AA criteria — including contrast ratios, form labels, keyboard navigation, alt text, and focus indicators — and returns a severity-ranked report in under 5 minutes.
You get a specific list of what fails, why it fails, and what to fix first. No account required. No credit card. Immediate results.
Check your site's accessibility in 60 seconds — free →
The 2026 deadline isn't hypothetical. The enforcement actions are happening. The lawsuits are being filed. Fix the compliance issues while you still have the opportunity to do it quietly — before the window closes.