Capacity Isn't the Defense — But It Is the Data

Patricia's legal analysis of the capacity argument is technically correct. Resource limitations have never functioned as a general defense under Title II or Section 504, and organizations that treat them as such are, as her recent analysis argues, taking on real legal exposure. But there's a distinction worth drawing out here — one that matters especially for the communities bearing the cost of these failures.

Capacity isn't a defense. It's a diagnostic. Conflating those two functions causes us to miss what the capacity variable is actually telling us about where the accessibility feedback gap is deepest, who it's harming most, and what kinds of interventions have any realistic chance of closing it.

What the Legal Framework Doesn't Capture About Affected Communities

The Department of Justice's Title II regulations (opens in new window) establish obligations that don't scale with organizational size — Patricia is right about that. But legal obligation and implementation reality operate on different timelines, and the communities most affected by under-resourced covered entities can't wait for enforcement cycles to run their course.

Consider who is disproportionately served by the smaller entities at the center of this debate: rural transit authorities, county health departments, regional housing agencies. According to the U.S. Census Bureau's American Community Survey (opens in new window), disability prevalence is meaningfully higher in rural counties than in urban ones — often by 4 to 6 percentage points. The entities with the least capacity to build accessible feedback infrastructure are frequently serving the populations with the highest rates of disability. That's not a coincidence. It's a structural pattern, and it deserves analysis on its own terms.

This is where community input as an analytical lens — the approach we use across our coverage here — changes the frame. When we center the experience of the person trying to navigate a county health department's complaint process using a screen reader, or trying to submit accessibility feedback to a rural transit authority that has no designated ADA coordinator, the capacity argument stops being a policy debate and becomes a harm-mapping exercise.

The Accessibility Enforcement Gap Isn't Uniform

Patricia's piece rightly notes that undue burden is a narrow, fact-specific defense — not a blanket exemption. But the enforcement infrastructure that would apply that standard is itself unevenly distributed. The ADA National Network (opens in new window), which operates through ten regional ADA Centers including the Great Lakes ADA Center (opens in new window) and the Southeast ADA Center (opens in new window), provides technical assistance that can help smaller entities understand their obligations. But technical assistance and enforcement are different levers, and the communities most harmed by the accessibility feedback gap are often the least equipped to trigger either one.

Section 504 of the Rehabilitation Act (opens in new window) applies to any entity receiving federal financial assistance — which includes most of the rural and regional agencies under discussion. That coverage is broad. The complaint mechanisms available to individuals when those agencies fail, however, require a level of systems literacy and persistence that itself functions as a barrier. As explored previously in this publication's coverage of the enforcement gap, the feedback loop between community members and covered entities is broken at multiple points — not just the legal compliance layer.

Using Capacity as a Title II Risk-Stratification Tool

Here's the reframe worth making: rather than treating capacity as either a defense (legally invalid) or an irrelevant variable (analytically blind), we should be treating it as a risk-stratification tool — a way of identifying which covered entities are most likely to have compliance failures, and which communities are therefore most exposed.

The Web Content Accessibility Guidelines (WCAG) (opens in new window) framework doesn't adjust its technical standards based on organizational size. But implementation support, technical assistance prioritization, and proactive outreach from enforcement agencies absolutely can and should account for where failures are most probable. The Section 508 program at GSA (opens in new window) has moved in this direction for federal agencies, providing tiered guidance and resources that acknowledge implementation complexity without relaxing legal standards.

That's the model worth scaling. Not "smaller entities get a pass" — but "smaller entities serving high-disability-prevalence populations get prioritized technical assistance before they're in a complaint posture."

This distinction matters from a community input perspective. The people filing accessibility complaints with under-resourced county agencies aren't primarily interested in enforcement outcomes — they're interested in getting accessible services. Enforcement that results in a finding of violation, without the technical capacity to remediate, doesn't close the feedback gap. It documents it.

Where Patricia's Framework and This One Converge

None of this is an argument against the legal analysis in Patricia's piece. Organizations treating capacity as a legal shield need to understand that it isn't one. The undue burden standard is narrow. The effective communications requirement doesn't scale down. Those are facts with real consequences.

But legal accuracy and policy utility are different things. The capacity variable, properly understood, tells us which covered entities are most likely to be out of compliance, which communities are most likely to be absorbing the cost of that non-compliance, and where proactive intervention — technical assistance, shared infrastructure, regional coordination — would do the most good before enforcement becomes necessary.

Centering community input means asking not just "what does the law require?" but "who is currently going without, and what would actually change that?" The ADA National Network's resource library (opens in new window) and the DOJ's ADA information line (opens in new window) exist precisely because legal obligation alone doesn't produce accessible services. Capacity, read correctly, is the map that shows where the gap between obligation and reality is widest — and where the communities waiting on the other side of that gap need us to look.

For practitioners, the immediate implication is concrete: if your organization provides technical assistance, advocates for covered entities, or advises on ADA compliance strategy, capacity data isn't a mitigating factor to set aside — it's a triage tool. Use it to find the entities most likely to fail the people who depend on them most.