The Capacity Argument Has a Legal Blind Spot

Marcus makes a compelling case that organizational capacity — not institutional will — drives the accessibility feedback gap. But framing capacity as the primary constraint obscures a harder truth: resource limitations have never been a recognized legal defense under Title II or Section 504, and treating them as the dominant variable in compliance analysis carries real legal risk for the organizations this framing is meant to protect.

In their recent analysis, Marcus draws a meaningful distinction between large federal agencies with dedicated civil rights infrastructure and smaller covered entities — rural transit authorities, county health departments, regional housing agencies — operating on constrained budgets. That distinction is operationally real. Where I part ways is on the policy conclusion it's meant to support: that enforcement pressure on capacity-constrained organizations is not just insufficient but potentially counterproductive. That conclusion, however sympathetically framed, may be doing those organizations a disservice.

What Title II and Section 504 Actually Say About Capacity

The Americans with Disabilities Act (opens in new window) and Section 504 of the Rehabilitation Act do include a structural accommodation for resource-limited entities: the "undue burden" standard. But undue burden is a narrow, fact-specific defense applied to specific accommodation requests — not a general exemption from building accessible feedback infrastructure. The Department of Justice's Title II regulations (opens in new window) require covered entities to ensure that communications with people with disabilities are as effective as communications with others. That obligation doesn't scale down based on agency size in the way Marcus's capacity framing implies.

Similarly, Title VI of the Civil Rights Act (opens in new window) and Executive Order 13166 impose language access obligations on recipients of federal financial assistance regardless of organizational size. The DOJ's Language Access Guidance (opens in new window) makes clear that recipients must take reasonable steps to provide meaningful access — and while "reasonable" does account for resources, it does so within a framework that still requires affirmative action, not inaction pending capacity improvements.

For the smaller entities Marcus is most concerned about, this legal reality matters enormously. An organization that has internalized "we lack capacity" as the primary explanation for its compliance gaps may be systematically underinvesting in the legal risk analysis that should be driving its prioritization decisions.

The Risk Calculus Smaller Organizations Are Missing

Here's what fifteen years of watching compliance cycles has taught me: the organizations most likely to face enforcement action aren't always the most egregious violators. They're often the ones that failed to document their good-faith efforts, failed to establish any feedback mechanism at all, or — critically — failed to respond when complaints surfaced.

The ADA National Network (opens in new window) does valuable technical assistance work, and Marcus is right that its resources document staffing and expertise constraints as barriers. But that same technical assistance network consistently emphasizes that covered entities must demonstrate ongoing good-faith compliance efforts. "We didn't have the staff" is not a documented good-faith effort. It's an absence of one.

The DOJ's settlement agreements with transit agencies (opens in new window) and health departments over the past decade reveal a consistent pattern: the triggering complaint is rarely the first signal of a problem. It follows a period in which the organization had notice — through informal complaints, community feedback, or internal audits — and didn't act. Capacity constraints may explain why the initial infrastructure wasn't built. They don't explain why complaints went unaddressed once they arrived.

As explored previously, the feedback gap is partly a structural problem. But structure and legal obligation aren't the same thing, and conflating them in policy analysis can lead practitioners toward a false sense of legal cover that doesn't exist.

The Perverse Incentive in Capacity-First Framing

There's a subtler problem with leading with capacity as the explanatory variable: it creates a rhetorical framework that organizations can — and do — use to defer compliance work indefinitely. If the dominant narrative in accessibility policy circles is that resource-constrained organizations can't reasonably be expected to build feedback infrastructure without additional support, that narrative becomes available as a justification for inaction.

This isn't a hypothetical concern. Section 508 compliance data (opens in new window) from the federal government's own reporting mechanisms shows persistent gaps even in agencies with dedicated accessibility staff and explicit legal obligations. If capacity-rich entities struggle to maintain compliance, the argument that capacity-poor entities simply need more resources before they can be held accountable becomes a permanent deferral mechanism.

The more legally sound framing — and the one that actually serves smaller organizations better — is to acknowledge capacity constraints while insisting that those constraints require prioritization, not postponement. A rural transit authority with limited staff should be building a basic, documented feedback channel and responding to complaints it receives. That's achievable at minimal cost. What it requires is legal clarity about the obligation, not additional technical assistance about the aspiration.

Our editorial approach at this publication has consistently emphasized that accessibility analysis serves practitioners best when it doesn't soften legal obligations in the service of sympathetic narratives. The capacity argument is sympathetic. It's also, in its strongest form, legally imprecise in ways that can harm the organizations it's trying to help.

Enforcement and Capacity Support Aren't Mutually Exclusive

Building on this framework, the more productive policy synthesis isn't enforcement versus capacity — it's enforcement calibrated to documented good-faith effort, combined with technical assistance that's explicit about legal floor rather than aspirational ceiling.

The Great Lakes ADA Center (opens in new window) and its regional counterparts do exactly this in their best technical assistance work: they help organizations understand what the minimum legal obligation actually requires, then build toward more robust compliance. That sequencing matters. When technical assistance leads with capacity constraints rather than legal obligations, it inadvertently signals that the legal floor is negotiable. It isn't.

Smaller covered entities deserve realistic support. They also deserve honest legal analysis — including the analysis that tells them their capacity constraints, while real, don't reduce their legal exposure the way they might hope. That's the conversation the accessibility policy community needs to have more directly, even when it's uncomfortable.