Operational Capacity Is the Metric Compliance Was Never Built to Measure

David's structural critique of the compliance industry is sharp and largely correct. The audit-as-endpoint model does treat accessibility as a state rather than a capacity, and that framing has calcified failure across jurisdictions for decades. But in his analysis of why compliance frameworks perpetuate the semantic translation gap, the diagnosis stops one layer short of where practitioners actually need to intervene.

The compliance industry isn't the root problem. It's a symptom of something more fundamental: public sector organizations have never been required to demonstrate operational accessibility — the sustained, real-world capacity to serve users across disability and language dimensions simultaneously. They've only been required to demonstrate documented accessibility, which is a categorically different thing.

This distinction matters enormously for how we think about solutions.

What Operational Capacity Actually Means for Accessibility Programs

At AccessibilityReviewed.org, our analytical approach distinguishes between four dimensions of any accessibility situation: community impact, operational capacity, risk exposure, and strategic positioning. The compliance industry David critiques has colonized the risk and strategic dimensions almost entirely. What it has systematically neglected is operational capacity — the organizational infrastructure, staffing, workflow integration, and feedback mechanisms that determine whether accessibility commitments survive contact with daily operations.

Consider what operational capacity requires in the specific context Patricia's original analysis and David's subsequent framework piece both address: a Spanish-speaking screen reader user attempting to complete a housing application. Serving that user well requires simultaneous operational competence across at least five domains: assistive technology compatibility maintained through content updates, translated interface strings that stay synchronized with English source content, workflow routing that delivers translated materials rather than defaulting to English, staff capacity to handle escalations when automated systems fail, and feedback channels the user can actually access to report failures.

No WCAG audit captures all five. No Title VI (opens in new window) language access plan addresses all five. The Section 508 (opens in new window) procurement standards touch perhaps two. The gap isn't primarily that frameworks don't intersect — it's that no framework currently in federal use is designed to assess whether an organization can sustain accessible service delivery as a living operational function.

The Federal Capacity Assessment Gap

The Department of Justice's guidance on web accessibility (opens in new window) and the ADA National Network's technical assistance resources (opens in new window) both emphasize compliance outcomes. What neither resource systematically addresses is organizational capacity to maintain those outcomes. This isn't an accident or an oversight — it reflects the enforcement model that underlies both frameworks.

Title II and Title VI enforcement is complaint-driven and retrospective. An agency gets investigated after someone is harmed, not before. That enforcement architecture creates rational incentives for organizations to invest in documentation — which creates a defensible record — rather than operational infrastructure, which is expensive, hard to demonstrate, and doesn't directly reduce complaint-driven liability. The compliance industry David identifies didn't create these incentives. It responded to them.

The Great Lakes ADA Center (opens in new window) and other regional technical assistance centers have long documented that small and mid-sized public entities face genuine resource constraints in building sustainable accessibility programs. Their technical assistance model recognizes that compliance documentation and operational capacity are different problems requiring different interventions. The compliance audit industry, by contrast, has a financial incentive to treat them as the same problem — because audits are billable and ongoing operational support is not.

Why Capacity Measurement Is Hard — and Why That's Not an Excuse

There's a genuine methodological challenge here that David's structural critique, while accurate, doesn't fully reckon with. Operational capacity is harder to measure than conformance. You can run an automated scan against WCAG 2.1 success criteria (opens in new window). You cannot run an automated scan against "does this organization's content update workflow preserve translated interface strings?"

But difficulty of measurement is not the same as impossibility. Several existing frameworks gesture toward capacity assessment without fully committing to it. The W3C's Web Accessibility Maturity Model (opens in new window) attempts to assess organizational processes rather than just technical outputs. The Section 508 Program Maturity Report (opens in new window) that GSA administers tracks agency-level program development, not just conformance rates. These are incomplete instruments, but they represent the right analytical instinct: asking whether organizations have built the systems to deliver accessibility, not just whether they produced accessible artifacts at a point in time.

The Pacific ADA Center's (opens in new window) technical assistance work with state and local government entities has consistently found that the organizations with the strongest long-term accessibility outcomes are those that integrate accessibility into operational roles — procurement, HR, IT governance, content management — rather than siloing it in a compliance function. That's a capacity finding, not a conformance finding.

Changing What Public Agencies Must Demonstrate

Building on the structural analysis David offers, the practical implication isn't primarily to reform or bypass the compliance industry. It's to change what public sector organizations are required to demonstrate to regulators and the public.

If DOJ enforcement of Title II web accessibility required agencies to document not just conformance but operational maintenance processes — who owns content updates, how translation synchronization is verified, what the escalation path is when a screen reader user encounters a broken workflow — the compliance industry would rapidly develop tools to assess those things. Markets respond to requirements. The problem is that current requirements don't ask the right questions.

For practitioners working inside public sector organizations right now, the operational capacity frame offers something more actionable than structural critique: a checklist of organizational functions that need to exist, not just a checklist of technical criteria that need to pass. That's a harder conversation to have with leadership, but it's the conversation that actually moves the needle on whether a Spanish-speaking screen reader user can complete a housing application next Thursday, not just last Monday when the audit ran.

Our analytical framework at AccessibilityReviewed.org treats operational capacity as the dimension most likely to predict real-world user outcomes — and most likely to be absent from compliance documentation. That's not an argument against compliance. It's an argument for demanding that compliance mean something operationally, not just documentarily.