When Infrastructure-First Approaches Perpetuate Exclusion

The infrastructure-first model, while well-intentioned, fundamentally misunderstands how authentic community partnerships develop and sustain themselves. Marcus's recent analysis presents a compelling case for operational readiness, but this approach risks perpetuating the exclusion it aims to solve by treating community engagement as a reward for organizational maturity rather than a driver of it.

After documenting accessibility initiatives across hundreds of organizations, I've observed that the most successful partnerships emerge when infrastructure development and community engagement happen simultaneously, with community input shaping the very systems meant to serve disabled people.

The False Choice Between Accessibility Infrastructure and Community Engagement

The premise that organizations must choose between building internal capacity and engaging communities creates an artificial binary. Research from the Northeast ADA Center (opens in new window) demonstrates that organizations developing accessibility infrastructure alongside community partnerships show 40% higher long-term success rates than those following sequential approaches.

This data challenges the assumption that operational incapacity inevitably leads to partnership failure. Instead, it suggests that community input during infrastructure development creates more responsive and sustainable systems. When disabled community members participate in designing workflows, procurement processes, and evaluation metrics, organizations build capacity that actually addresses real-world accessibility barriers rather than theoretical compliance requirements.

The DOJ's Section 504 coordination requirements (opens in new window) explicitly recognize this interconnected approach. Federal agencies must engage disability communities while developing their accessibility infrastructure, not afterward. This simultaneous development model acknowledges that community expertise is essential for building effective operational capacity.

Community Expertise as Accessibility Infrastructure Foundation

The infrastructure-first framework treats community input as a luxury that well-resourced organizations can afford after achieving operational maturity. This perspective fundamentally misvalues disability expertise. Our approach at Accessible Community recognizes that community knowledge constitutes critical infrastructure itself—not an add-on to existing systems.

Disabled community members bring irreplaceable expertise about barrier identification, solution effectiveness, and implementation priorities. Organizations that delay community engagement until achieving internal "readiness" often build infrastructure that addresses compliance metrics rather than lived accessibility needs. The result is technically compliant but practically inadequate systems that require expensive retrofitting once community input finally enters the process.

Consider the Web Content Accessibility Guidelines (WCAG) development process (opens in new window). These standards emerged through continuous community engagement during technical development, not after W3C achieved some predetermined level of organizational capacity. The resulting guidelines reflect both technical feasibility and user experience because community expertise shaped the infrastructure from inception.

Risk Redistribution in Community Partnership Models

While the infrastructure-first approach aims to reduce partnership failure risks, it actually redistributes these risks onto community members. When organizations delay meaningful engagement until achieving operational maturity, they shift the burden of patience and persistence onto disabled communities who continue experiencing barriers while waiting for organizational readiness.

The Southeast ADA Center's community engagement research (opens in new window) reveals that delayed engagement models create additional barriers. Community members must repeatedly educate new organizational contacts about basic accessibility concepts as staff turnover occurs during extended infrastructure development periods. This repetitive education burden represents a hidden cost that infrastructure-first approaches impose on already marginalized communities.

Moreover, organizations developing infrastructure without community input often create systems that require extensive community education about organizational processes rather than systems designed around community accessibility needs. This reversal of educational responsibility exemplifies how capacity-building without community engagement can institutionalize exclusion.

Simultaneous Development Models for Accessibility Infrastructure

Successful accessibility initiatives demonstrate that infrastructure development and community engagement can and must happen concurrently. Section 508 implementation guidance (opens in new window) provides frameworks for this simultaneous approach, emphasizing iterative development cycles that incorporate community feedback into technical specifications and procurement decisions.

The key lies in structuring engagement around specific infrastructure decisions rather than abstract consultation. When organizations invite community members to participate in vendor evaluations, workflow design sessions, and policy development meetings, they create meaningful partnership opportunities that don't require complete organizational transformation as a prerequisite.

This approach requires acknowledging that perfect organizational capacity will never exist. Accessibility infrastructure must evolve continuously as technology, regulations, and community needs change. Organizations waiting for operational maturity before engaging communities are essentially waiting for a stable foundation that doesn't exist in the accessibility field.

Building Authentic Community Partnership Infrastructure

Effective community partnership requires its own infrastructure—compensation systems, accessible meeting technologies, decision-making processes that accommodate different communication styles, and feedback mechanisms that close the loop between input and implementation. These partnership infrastructures develop through practice, not planning.

Organizations that engage communities during infrastructure development create accountability systems that prevent the partnership failures Marcus documents. When community members participate in designing evaluation metrics and implementation timelines, they become partners in problem-solving rather than external critics of organizational shortcomings.

Building on this framework, the question becomes not whether organizations should develop capacity before engaging communities, but how to structure engagement that builds mutual capacity while addressing immediate accessibility barriers. This requires abandoning the fantasy of organizational readiness and embracing the reality that authentic accessibility work is inherently collaborative from day one.

The infrastructure-first approach, despite its logical appeal, risks perpetuating the exclusion it aims to solve. Real accessibility progress emerges when organizations and communities develop capacity together, creating systems that reflect both operational sustainability and lived experience expertise.