The Enforcement Gap Is a Design Problem, Not a Resource Problem

The two preceding analyses in this series — Patricia's legal framework and Keisha's diagnostic reframe — both operate from a shared assumption worth interrogating: that the primary variable explaining persistent Title II and Section 504 failures is organizational capacity, whether as defense or data point. That framing is analytically useful but strategically incomplete.

The more durable explanation isn't that covered entities lack resources. It's that the compliance architecture itself was designed in ways that make failure predictable, measurable, and — critically — tolerable to everyone except the people experiencing it.

Compliance Systems Produce What They're Designed to Produce

The ADA's Title II regulations (opens in new window) have been in effect since 1992. The Section 504 regulations (opens in new window) predate them by over a decade. If resource constraints were the primary driver of persistent non-compliance, we would expect compliance rates to improve as organizational capacity improves — and to deteriorate during genuine austerity periods. The evidence doesn't consistently support that pattern.

What we see instead, across enforcement cycles, is that compliance gaps cluster not just by organizational size but by the political and administrative salience of the affected population. Rural transit authorities serving high-disability-prevalence counties, as Keisha's analysis correctly identifies, are chronically under-resourced. But they're also chronically under-scrutinized. The Department of Justice's enforcement priorities (opens in new window) have historically concentrated on higher-visibility entities — large municipalities, major transit systems, state-level agencies — where enforcement actions generate broader precedent and media coverage.

That's not a criticism of DOJ resource allocation; it's a description of how enforcement systems operate under their own capacity constraints. But it means the communities absorbing the deepest compliance failures are also the least likely to generate the enforcement pressure that would compel change.

The Feedback Loop Problem Is Structural, Not Incidental

Accessibility compliance frameworks rely heavily on complaint-driven enforcement. The ADA National Network's guidance on filing complaints (opens in new window) walks through a process that places significant burden on the individual experiencing the barrier: documenting the issue, navigating agency jurisdictions, waiting through investigation timelines that routinely extend 18 to 24 months or longer.

For people with disabilities in rural or under-resourced communities — the same populations Keisha's analysis identifies as disproportionately affected — that complaint process carries compounded friction. Limited broadband access, fewer disability advocacy organizations per capita, and less familiarity with federal complaint mechanisms all suppress complaint rates in precisely the communities where barriers are most concentrated.

This is a design problem. A compliance system that generates its enforcement signals primarily through formal complaints will systematically undercount failures in communities with the least capacity to generate those signals. Capacity, in this reading, isn't just an organizational variable — it's a community-level variable that shapes what the enforcement system can even see.

The Great Lakes ADA Center (opens in new window) and its regional counterparts have documented this pattern in technical assistance contexts for years: the entities that most need compliance support are often the least likely to proactively seek it, and the communities most affected by failures are the least likely to formally report them. The data gap Keisha identifies isn't just about feedback infrastructure within covered entities. It runs through the entire compliance ecosystem.

Redesigning the Signal, Not Just the Response

From a strategic alignment perspective — which our editorial approach at this publication consistently applies to accessibility compliance questions — the policy question isn't only how covered entities should respond to capacity constraints. It's whether the compliance architecture is generating accurate signals about where failures are occurring and who is bearing the cost.

The Section 508 Standards (opens in new window) that govern federal digital accessibility offer a partial model: proactive requirements, periodic assessments, and agency-level reporting obligations that don't depend entirely on affected individuals initiating complaints. Title II's 2024 digital accessibility rule — the DOJ's web and mobile accessibility rule for state and local governments (opens in new window) — moves in a similar direction by establishing specific technical standards rather than relying solely on the general effective communication framework.

But rules without monitoring mechanisms still depend on complaint-driven enforcement at the margin. The strategic gap isn't regulatory text. It's the absence of systematic, proactive audit infrastructure for the covered entities least likely to self-report or attract formal complaints.

Some regional ADA Centers have piloted technical assistance models that function more like proactive outreach than reactive support — identifying high-risk entities by service population and organizational profile, rather than waiting for complaints to surface. That model, scaled and resourced appropriately, would begin to address the signal problem rather than just the response problem.

What This Means for Practitioners

For accessibility professionals and compliance officers working within covered entities, the practical implication is this: capacity data, as Keisha's framework argues, is genuinely diagnostic. But the diagnosis it surfaces is incomplete if it only looks inward at organizational resources. The communities your entity serves are also generating — or failing to generate — signals that shape your compliance risk profile in ways that formal complaint data won't capture.

Proactive community engagement, plain-language accessibility feedback mechanisms, and partnerships with local disability organizations aren't just good practice. They're the infrastructure that makes your compliance gaps visible before enforcement cycles do. Entities that build those channels aren't just managing legal risk; they're correcting for a structural blind spot in how the compliance system generates information.

The Pacific ADA Center's resources on effective communication (opens in new window) and the Northeast ADA Center's technical assistance materials (opens in new window) both emphasize community-facing accessibility planning as a core compliance function — not a supplementary one. That framing deserves wider adoption.

The capacity argument, in its diagnostic form, points toward real structural inequities. But the intervention those inequities call for isn't just better-resourced covered entities. It's a compliance architecture that doesn't require the most marginalized communities to do the most work to make their barriers visible.