ADA Title II: A Compliance Roadmap for Housing Authorities

If you work at a housing authority and your website hasn’t been tested for accessibility, you’re not alone. Most haven’t. But a federal deadline is approaching fast, and the consequences of inaction are serious: lawsuits, loss of HUD funding, and residents who can’t access the services they need.
In April 2024, the Department of Justice finalized a rule requiring all state and local government websites to meet a specific accessibility standard called WCAG 2.1 Level AA. Housing authorities are covered. The deadlines are April 2026 for larger entities and April 2027 for smaller ones. There are no extensions.
This guide breaks down exactly what the rule requires, why housing authorities are uniquely affected, and what steps you can take right now to get compliant.
What You Need to Know in 60 Seconds
50
WCAG Criteria Required
Apr 2026
Deadline (50K+ Population)
$115K+
First Violation Penalty
|
The Rule |
The DOJ now requires all state and local government websites and mobile apps to conform to WCAG 2.1 Level AA. |
|
|
Who It Covers |
Every housing authority in the country, whether you operate public housing, administer Housing Choice Vouchers, or both. |
|
|
Deadlines |
|
|
|
What’s at Stake |
Private lawsuits (no administrative complaint required first), civil penalties up to $115,231, potential loss of HUD funding, and mandatory remediation. |
|
|
What’s Covered |
Main website, tenant portals, online applications, rent payment systems, PDFs, videos, and third-party tools you provide to residents. |
|
|
Bottom Line |
|
Your Compliance Checklist
Use this as your starting point. Each item connects to a deeper explanation later in this guide.
Understand Your Deadline
- Determine whether your housing authority serves a population of 50,000+ (April 2026) or under 50,000 / is a special district (April 2027)
- Confirm your entity’s legal classification: instrumentality of a city/county vs. independent special district
- Brief your executive director, board, and legal counsel on the requirement
Assess Where You Stand
- Complete a digital asset inventory: every website, portal, app, PDF library, and third-party tool
- Run an automated scan using tools like Insi, WAVE, or axe DevTools for a baseline error count
- Identify highest-risk digital assets: online applications, payment portals, maintenance request systems
- Review third-party vendor contracts for accessibility language and VPAT documentation
Build Your Plan
- Designate an accessibility coordinator or point person
- Set a budget for audit and remediation (typical range: $15,000–$50,000+ depending on complexity)
- Engage a qualified accessibility partner for a comprehensive audit (automated + manual + assistive technology testing)
- Create a prioritized remediation plan starting with resident-facing critical services
- Establish an accessibility policy and publish a public accessibility statement with feedback mechanism
Execute and Maintain
- Remediate critical-path services first: housing applications, rent payment, maintenance requests, waitlist
- Address the most common errors: low contrast text, missing alt text, unlabeled forms, empty links/buttons
- Remediate high-use PDFs: lease agreements, applications, policy documents, annual plans
- Require WCAG 2.1 AA conformance in all new vendor contracts and procurement
- Train content creators, web staff, and communications teams on accessibility basics
- Set up ongoing monitoring: monthly automated scans (Insi provides continuous WordPress monitoring), quarterly manual checks, annual full audits
Common Mistakes to Avoid
Do not purchase an accessibility overlay widget (accessiBe, UserWay, etc.) and assume you’re compliant. The FTC fined accessiBe $1 million for false advertising. 25% of accessibility lawsuits in 2024 targeted sites using overlays.
Do not assume your website vendor has handled this. Housing authorities remain legally responsible regardless of who built or hosts the site.
Do not wait for a complaint or lawsuit to start. There is no grace period after the deadline.
In This Guide
- The DOJ’s 2024 rule — what it says, how the deadlines work, and what’s covered
- Why housing authorities face unique obligations — ADA Title II, Section 504, and Fair Housing Act
- Enforcement and legal risk — who’s getting sued, what it costs, and why
- Common barriers — the most frequent failures and why overlays don’t work
- A realistic remediation roadmap — phased approach with timelines and costs
- The mission case — why this matters beyond legal compliance
- Resources — free tools, official guidance, and next steps
The DOJ’s 2024 Final Rule: Clear Standards, Hard Deadlines
On April 24, 2024, the Department of Justice published its landmark final rule (89 FR 31337) adding Subpart H to 28 CFR Part 35. It requires all state and local government entities to make their web content and mobile applications conform to WCAG 2.1 Level A and Level AA — a total of 50 success criteria. The rule took effect June 24, 2024, and represents the first time the DOJ has adopted a specific, enforceable technical standard for digital accessibility under the ADA.
Which Deadline Applies to Your Housing Authority?
|
Entity Type |
Deadline |
How to Determine |
|---|---|---|
|
Instrumentality of a city/county with 50,000+ population |
April 24, 2026 |
Use parent jurisdiction’s Census population |
|
Instrumentality of a city/county with under 50,000 population |
April 26, 2027 |
Use parent jurisdiction’s Census population |
|
Independent special district government (any size) |
April 26, 2027 |
Census Bureau does not calculate populations for special districts |
What the Rule Covers
The rule’s scope is broad. It covers all websites, mobile apps, online forms, PDFs, videos, social media posts (after the compliance date), and third-party tools provided through contractual arrangements — including tenant portals and payment systems operated by private vendors.
Housing authorities cannot contract away their ADA responsibilities.
If a private company runs the rent payment portal, the housing authority remains legally responsible for its accessibility. All third-party tools provided to residents must meet WCAG 2.1 AA.
Digital Assets Within Scope
|
Digital Asset |
Examples |
Risk Level |
|---|---|---|
|
Main public website |
Homepage, about pages, contact info, property listings |
High |
|
Online applications |
Housing applications, waitlist registration, voucher applications |
Critical |
|
Tenant/resident portals |
Rent payment, maintenance requests, income recertification |
Critical |
|
Document libraries |
Lease agreements, policy notices, annual plans, board minutes |
High |
|
Emergency communications |
Weather alerts, building notices, COVID updates |
Critical |
|
Third-party integrations |
Payment processors (Yardi, RealPage), chat widgets, maps |
High |
|
Multimedia content |
Videos, virtual tours, informational recordings |
Medium |
|
Social media (post-deadline) |
Posts made after compliance date on official accounts |
Medium |
Five narrow exceptions exist: archived web content meeting strict criteria, preexisting electronic documents posted before the compliance date (but not documents currently used to access services), content posted by third parties (though the platform itself must be accessible), individualized password-protected documents, and social media posts made before the compliance date. Even when an exception applies, the entity must still provide content in an accessible format upon individual request.
Housing Authorities Sit at the Intersection of Three Federal Laws
Housing authorities occupy a unique legal position: they are simultaneously covered by ADA Title II (as government entities), Section 504 of the Rehabilitation Act (as recipients of HUD funding), and the Fair Housing Act (as housing providers). This creates overlapping obligations that make digital accessibility non-negotiable.
|
|
ADA Title II |
Section 504 |
Fair Housing Act |
|---|---|---|---|
|
Applies Because |
Housing authorities are state/local government entities |
Housing authorities receive HUD financial assistance |
Housing authorities are housing providers |
|
Digital Standard |
WCAG 2.1 AA (explicit since 2024) |
Effective communication / program access (no specific WCAG standard yet) |
No explicit digital requirement, but inaccessible applications may violate 42 U.S.C. 3604(f)(1) |
|
Enforcement |
DOJ + private lawsuits (no exhaustion required) |
HUD FHEO + potential funding loss |
HUD complaints + private lawsuits |
|
Strength for Digital |
Strongest |
Strong |
Moderate |
PHAs must comply with whichever law provides the greatest protection. The ADA Title II rule now provides the most specific and enforceable digital accessibility standard, while Section 504 creates an independent enforcement pathway through HUD that could result in the loss of federal funding.
Enforcement Is Real: The Legal Landscape
The most immediate risk comes not from federal agencies but from private litigation.
4,187
ADA Digital Lawsuits in 2024
25,000+
Filed Since 2018
48%
Were Repeat Defendants
Under ADA Title II, individuals can sue directly in federal court without first filing any administrative complaint. Digital accessibility lawsuits surged 20% in the first half of 2025. Legal experts consistently identify private enforcement as the primary mechanism driving compliance, especially given reduced DOJ staffing.
Consequences of Non-Compliance
|
Consequence |
Details |
|---|---|
|
Civil penalties (first) |
Up to $115,231 per violation |
|
Civil penalties (subsequent) |
Up to $230,464 per violation |
|
Loss of federal funding |
Enforceable by HUD FHEO under Section 504. Could affect public housing funds, HCV, CDBG, HOME. |
|
Compensatory damages |
Available under Title II and Section 504 |
|
Injunctive relief |
Mandatory remediation, multi-year monitoring, independent audits, staff training |
|
Attorney’s fees |
Shift to prevailing plaintiffs, adding significant cost beyond settlements |
The current administration has not rescinded or delayed the rule. In October 2025, DOJ announced it would re-examine ADA regulations, but the existing deadlines remain in force. Reduced federal enforcement capacity makes private lawsuits more likely, not less. No grace period exists after the deadline.
Common Barriers on Housing Authority Websites
The WebAIM Million 2025 analysis evaluated one million home pages and found that 94.8% had detectable WCAG failures, with an average of 51 errors per page. Six error types account for 96% of all detected issues:
|
Most Common WCAG Failures |
(% of Pages Affected) |
|---|---|
|
Low contrast text |
79.1% |
|
Missing alt text |
55.5% |
|
Missing form labels |
48.2% |
|
Empty links |
45.4% |
|
Empty buttons |
29.6% |
|
Missing doc language |
15.8% |
Source: WebAIM Million 2025 Analysis
Housing-Specific Findings
The Equal Rights Center’s landmark study tested 25 housing provider websites using matched blind and sighted testers:
84%
Had Desktop Barriers
81%
Blocked Applications
13/16
Online Apps Inaccessible
The Three Biggest Remediation Challenges
|
Barrier |
Why It Matters for Housing |
Fix Difficulty |
|---|---|---|
|
Inaccessible PDFs |
Lease agreements, applications, policy documents — often image-only scans invisible to screen readers |
High ($4–$7+/page) |
|
Inaccessible forms |
Forces disabled residents to disclose sensitive financial and disability information to helpers |
Medium–High |
|
Third-party tools |
Payment processors (Yardi, RealPage), chat widgets. Outside your control but within your legal responsibility. |
High (requires vendor cooperation) |
Overlays Are Not a Compliance Solution
Accessibility overlay widgets (accessiBe, UserWay, etc.) inject JavaScript on top of inaccessible HTML without fixing underlying code. The FTC fined accessiBe $1 million in 2025. 25% of lawsuits targeted overlay users. Only 2.4% of disabled users found them effective. Over 400 accessibility experts have publicly condemned them.
What Actually Works: Tools That Fix the Code
Effective accessibility tools identify issues at the source and guide your team through fixing them in actual code and content. Insi, for example, uses an advanced cloud-based virtual browser engine that simulates real user experiences, catching problems that code-only scanners miss. It integrates directly into WordPress so your team can scan pages, see exactly where issues exist with visual screenshots, and follow step-by-step remediation guidance without leaving the dashboard. The difference between an overlay and a real accessibility tool is simple: overlays hide problems from scanners while real tools help you eliminate them.
A Realistic Remediation Roadmap
A typical single-website remediation takes 4 to 8 months. Housing authorities with multiple digital systems should plan for 8+ months minimum.
|
Phase |
Activity |
Timeline |
Key Actions |
|---|---|---|---|
|
1 |
Foundation |
Weeks 1–4 |
Form accessibility committee, inventory all digital assets, study DOJ guidance, set budget ($15K–$50K+) |
|
2 |
Assessment |
Weeks 4–10 |
Comprehensive audit: automated scanning (Insi, WAVE, axe DevTools) + manual review of all 50 WCAG criteria + assistive technology testing. Automated tools catch only 25–30% of issues. |
|
3 |
Remediation |
Weeks 8–28 |
Fix critical-path services first. Address top 6 error types (96% of issues). PDF remediation. Third-party vendor engagement. |
|
4 |
Training & Policy |
Week 4+ |
Train content creators and procurement staff. Publish accessibility statement. Require WCAG 2.1 AA in all vendor contracts. |
|
5 |
Verification |
Weeks 26–32 |
Re-audit to verify fixes, secondary remediation, document conformance status. |
|
6 |
Maintenance |
Permanent |
Monthly automated monitoring (Insi provides continuous WordPress scanning), quarterly manual checks, annual full audits. Budget $5K–$15K/year. |
Typical Budget Ranges
|
Component |
Estimated Cost Range |
|---|---|
|
Comprehensive accessibility audit |
$5,000 – $15,000 |
|
Website remediation (single site, moderate complexity) |
$10,000 – $35,000 |
|
PDF remediation (per page, at scale) |
$4 – $7+ per page |
|
Staff training (initial) |
$2,000 – $5,000 |
|
Annual ongoing maintenance and monitoring |
$5,000 – $15,000/year |
|
Typical Total (Year 1, single site) |
$15,000 – $50,000+ |
Why This Matters Beyond Legal Compliance
The populations housing authorities serve have dramatically higher disability rates than the general population.
52%+
PH Households: Disabled or Elderly Head
23%
Include a Disabled Member
1.8M
Disabled Households on HUD Assistance
|
Public Housing Resident Demographics |
(% of Households) |
|
Headed by elderly (62+) |
40% |
|
Include disabled member |
23% |
|
Below poverty line |
75% |
|
Seniors lacking computer |
70% |
|
Seniors lacking internet |
74% |
Sources: HUD 2024 Resident Characteristics Report, CLPHA, NCHPH
The average public housing household income is $18,284 per year. Research shows 71% of disabled users abandon websites they find difficult to use. For housing services, that abandonment means losing access to housing itself.
Less than 5% of U.S. housing is physically accessible to people with disabilities. Digital access to housing information and services is therefore even more critical as a pathway to the limited accessible housing that exists. Making digital services accessible is not a regulatory burden imposed from outside the mission. It is the mission.
Resources
Accessibility Testing Tools
|
Tool |
What It Does |
URL |
|---|---|---|
|
Insi |
WordPress accessibility scanner that simulates real user experiences to catch issues code-only tools miss. Free URL scan available. |
|
|
WAVE |
Browser-based tool that visually highlights accessibility errors on any page |
|
|
axe DevTools |
Browser extension for Chrome and Firefox, widely used by developers |
|
|
ANDI |
Free tool from the Social Security Administration for testing web content |
|
|
Colour Contrast Analyser |
Standalone tool for checking text contrast ratios |
|
|
NVDA Screen Reader |
Free, open-source screen reader for Windows for manual testing |
Official Guidance and Legal References
|
Resource |
URL |
|
DOJ Fact Sheet on Web Accessibility Rule |
|
|
DOJ First Steps Guide |
|
|
Regulation Text (28 CFR Part 35, Subpart H) |
|
|
WCAG 2.1 Quick Reference |
|
|
HUD Section 504 Regulations (24 CFR Part 8) |
Potential Funding Sources
|
Source |
Details |
|
Disabled Access Tax Credit |
IRS Section 44 — up to $5,000 annually for small entities’ accessibility costs |
|
Digital Equity Act Grants |
Federal competitive grant program supporting digital inclusion (ntia.gov) |
|
CDBG Allocations |
Existing Community Development Block Grant funds may cover digital accessibility improvements |
|
State AT Programs |
Check your state’s Assistive Technology program for potential resources |
