Capacity Without Community: Who Defines 'Ready' in Accessibility Reform?

In their recent analysis of infrastructure arguments and justice delays, Jamie makes a sharp case that capacity-building and accountability are parallel obligations, not sequential ones. The historical record on Title VI and Section 508 implementation supports that reading. But there's a constituency largely absent from that framing — disabled people, limited English proficient individuals, and community advocates who have been submitting complaints into systems that weren't designed to hear them in the first place.

The capacity trap is real. The accountability gap is real. What the debate between operational realism and enforcement rigor tends to sidestep is a more uncomfortable question: who gets to define organizational readiness, and why have affected communities been so systematically excluded from that determination?

The Readiness Definition Problem

When federal agencies and covered entities assess their capacity to handle accessibility complaints, they typically measure inputs — staffing levels, technical systems, processing timelines, budget allocations. These are the metrics that appear in compliance audits and organizational self-assessments. They're also metrics that organizations control entirely.

The Department of Justice's complaint resolution process (opens in new window) gives complainants a role in initiating enforcement, but virtually no structural role in evaluating whether an organization's remediation plan is adequate. A school district can report that it has hired a language access coordinator and updated its translation vendor contracts. Whether those changes actually reach the Somali-speaking parent who couldn't access her child's IEP meeting — that feedback loop is rarely built into compliance frameworks.

This isn't a peripheral concern. Research from the National Council on Disability (opens in new window) has repeatedly documented the gap between formal accommodation infrastructure and lived accessibility experience. Organizations can be technically compliant — staffed, documented, audited — while remaining functionally inaccessible to the communities they serve. The metrics don't capture what the community experiences.

Community Input as Infrastructure, Not Afterthought

Our editorial approach at this publication treats community input as a structural element of accessibility analysis, not a soft supplement to legal and technical frameworks. That lens produces a different reading of the capacity debate.

If we center the perspective of someone who has filed an accessibility complaint — a deaf patient navigating a hospital system without consistent interpreter access, a Spanish-speaking tenant trying to understand a lease modification notice — the capacity question looks different. From that position, the organization's internal readiness assessment is largely invisible. What's visible is whether the complaint produced a response, whether the response addressed the actual barrier, and whether the barrier recurred.

The WCAG 2.1 guidelines (opens in new window) that govern digital accessibility were developed through a multi-stakeholder process that included disability community input at the technical level. The Section508.gov framework (opens in new window) builds on that foundation. But complaint processing systems — the human infrastructure that handles failures in technical accessibility — have no equivalent community co-design requirement. Organizations build those systems largely for themselves, optimized for compliance documentation rather than complainant experience.

As explored previously in the capacity trap analysis, Section 508 procurement guidance eventually required accessibility review to be built into acquisition processes as a current requirement rather than a future goal. That's a meaningful precedent. But procurement review is still an internal organizational process. It doesn't require organizations to ask the people who use their systems whether those systems actually work.

What Meaningful Community Input Would Require

The Great Lakes ADA Center (opens in new window) and similar regional technical assistance providers have documented that organizations often seek guidance on compliance processes without meaningfully engaging the disability communities in their service areas. Technical assistance tends to flow toward organizational capacity — how to write a transition plan, how to structure a grievance procedure — rather than toward community accountability mechanisms.

Building community input into accessibility infrastructure would require several structural shifts that go beyond what current enforcement frameworks mandate:

Complaint outcome transparency. Organizations that receive and resolve accessibility complaints under Title VI (opens in new window) or Section 504 rarely publish aggregate data on complaint volumes, resolution timelines, or outcome categories. Complainants typically receive individual responses with no visibility into systemic patterns. Publishing that data — even in anonymized form — would allow community advocates to identify whether capacity investments are producing actual results.

Participatory remediation planning. When the DOJ's Civil Rights Division negotiates settlement agreements with covered entities, community members are rarely at the table. The DOJ's ADA information resources (opens in new window) outline rights and processes, but the negotiation of specific remediation timelines and benchmarks happens between enforcement staff and organizational counsel. Structured community input into those negotiations would change what gets prioritized.

Feedback loop requirements. A complainant who reports that a hospital's interpreter service failed during an emergency has no formal mechanism to report whether the hospital's remediation actually prevented future failures. Building mandatory follow-up contact into complaint resolution — asking complainants whether the stated fix worked — would generate the community-sourced data that compliance audits currently lack.

The Risk of Capacity-Centered Reform

From a community perspective, the risk of the capacity debate — even when it correctly rejects the deferral strategy Jamie identifies — is that it remains fundamentally institution-centered. We argue about whether organizations are building capacity fast enough, whether enforcement timelines are appropriately urgent, whether technical assistance resources are adequate. These are real questions with real stakes.

But they're questions about organizational systems, answered by organizational actors, evaluated by enforcement agencies. The people filing complaints are positioned as inputs to that system rather than as stakeholders in its design.

Our analytical framework holds that accessibility reform without community accountability is structurally incomplete — not because community input is a nice supplement to legal compliance, but because affected communities hold information about accessibility failures that organizational self-assessment cannot generate. A hospital can audit its interpreter scheduling system. Only patients can report whether interpreters were actually present when needed, whether they were qualified, whether the interaction was private.

Building on this framework for understanding capacity arguments, the next analytical step isn't just demanding faster capacity-building — it's asking who gets to verify that capacity is real. Until affected communities have structural roles in that verification, organizational readiness will remain a self-reported metric, and the capacity trap will keep closing around the people it was supposed to protect.

The enforcement frameworks exist. The technical standards exist. What's missing is the accountability loop that runs back through the communities bearing the cost of every delayed response.