The Procurement Gap Nobody Talks About in Accessibility

Marcus makes a compelling case for operational capacity as the missing metric in his recent analysis of why compliance frameworks fail public agencies. The argument is structurally sound — documented accessibility and operational accessibility are categorically different things, and federal frameworks have only ever required the former. But there's a mechanism that keeps operational capacity perpetually underfunded and organizationally marginalized, and it sits upstream of programs entirely: procurement.

How agencies buy technology and services determines what operational capacity is even possible to build. And right now, procurement systems are almost perfectly designed to select against sustained accessibility.

How Procurement Specifications Set the Ceiling for Disabled Users

When a public agency issues an RFP for a benefits portal, a housing application system, or a transit information platform, the accessibility requirements in that solicitation document determine the ceiling of what vendors will deliver. In practice, those requirements are almost universally written to mirror WCAG 2.1 Level AA conformance (opens in new window) checkpoints and Section 508 technical standards (opens in new window) — both of which are documentation frameworks, not operational ones.

Vendors respond rationally to what gets evaluated. If an RFP scores accessibility on the presence of a VPAT and a conformance statement, that's what vendors produce. The Voluntary Product Accessibility Template (opens in new window) system, administered through GSA, was designed to create market transparency around accessibility features. Instead, it has largely become a procurement checkbox that sophisticated vendors know how to satisfy without delivering systems that actually work for disabled users in operational conditions.

This isn't a vendor ethics problem. It's a specification problem. Agencies aren't writing procurement requirements that demand operational evidence because their analytical frameworks — and the legal standards those frameworks derive from — don't define operational accessibility as a measurable deliverable.

The Section 508 Refresh Didn't Fix the Specification Gap

The 2017 Section 508 refresh was widely understood as a modernization of federal accessibility standards, aligning them more closely with WCAG 2.0 and extending coverage to more categories of information and communication technology. The Access Board's final rule (opens in new window) was substantively important. But it didn't address the specification gap in procurement because it couldn't — the refresh governed technical standards, not acquisition practice.

GSA's government-wide Section 508 program (opens in new window) provides guidance on procurement, including resources on how to write accessibility requirements into solicitations. That guidance exists and is reasonably detailed. The problem is that contracting officers, who ultimately write and evaluate RFPs, rarely have the domain expertise to translate technical accessibility standards into operationally meaningful evaluation criteria. The result is that procurement documents reference Section 508 compliance as a contract requirement while simultaneously lacking any mechanism to evaluate whether delivered systems actually meet that requirement in use.

As Marcus explored in the operational capacity framework, serving a Spanish-speaking screen reader user through a housing application requires simultaneous competence across multiple domains. No VPAT captures that. No conformance statement tests it. And no standard RFP evaluation rubric scores for it.

Strategic Alignment Requires Working Backward From Procurement

At AccessibilityReviewed.org, our CORS analytical approach treats strategic alignment as the dimension that determines whether accessibility work is structurally sustainable or perpetually reactive. For public agencies, strategic alignment on accessibility has to mean something specific: accessibility requirements embedded in procurement cycles, not retrofitted into programs after contracts are signed.

This is where the counterpoint to Marcus's framework becomes concrete. Operational capacity isn't just an organizational infrastructure question — it's a market-shaping question. Agencies that write operationally grounded accessibility requirements into solicitations change what vendors build, which changes what the market offers, which changes what operational capacity is achievable at scale. The DOJ's technical assistance resources on Title II obligations (opens in new window) emphasize effective communication as a program access requirement — but effective communication with disabled users through a procured digital system requires that the procurement process specified effective communication as a deliverable.

The Great Lakes ADA Center (opens in new window) and peer regional centers have documented extensively how agencies struggle to translate legal obligations into operational practice. The translation failure they observe downstream — in programs, in service delivery, in complaint response — frequently originates upstream in procurement specifications that created systems incapable of meeting those obligations regardless of how well the program office manages them.

What Operationally Grounded Procurement Looks Like

This isn't theoretical. Some procurement offices have begun writing accessibility requirements that go beyond conformance documentation. Operationally grounded specifications tend to share several characteristics: they require user testing with disabled participants as an acceptance criterion, not just a development activity; they specify performance under assistive technology combinations in scope for the user population; they include accessibility in service-level agreements with measurable thresholds; and they require remediation timelines tied to contract performance rather than voluntary corrective action plans.

None of these approaches require new legal authority. They require contracting officers with accessibility domain expertise, or access to that expertise through procurement support structures. The Northeast ADA Center (opens in new window) has developed training resources specifically oriented toward procurement contexts, recognizing that the acquisition phase is where accessibility outcomes are largely determined.

The Upstream Intervention

Building on the operational capacity framework Marcus articulates, the strategic alignment question for practitioners isn't only how to build organizational infrastructure for sustained accessibility — it's how to ensure that the systems agencies procure are capable of supporting that infrastructure in the first place.

Compliance frameworks have failed to require operational accessibility, as Marcus documents carefully. But the mechanism of that failure runs through procurement. Agencies inherit systems that cannot serve disabled users well, then build programs around those systems, then measure compliance against documentation those systems can produce. The loop closes without ever touching actual operational capacity.

Practitioners who want to intervene in that loop need leverage points earlier in the cycle. Procurement specification is the highest-leverage point available — and it remains, for most accessibility advocates and analysts, almost entirely unworked territory. The concrete next step isn't another program audit; it's reviewing the solicitation documents that preceded the systems already in production, and writing the next RFP differently.