If you're responsible for a government website or mobile app, this guide breaks down exactly what ADA Title II requires, what WCAG 2.1 AA actually means, and how to build a compliance roadmap that works. No legal jargon, just practical guidance you can use today.
In Plain English: What the New DOJ Rule Means for Websites & Mobile Apps
Your digital services are covered under ADA Title II (state & local government 'programs, services, and activities'). Just like wheelchair ramps and braille signage in buildings, your digital properties need accessibility features for people with disabilities.
Mobile apps are included. Any app you offer for public services—whether for paying taxes, reporting issues, or accessing benefits—must meet the same standards.
This is federal law, not guidance. The rule has the force of law with specific deadlines:
• April 2026 for entities serving 50,000+ people
• April 2027 for smaller entities
Real people need this access. 1 in 4 Americans has a disability (per CDC data). They're trying to pay parking tickets, apply for permits, access emergency information, and use the same services everyone else does.
The technical standard is WCAG 2.1 Level AA, but what matters is that citizens with visual, hearing, mobility, and cognitive disabilities can successfully use your digital services. Test your current compliance to see where you stand today.
Who Is Covered: State/Local Government + Vendors
• All state government agencies and departments
• Counties (all sizes, with staggered deadlines)
• Cities and towns
• Special districts (water, transit, library, park districts)
• Public schools and universities
• Any entity receiving state/local government funding
Critical Vendor Alert:
If you build, maintain, or provide digital services for government entities, you're implicated. The government entity remains liable, but they'll require compliance from you through:
• Contract requirements
• Indemnification clauses
• Accessibility warranties
• Regular compliance audits
What This Means:
• Government entities: You're liable even if a vendor built your site
• Vendors: Government clients will require WCAG 2.1 AA compliance
• Third-party tools: That chatbot, payment processor, or document viewer must also comply
Check your state's specific requirements at /states as some have additional obligations beyond federal requirements.
What 'WCAG 2.1 AA' Practically Means
🎯 Headings & Structure
• Use proper heading hierarchy (H1 → H2 → H3)
• Don't skip levels for visual styling
• Each page needs one clear H1
• Screen readers use these to navigate
🖼️ Alt Text for Images
• Every image needs descriptive alt text
• Decorative images need empty alt=""
• Complex graphics need detailed descriptions
• Logos should identify the organization
🎨 Color Contrast
• Regular text: 4.5:1 contrast ratio minimum
• Large text (18pt+): 3:1 contrast ratio
• This includes text over images
• Test with free contrast checkers
📝 Forms & Labels
• Every form field needs a visible label
• Required fields must be clearly marked
• Error messages must be specific
• Instructions can't rely on color alone
⌨️ Keyboard Navigation
• Everything must work without a mouse
• Tab order must be logical
• Focus indicators must be visible
• No keyboard traps (users getting stuck)
🔍 Focus Management
• Users must see where they are
• Custom controls need focus styles
• Modals must trap and return focus
• Skip links help bypass navigation
🎬 Media & Captions
• Videos need synchronized captions
• Audio content needs transcripts
• Live events need real-time captions
• Auto-playing media must be controllable
Need more detail? Visit our comprehensive WCAG explained guide or scan your site to see specific issues.
What's In / What's Out
• Home pages and navigation
• Service pages and applications
• Payment portals
• Public records and documents
• Emergency alerts and updates
• Contact forms and feedback systems
✅ Mobile Apps: Native and web apps for:
• Service delivery
• Payment processing
• Permit applications
• Public reporting
• Information access
✅ Documents: When provided digitally:
• PDFs must be tagged and accessible
• Word documents should use styles
• Spreadsheets need headers
• Presentations need structure
• Forms must be fillable
✅ Multimedia:
• Videos (need captions)
• Podcasts (need transcripts)
• Virtual meetings (need accommodations)
• Social media content (when used officially)
EXCEPTIONS (Limited):
❌ Archived Content: Materials archived before the rule *may* be excluded if:
• Not needed for current services
• Clearly marked as archived
• Alternative access provided if requested
❌ Third-Party Content: Limited exception for:
• Public comments on forums
• User-generated content
• BUT: The platform itself must be accessible
❌ Password-Protected Employee Areas: Internal systems have different requirements under Title I
⚠️ Warning: Exceptions are narrow. When in doubt, make it accessible. Courts rarely accept broad exception claims.
For detailed guidance, see our comprehensive guide or review state-specific requirements.
Roadmap: 30/60/90-Day Remediation Plan
📅 DAYS 1-30: QUICK WINS
Focus on high-impact, low-effort fixes that immediately improve accessibility:
✓ Week 1: Discovery
• Run automated scan on main pages
• Document all digital properties
• Identify responsible parties
• Check current vendor contracts
✓ Week 2-3: Easy Fixes
• Add missing alt text to images
• Fix heading hierarchy
• Increase color contrast
• Add missing form labels
• Ensure focus indicators visible
✓ Week 4: Documentation
• Create accessibility statement
• Set up issue reporting method
• Document what's been fixed
• Plan next phase priorities
🛠️ DAYS 31-60: TEMPLATES & PATTERNS
Build sustainable accessibility into your systems:
✓ Week 5-6: Template Updates
• Fix common headers/footers
• Update CMS templates
• Create accessible components
• Standardize navigation patterns
✓ Week 7-8: Training & Process
• Train content creators
• Create accessibility checklist
• Update procurement requirements
• Establish testing workflow
✅ DAYS 61-90: TESTING & MONITORING
Ensure fixes stick and catch new issues:
✓ Week 9-10: Comprehensive Testing
• Manual keyboard testing
• Screen reader validation
• Mobile accessibility check
• PDF remediation
✓ Week 11-12: Ongoing Compliance
• Implement monitoring tools
• Schedule regular audits
• Update vendor requirements
• Create maintenance plan
- Day 30: 50% of critical issues resolved
- Day 60: 80% WCAG 2.1 AA compliance
- Day 90: Full compliance with monitoring in place
Need help getting started? Scan your site now for a prioritized issue list.
Procurement Language
The Vendor shall ensure all deliverables, including websites, web applications, mobile applications, and digital content, conform to WCAG 2.1 Level AA standards. The Vendor must:
1. Provide a current Voluntary Product Accessibility Template (VPAT) or Accessibility Conformance Report (ACR) 2. Conduct manual accessibility testing in addition to automated testing 3. Remediate any accessibility issues identified within 30 days 4. Provide documentation of accessibility testing methodologies and results 5. Warrant that deliverables will maintain WCAG 2.1 AA compliance throughout the contract term 6. Indemnify [Agency Name] against any accessibility-related claims or lawsuits arising from non-compliant deliverables
Additional Procurement Considerations:
• For New Projects: Require accessibility from day one—it's 3x more expensive to retrofit
• For Existing Vendors: Add accessibility amendments to current contracts
• For Small Purchases: Even small tools must comply if they're public-facing
• For Emergency Contracts: Accessibility requirements can't be waived for urgency
Red Flags in Vendor Responses:
• "We use an overlay for compliance" (overlays don't achieve full compliance)
• "We'll make it accessible after launch" (accessibility must be built in)
• "Our tool is exempt" (very few true exemptions exist)
• No VPAT provided or VPAT is outdated
Verification Questions:
• How do you test with actual assistive technology?
• Which WCAG 2.1 AA criteria does your solution currently not meet?
• What's your remediation timeline for identified issues?
• Can you provide references from other government clients?
Update your procurement process now—before you're locked into non-compliant solutions.
State Specifics
States with Stricter Standards:
• California - Unruh Act adds state liability
• New York - State Human Rights Law applies
• Illinois - Information Technology Accessibility Act
• Texas - DIR accessibility requirements
• Massachusetts - Additional procurement rules
Check Your State's Requirements:
Every state has unique considerations:
• Population-based deadlines
• Number of affected entities
• Recent lawsuit activity
• State-specific laws
• Available resources
Explore our comprehensive State Guides Hub for:
• Your state's specific requirements
• Local lawsuit history
• Compliance resources
• Risk assessment
• Deadline details
High-Risk States Needing Immediate Action:
States with higher litigation volume include:
• California - Highest lawsuit activity
• New York - Very high litigation risk
• Florida - Significant lawsuit volume
• Texas - Growing litigation activity
• Pennsylvania - Increasing legal actions
States with Approaching First Lawsuits:
• North Carolina
• Ohio
• Georgia
• Michigan
• Washington
Don't see your state in the high-risk list? You're not safe—plaintiff firms are expanding geographically. Check your state's profile for current risk assessment.
DIY vs. Vendor
✅ Good Candidates for In-House:
• Simple websites (under 50 pages)
• Sites built on modern CMS platforms
• Teams with HTML/CSS knowledge
• Organizations with time before deadline
• Limited budget scenarios
DIY Approach: 1. Start with our free scanner for baseline 2. Use free tools like WAVE and axe DevTools 3. Follow our WCAG guide 4. Fix issues systematically 5. Test with real users
DIY Advantages:
• Lower direct costs
• Team learns accessibility
• Full control over timeline
• No vendor dependence
DIY Risks:
• Miss complex issues
• Time-intensive
• No liability protection
• Steep learning curve
---
When You Need a Vendor:
✅ Must Use Vendor:
• Complex sites (hundreds of pages)
• Custom applications
• Dynamic content/databases
• Tight deadlines (under 6 months)
• Previous lawsuit/complaint
• No technical staff
Vendor Services:
• Professional audits
• Remediation services
• Ongoing monitoring
• Legal documentation
• Training programs
• Indemnification (sometimes)
Choosing a Vendor:
• Require WCAG 2.1 AA guarantee
• Check government references
• Avoid overlay-only solutions
• Get fixed pricing
• Ensure knowledge transfer
---
Hybrid Approach (Recommended):
1. Use DIY for: Quick wins, ongoing content, basic monitoring 2. Use Vendors for: Initial audit, complex fixes, compliance documentation 3. Start with: Our free scan to understand your needs 4. Then evaluate: Whether you need professional help
Explore solutions and options or get your baseline scan to make an informed decision. Check your compliance deadline to understand your timeline.
Frequently Asked Questions
Do overlays fix compliance?
No. Accessibility overlays (widgets that claim to make your site compliant with one line of code) do not achieve full WCAG 2.1 AA compliance. They can help with some issues but often create new problems. Many organizations using overlays have still been sued. The DOJ has been clear that automated solutions alone are insufficient. You need to fix the underlying code.
Are PDFs in scope?
Yes. PDFs provided to the public must be accessible. This means they need proper tags, reading order, alternative text for images, and fillable forms where applicable. Scanned PDFs (image-only) are never compliant. You'll need to either recreate PDFs accessibly or provide HTML alternatives. Archive PDFs before the rule *may* have limited exceptions.
How do we test mobile apps?
Mobile apps must be tested with platform assistive technology: VoiceOver for iOS and TalkBack for Android. Test for: navigation with screen readers, gesture alternatives for all actions, proper labeling of all controls, adequate touch target sizes (per platform guidance), and orientation support. Both automated tools and manual testing with actual devices are necessary.
What if we can't meet the deadline?
There are no extensions or waivers for the deadline. However, demonstrating good faith efforts can reduce liability: document all remediation efforts, fix the most critical barriers first, provide alternative access methods, respond promptly to complaints, and show continuous improvement. Courts consider effort and progress, but the deadline is firm.
Do internal employee portals need to comply?
Internal employee-only systems fall under Title I (employment) rather than Title II (public services). However, they still need to be accessible for employees with disabilities as a reasonable accommodation. The technical standards are similar, but the legal framework and deadlines differ.
What about third-party content like YouTube videos?
You're responsible for ensuring third-party content you embed or link to is accessible if it's essential for accessing your services. For YouTube videos: use only captioned videos, provide transcripts, or create accessible alternatives. You can't just blame the third party if someone can't access your services.
How much does compliance typically cost?
Costs vary widely: Simple sites (under 50 pages): $5,000-$20,000. Medium complexity (50-200 pages): $20,000-$75,000. Complex sites/applications: $75,000-$250,000+. Building accessibility in from the start costs 0-3% more. Retrofitting costs 30-100% of the original development cost. Lawsuits average $90,000-$150,000 in settlements alone.
Can we just provide a separate accessible version?
No. Separate but equal doesn't work for digital accessibility. Your main website must be accessible. Alternative versions are rarely maintained equally, often lack features, and courts have repeatedly rejected this approach. The only exception is providing an accessible alternative format for specific documents while working to make the originals accessible.
What if our vendor says they're compliant?
Trust but verify. Request their VPAT (Voluntary Product Accessibility Template), test their demo with assistive technology, check references from other government clients, and include indemnification clauses in contracts. Remember: you remain liable even if your vendor claimed compliance. Many lawsuits involve government entities whose vendors assured them of compliance.
How do we maintain compliance after fixing issues?
Accessibility isn't one-and-done. Establish ongoing processes: train all content creators, test new features before launch, conduct quarterly audits, monitor with automated tools (like our scanner), respond to user feedback quickly, and update your accessibility statement regularly. Budget 10-15% of your web maintenance for ongoing accessibility.
Start Your Compliance Journey
Every day you wait makes compliance harder and more expensive. Get your baseline assessment now and receive a prioritized remediation roadmap.
Get Your Free Accessibility ScanResources and Next Steps
• Instant Accessibility Scanner - Get your baseline score
• Compliance Deadline Tracker - Understand your timeline
• WCAG 2.1 Explained - Technical details made simple
• Complete Implementation Guide - Step-by-step instructions
• State-Specific Requirements - Your local obligations
• Solutions & Services - Professional help options
Immediate Action Items:
1. Today: Run a scan to know where you stand 2. This Week: Share this guide with stakeholders 3. This Month: Allocate budget and resources 4. Next Month: Begin remediation 5. Ongoing: Monitor and maintain compliance
Remember: This isn't just about avoiding lawsuits—it's about serving all your citizens equally. 1 in 4 Americans has a disability. They deserve equal access to government services.
The deadline is approaching. The requirements are clear. The tools are available. The only question is: will you be ready?
ADA Title II web accessibility isn't optional—it's federal law with specific deadlines and requirements. This guide has broken down exactly what you need to do, when you need to do it, and how to get it done. Whether you DIY or hire vendors, the key is starting now. Use our free scanner to understand your current state, then follow the roadmap to achieve compliance. The April 2026 deadline won't wait. Neither should you.