The Compliance Clock Doesn't Pause for Capacity Planning

Keisha's framing in the capacity-as-diagnostic piece is genuinely useful for understanding structural patterns in accessibility failures. The distinction between capacity as defense versus capacity as data is real, and the demographic analysis connecting rural disability prevalence to under-resourced covered entities deserves serious attention. But there's a risk embedded in that analytical generosity — one that practitioners advising covered entities need to understand clearly before it becomes a liability.

The enforcement environment has shifted. What was once a compliance landscape characterized by extended technical assistance periods and negotiated voluntary resolution agreements is increasingly one where the Department of Justice (opens in new window) moves directly to findings and consent decrees. Covered entities that have been treating capacity constraints as a mitigating narrative — even a diagnostic one — are discovering that the legal framework has less patience for that framing than it once did.

What the 2024 Title II Rule Change Actually Signals

The DOJ's 2024 amendments to Title II regulations (opens in new window) establishing specific WCAG 2.1 AA standards for web and mobile accessibility weren't just a technical clarification. They were an enforcement signal. By codifying a specific technical standard with defined compliance timelines — 2026 for larger entities, 2027 for smaller ones — the rule effectively closed the interpretive space that capacity arguments had previously occupied.

Before those amendments, a covered entity could argue that its web accessibility approach was reasonable under the circumstances, and "circumstances" had some room to breathe. That room is now considerably smaller. The rule creates a binary: either your public-facing digital infrastructure meets WCAG 2.1 AA or it doesn't. Organizational capacity explains why you're not there yet. It doesn't change whether you're out of compliance.

This matters because the communities Keisha identifies — rural transit authorities, county health departments, regional housing agencies — are precisely the entities most likely to have relied on that interpretive breathing room. The 2027 deadline for smaller covered entities sounds generous until you map it against the procurement cycles, IT staffing realities, and budget approval processes that govern those organizations. Many of them are already behind a timeline they haven't fully internalized.

The Risk Calculus That Capacity Framing Obscures

From a risk management perspective, the capacity-as-diagnostic lens, however analytically sound, can function as a cognitive buffer that delays action. When leadership at a county health department hears that their accessibility gaps are "structural" and "diagnostic," the organizational response is often to treat the problem as systemic and therefore slow-moving. That's the wrong read of the legal exposure — and of what's at stake for the people those agencies serve.

Section 504 of the Rehabilitation Act (opens in new window) has always applied to federal funding recipients without a capacity carve-out, and the complaint mechanisms under both Section 504 and Title II are accessible to any individual who experiences a barrier. A single complainant with a documented accessibility failure can initiate a federal investigation regardless of whether the covered entity has three IT staff or three hundred. The ADA National Network's technical assistance resources (opens in new window) are explicit on this point: organizational size affects what remediation looks like, not whether the obligation exists.

As explored in the original analysis, the communities absorbing the cost of these failures are disproportionately rural and disabled. Those same community members hold federal complaint rights that don't require them to wait for structural reform. The gap between "this is a systemic problem" and "this is an active legal exposure" is where organizations get caught — and where people with disabilities continue to be denied access in the meantime.

Our editorial approach at this publication has consistently emphasized that understanding the legal framework isn't separate from understanding community impact — it's the mechanism through which community members can actually enforce their rights.

Where Capacity Data Should Actually Drive Action

If capacity data is genuinely diagnostic, the appropriate response is to use it diagnostically — meaning it should drive resource allocation decisions, not narrative construction for potential enforcement conversations.

The Great Lakes ADA Center (opens in new window) and other regional ADA Centers have documented that covered entities with the most significant compliance gaps are often those that have never conducted a formal self-evaluation or transition plan under Title II's existing requirements. That's not a capacity problem in the first instance — it's a prioritization problem. The self-evaluation requirement has existed since 1992. An organization that hasn't completed one isn't resource-constrained; it's non-compliant in a way that predates any current budget cycle.

This is where the risk framing becomes essential. Covered entities that use capacity data to identify their highest-exposure compliance gaps — and then sequence remediation around those gaps — are in a fundamentally different legal position than entities that use capacity constraints to explain why comprehensive compliance isn't currently achievable. The former is risk management. The latter is, as the original piece correctly notes, not a defense.

The Section 508 compliance framework (opens in new window) offers a useful parallel. Federal agencies that have successfully reduced their accessibility debt didn't do so by documenting why the debt existed. They did it by treating the highest-risk exposures as non-negotiable remediation priorities regardless of competing resource demands.

The Practitioner's Obligation

For accessibility practitioners and legal counsel advising covered entities, the analytical distinction between capacity-as-defense and capacity-as-data is worth preserving — but it needs a harder edge than the diagnostic framing alone provides. Capacity data should feed directly into a prioritized remediation roadmap with documented timelines, assigned ownership, and budget commitments. That documentation doesn't just serve the organization's compliance trajectory; it serves as evidence of good-faith effort in the event of a complaint or investigation.

The practical threshold is concrete: if your covered entity hasn't completed a self-evaluation, that's the first documented deliverable, with a deadline. If you have a self-evaluation but no transition plan, that's the second. If you have both but no budget line tied to the 2026 or 2027 WCAG 2.1 AA deadline, you have a plan without a commitment — and that distinction will matter if a complaint is filed.

The communities bearing the cost of these failures deserve both the structural analysis and the enforcement pressure. Those aren't competing priorities. The diagnostic lens tells us where the gaps are deepest and who is being excluded. The legal framework tells us that the clock on remediation is running regardless of whether the organization has caught up to it.

You can learn more about how our contributors approach the intersection of legal analysis and community impact on the about page, including how Keisha and I often work from complementary rather than conflicting frameworks — even when the emphasis differs significantly.