Capacity Arguments Don't Resolve the Access Deficit

David's defense of operational metrics raises legitimate concerns about enforcement outpacing organizational capacity — but the argument, however carefully constructed, risks normalizing a compliance floor that leaves disabled people without the access the law actually promises.

In their recent analysis, the case is made that dismissing operational metrics produces its own access failures: organizations become legally exposed, under-resourced, and ultimately less capable of delivering access at all. That's a real tension. Enforcement without implementation pathways can produce paralysis rather than progress. But the analytical weight placed on organizational capacity deserves scrutiny from a different direction — specifically, from the perspective of the people who absorb the cost when capacity arguments win.

Who Pays When Capacity Arguments Succeed

Every time a compliance framework accommodates resource constraints, someone pays the price. That someone is almost never the organization citing capacity limitations. The ADA National Network (opens in new window) has documented consistently that the populations most affected by inaccessible digital services — people with disabilities who rely on government benefits portals, healthcare scheduling systems, and public transit interfaces — are also among the least positioned to seek alternative access routes. The capacity argument, whatever its analytical merit, distributes the burden of institutional limitation onto the people the law was designed to protect.

This isn't a rhetorical point. Section 508 of the Rehabilitation Act (opens in new window) and Title II of the ADA establish affirmative obligations precisely because Congress recognized that access wouldn't materialize through market incentives or organizational goodwill alone. The legal standard is access, not reasonable effort toward access. When operational metrics become the measure of compliance rather than actual user outcomes, the standard effectively shifts — regardless of what the statute says.

The DOJ's 2024 Title II final rule on web accessibility (opens in new window) reflects this orientation. The Department established specific WCAG 2.1 Level AA conformance requirements with defined compliance timelines precisely because outcome-neutral frameworks had produced decades of stagnation. The rule's preamble explicitly addresses the capacity argument: smaller entities receive extended timelines, not exemptions. The distinction is deliberate.

What "Sustainable Access" Actually Requires

David's framing around sustainable access is worth examining carefully. The argument holds that organizations under-resourced and legally exposed become less capable of delivering access to anyone. This is structurally true but strategically incomplete. Organizations have consistently demonstrated an ability to resource priorities when legal exposure is concrete and enforcement is credible. The accessibility field has ample evidence of this pattern — the wave of web accessibility litigation beginning around 2017 produced more organizational investment in accessibility programs than a decade of technical assistance had generated.

The Great Lakes ADA Center (opens in new window) and its regional counterparts have noted this dynamic in their training and technical assistance work: entities that treat accessibility as a compliance risk to be managed allocate resources differently than those that treat it as a legal obligation with teeth. Capacity isn't fixed. It responds to incentive structures, and enforcement credibility is among the most reliable of those structures.

As explored previously in this conversation, the measurement gap is real. But the question of which direction it cuts depends entirely on whose experience you center. For practitioners designing compliance programs, operational metrics provide useful benchmarks. For a screen reader user who cannot complete a benefits application, the gap between metric achievement and actual access is the entire problem.

The Strategic Alignment Problem

From a strategic alignment perspective, the capacity defense contains a structural flaw: it optimizes for organizational sustainability at the expense of mission alignment. Public entities exist to serve their communities. When capacity arguments successfully moderate enforcement expectations, they produce organizations that are operationally stable but mission-compromised — capable of sustaining themselves while failing the populations they're legally obligated to serve.

This isn't a critique of operational thinking per se. Operational grounding matters. Organizations that collapse under enforcement pressure don't serve anyone. But the strategic question is about sequencing and priority: capacity should be built toward access outcomes, not used as a ceiling on what access outcomes are expected.

The Web Content Accessibility Guidelines (opens in new window) framework itself reflects this logic. WCAG doesn't offer a reduced standard for under-resourced organizations — it offers a clear target and leaves implementation pathways to the entity. The standard is the standard. How you get there is yours to determine.

The Northeast ADA Center (opens in new window) has published guidance emphasizing that technical assistance exists precisely to help organizations build capacity toward compliance, not to reframe compliance around existing capacity. That distinction — capacity-building versus capacity-accommodation — is where the strategic alignment question lives.

What the Evidence Actually Shows

David's article references regional ADA Center training data showing that entities seeking guidance are often navigating genuine resource limitations rather than gaming the system. That's accurate, and it matters for how technical assistance is delivered. But it's worth separating the motivation question from the outcome question. An organization can be genuinely resource-constrained and genuinely well-intentioned and still produce access failures that harm real people. Intent doesn't change the outcome for the user who can't access the service.

Research from WebAIM (opens in new window) consistently finds that the most common accessibility failures on high-traffic websites — missing alternative text, inadequate color contrast, unlabeled form inputs — are not technically complex to remediate. They persist not because organizations lack capacity but because accessibility hasn't been embedded in standard workflows. That's an organizational design problem, not a resource problem, and it doesn't resolve through enforcement moderation.

Separating the Enforcement Question from the Capacity Question

The more productive analytical move is to separate the enforcement question from the capacity question entirely. Enforcement standards should reflect what the law requires and what access actually demands. Capacity-building infrastructure — technical assistance, phased timelines, implementation guidance — should be robust enough to support organizations in meeting those standards. Conflating the two, allowing capacity limitations to moderate what counts as compliance, produces a system where the legal standard quietly retreats to meet organizational reality rather than organizational reality rising to meet the legal standard.

For practitioners working in strategic accessibility alignment, this distinction has direct operational implications. Compliance programs designed around outcome metrics — actual user task completion rates, assistive technology compatibility testing, real-world usability data — produce different results than programs designed around process metrics. The former requires more from organizations. It also delivers more to the people the law was written for.

The capacity argument deserves a seat at the implementation table. It shouldn't have one at the standard-setting table. For practitioners, that means one concrete reorientation: when your organization's compliance program is being scoped, insist that the success criteria are defined by user outcomes, not process milestones. If the program can't answer whether a screen reader user can complete the task, it isn't measuring the right thing.