When Good Faith Isn't Enough: Operational Capacity as the Missing Variable

David's analysis in The Evidentiary Gap Runs Both Directions makes a structurally sound argument: the feedback loops connecting accessibility failures to institutional decision-making are broken in both directions, not just the direction that disadvantages complainants. That framing is useful for practitioners because it moves the conversation past a simple villain-and-victim narrative toward something more diagnostically accurate.

But accurate diagnosis doesn't automatically generate treatment capacity. The evidentiary gap David describes — where covered entities genuinely don't know what they don't know — is real. What the analysis underweights is that many covered entities who do acquire better information still lack the operational infrastructure to act on it systematically. The problem isn't only epistemic. It's structural.

The Capacity Floor Problem in ADA Compliance

Consider what it actually takes to close the feedback loop David describes. A transit agency that wants to measure navigation failures among limited-English riders needs, at minimum: multilingual outreach capacity, staff who can analyze disaggregated ridership data, a complaint intake process that doesn't require English fluency, and a mechanism for routing that information to decision-makers who control route planning. Most mid-sized transit agencies don't have all four of those things simultaneously. Many don't have any of them in functional form.

The ADA National Network (opens in new window), which coordinates technical assistance across ten regional centers, has documented this capacity gap extensively. Their training requests from covered entities skew heavily toward compliance basics — what the law requires — rather than toward sophisticated feedback measurement systems. That's not because covered entities are strategically avoiding accountability. It's because they're operating at or below the capacity floor required to implement even foundational compliance structures.

Section 508 of the Rehabilitation Act (opens in new window) provides a useful parallel. Federal agencies have had mandatory digital accessibility obligations since 1998. The Government Accountability Office has found repeatedly (opens in new window) that agencies struggle to implement consistent Section 508 compliance not primarily because they lack information about their failures, but because they lack dedicated staff, clear ownership of remediation workflows, and procurement processes that screen for accessibility before purchase rather than after deployment. Better feedback mechanisms wouldn't have solved that problem. Operational restructuring would.

What Community-Defined Accessibility Metrics Actually Require

The original analysis in The Evidentiary Gap Runs Both Directions gestures toward community-defined metrics as part of the solution architecture. That's directionally correct, and it aligns with what accessibility advocates have argued for years — that harm definitions constructed without affected communities will systematically undercount certain categories of failure.

But community-defined metrics are operationally expensive to implement well. They require sustained engagement infrastructure: community liaisons, translation capacity, accessible meeting formats, feedback channels that don't require digital fluency, and staff time to synthesize qualitative input into actionable data. The Pacific ADA Center (opens in new window) has published guidance on community engagement for covered entities, and the resource requirements are substantial even for relatively small programs.

This creates a distributional problem worth naming directly. Larger covered entities — major urban transit systems, well-resourced school districts, federal agencies — have more capacity to implement community-defined metrics and still face significant operational challenges. Smaller covered entities — rural transit providers, small municipalities, community colleges operating on thin margins — are being asked to close a feedback loop that requires infrastructure they cannot realistically build without targeted technical assistance and, in many cases, direct funding.

The DOJ's ADA guidance (opens in new window) establishes legal obligations without differentiating by organizational capacity. That's legally appropriate — civil rights obligations don't scale down for resource-constrained entities. But it means the compliance gap is widest precisely where operational capacity is lowest, and no amount of improved feedback mechanisms changes that arithmetic.

Complaint Processing as an Operational Capacity Indicator

There's a diagnostic angle here that practitioners often miss. The complaint processing dysfunction that Keisha's original analysis identified — and that David's response correctly complicates — is itself a signal about operational capacity, not just about institutional intent or information quality.

Agencies that process complaints slowly, inconsistently, or in ways that systematically disadvantage certain complainants are usually doing so because complaint processing isn't resourced as a core operational function. It's handled by staff with competing responsibilities, using intake systems that weren't designed for the volume or type of complaints they receive, with escalation pathways that aren't clearly defined. The Northeast ADA Center (opens in new window) has documented how complaint processing delays correlate with organizational characteristics that are fundamentally about capacity rather than commitment.

This matters for how we think about enforcement strategy. If complaint processing dysfunction reflects operational capacity problems, then enforcement approaches that add compliance pressure without adding capacity may produce worse outcomes — more complaints filed, less institutional ability to respond meaningfully, and communities experiencing the same barriers while agencies are technically in enforcement proceedings.

A Different Intervention Logic for Accessibility Enforcement

The CORS framework that informs analysis on this site treats Operational Capacity as a distinct variable — not reducible to intent, information, or legal obligation. That analytical separation is doing real work here.

The intervention logic that follows from David's evidentiary analysis is: improve information flows, and covered entities will make better decisions. That's partially correct. But the intervention logic that follows from an operational capacity analysis is different: build the infrastructure that makes better decisions executable, and information improvement becomes actionable rather than merely illuminating.

Those aren't mutually exclusive, but they point toward different resource allocations and different technical assistance priorities. Regional ADA centers, DOJ technical assistance programs, and state-level disability rights infrastructure all have choices to make about where to concentrate limited capacity-building resources. Framing the problem primarily as an evidentiary one may systematically underinvest in the operational scaffolding that determines whether better evidence actually changes outcomes for the people those systems are supposed to serve.

The more complete picture for practitioners: yes, fix the feedback loops, and yes, center community-defined metrics. But do that work inside an honest accounting of what it takes to act on that information — and where the capacity to act is structurally absent, name that as its own problem requiring its own solutions. Accurate diagnosis is necessary. It isn't sufficient.