The internet is full of panicky articles about the April 24, 2026 ADA deadline. Most of them are trying to sell you something. Here's what's actually happening, who it affects, and what you should do about it. From a developer's perspective.
What's the Deadline?
On April 24, 2026, state and local government entities serving populations of 50,000+ must have web content and mobile apps that conform to WCAG 2.1 Level AA.
Smaller entities (under 50,000) get until April 26, 2028.
This is a DOJ rule under Title II of the ADA (which covers government entities).
Does This Apply to Private Businesses?
Not directly. The April 2026 rule specifically targets government entities.
But here's the nuance that matters: Title III of the ADA covers "places of public accommodation". And courts have increasingly ruled that websites fall into this category. Over 4,000 ADA website accessibility lawsuits were filed against private businesses in 2023 alone.
The April deadline doesn't create new obligations for private businesses. But it:
- Sets WCAG 2.1 AA as the explicit standard (previously it was implied)
- Increases public awareness
- Gives plaintiff attorneys more ammunition
If you build websites for clients, expect more questions about this.
For EU Developers: You're Already Late
The European Accessibility Act (EAA) deadline was June 28, 2025. It's already passed. The EAA applies to ALL private businesses selling products or services in the EU. If your client has EU customers, they should already be compliant.
What WCAG 2.1 AA Actually Requires
Skip the 78-page spec. Here's what matters for developers:
The Big 5 (fix these and you're 70% there)
Alt text on images — Every non-decorative
<img>needsalt. Decorative images getalt="".Form labels — Every
<input>,<select>,<textarea>needs an associated<label>oraria-label.Color contrast — Text needs 4.5:1 ratio against background (3:1 for large text). Use WebAIM's contrast checker.
Keyboard navigation — Every interactive element must be reachable and usable via keyboard alone. Tab order should be logical.
Heading hierarchy — Use
<h1>through<h6>in order. Don't skip levels. Don't use headings just for styling.
The Next 5 (for AA compliance)
-
Language declaration —
<html lang="en">(or appropriate language code) - Link purpose — Links should make sense out of context. No "click here."
- Error identification — Form errors must be clearly described in text.
- Resize support — Content usable at 200% zoom without horizontal scrolling.
- Focus visibility — Interactive elements must have visible focus indicators.
What NOT to Do
Don't Install an Accessibility Widget
AccessiBe was fined $1 million by the FTC in 2024 for making false claims about their AI-powered accessibility widget. Overlay widgets:
- Don't fix underlying code issues
- Can interfere with actual assistive technology
- Give a false sense of compliance
- Won't protect you in a lawsuit
Don't Panic-Buy an Enterprise Tool
If you're a solo dev or small agency, you don't need Siteimprove ($5k+/year) or Level Access. A good scanner + manual testing covers most needs.
Don't Ignore It
"We'll deal with it later" is how businesses get demand letters. The basics take a few hours to fix.
What TO Do
1. Scan Your Sites
Run an automated scan to find the low-hanging fruit. Tools:
- AccessiGuard — free scan, 22 WCAG checks (full disclosure: I built this)
- WAVE — browser extension
- axe DevTools — Chrome extension
- Lighthouse (built into Chrome DevTools)
No single tool catches everything. Use 2-3.
2. Fix the Automated Issues
Alt text, labels, headings, lang attribute — these are mechanical fixes. A developer can knock out 80% of automated issues in a day.
3. Manual Testing
Automated tools catch ~30-40% of issues. For the rest:
- Keyboard test: Tab through your entire site without a mouse
- Screen reader test: Try NVDA (Windows) or VoiceOver (Mac) on key pages
- Zoom test: Set browser to 200% zoom and check layout
4. Set Up Monitoring
Accessibility is ongoing. Sites change. New content gets added. A monthly scan catches regressions before they become problems.
The Business Case (For When Clients Push Back)
- Legal risk: Average ADA settlement is $5,000-25,000. Annual scanning costs $348.
- Market size: 26% of US adults have a disability (CDC). That's customers you're excluding.
- SEO benefit: Many accessibility improvements (alt text, headings, semantic HTML) directly improve SEO.
- April 24 creates urgency: Even if the rule doesn't directly apply, the attention spike increases lawsuit risk.
TL;DR
- April 24, 2026 deadline is for government entities, but affects everyone indirectly
- WCAG 2.1 AA is the standard — fix alt text, labels, contrast, keyboard nav, headings
- Don't buy widgets. Do fix your code.
- Scan → fix → test manually → monitor
Top comments (0)