Readiness Is a Power Question, Not a Process Question

In their analysis of who defines readiness in accessibility reform, Keisha surfaces something the compliance literature rarely names directly: the metrics organizations use to measure their own readiness are metrics those same organizations designed. That's not an oversight. It's a power arrangement.

The piece frames this as a feedback loop problem — affected communities submit complaints into systems that weren't built to hear them, remediation plans get approved without their input, and the cycle continues. That framing is accurate. But the analysis needs to go further: the exclusion of disabled people, limited English proficient individuals, and community advocates from readiness determinations isn't primarily a design gap that better process architecture can solve. It's the predictable output of a compliance regime that treats accountability as an internal organizational function rather than a community relationship. Understanding why that arrangement persists — and what it would actually take to disrupt it — requires a different analytical lens than process reform alone can provide.

The Compliance-as-Self-Assessment Problem

Federal accessibility frameworks, including Section 508 (opens in new window) and the language access obligations flowing from Title VI of the Civil Rights Act (opens in new window), share a structural characteristic: they rely heavily on covered entities to assess and report their own compliance status. The Department of Justice's complaint resolution process (opens in new window) creates an external check, but it's reactive and complaint-driven. Organizations that successfully suppress complaint volume — through inaccessible filing processes, language barriers, or community distrust — face less external scrutiny, not more.

This creates a perverse incentive structure. An organization that makes its complaint process difficult to navigate can report lower complaint rates as evidence of operational success. The National Council on Disability has documented (opens in new window) this pattern across multiple federal programs, noting that complaint data systematically undercounts actual access failures because the barriers to filing mirror the barriers being complained about.

The Web Content Accessibility Guidelines (opens in new window) provide a partial analogy: WCAG conformance testing conducted only by the organization whose site is being tested produces systematically different results than testing that includes disabled users. The technical accessibility community has largely accepted this — user testing is considered a compliance best practice precisely because organizational self-assessment misses what users actually encounter. The same logic applies to organizational readiness assessments for complaint processing, language access, and program accessibility. The compliance frameworks haven't caught up.

Who Does Strategic Alignment Actually Serve?

From a strategic alignment perspective, the question Keisha raises about readiness definition has a sharper edge than it might initially appear. When we talk about aligning accessibility strategy with organizational capacity, we're implicitly asking: capacity to serve whom, as defined by whom, measured against whose experience?

Organizations that treat accessibility compliance as a risk management function — minimizing legal exposure while maintaining operational control — will consistently define readiness in terms that serve that goal. Staffing levels, processing timelines, and vendor contracts are legible to auditors and defensible in enforcement proceedings. The Somali-speaking parent who still can't access her child's IEP meeting is not a metric that appears in a compliance audit unless someone builds her experience into the measurement framework.

This isn't cynicism about organizational intent. It's a structural observation about what happens when strategic alignment is defined internally. The ADA National Network's technical assistance resources (opens in new window) consistently emphasize that genuine accessibility requires centering the experience of people with disabilities in both design and evaluation — not as a values statement, but as a practical requirement for getting the measurement right. Organizations that skip this step don't just fail ethically; they fail technically, because they're optimizing against the wrong indicators.

The metrics organizations control entirely are the metrics they tend to report. Strategic alignment that doesn't include community accountability mechanisms will reproduce this problem regardless of how sophisticated the internal compliance infrastructure becomes.

What Community-Defined Readiness Would Actually Require

The practical question is what it would take to shift readiness determination from an internal organizational function to something that includes affected communities in a structural — not advisory — role. A few mechanisms exist in adjacent fields worth examining.

The Pacific ADA Center (opens in new window) and other regional ADA Centers have developed community-based technical assistance models that position disabled people and advocacy organizations as active participants in compliance planning, not just complaint filers. These models don't eliminate organizational authority over implementation decisions, but they create accountability relationships that external audits alone can't replicate.

Participatory research methodologies, increasingly used in public health and urban planning, offer another model. When affected communities participate in defining the research questions and success metrics — not just validating findings after the fact — the resulting frameworks tend to capture dimensions of the problem that self-assessment misses. Applied to accessibility compliance, this would mean involving disabled people and LEP community members in designing the metrics against which organizational readiness is measured, before the assessment process begins.

The Section508.gov guidance on agency reporting (opens in new window) reflects the current state: agencies report against internally defined benchmarks with limited external community input into what those benchmarks should measure. That's a policy choice, not a technical constraint, and it's one that could be revisited.

The Strategic Case for External Accountability

Organizations sometimes resist community involvement in readiness assessments on the grounds that it creates unpredictability — communities may define readiness in ways that are operationally difficult or politically contentious. That concern is real. It's also, from a strategic alignment standpoint, precisely the point.

Accessibility compliance that only achieves what organizations find operationally comfortable will systematically underserve the communities with the greatest access barriers — because those communities face barriers that are, by definition, operationally inconvenient to address. Building community accountability into readiness determination doesn't make compliance harder for organizations that are genuinely committed to access. It makes compliance harder to fake for organizations that aren't.

The strategic alignment question for accessibility practitioners isn't just how to align internal capacity with compliance obligations. It's how to align organizational accountability structures with the communities those obligations were designed to protect — and to recognize, as Keisha's analysis makes clear, that these are not the same question.

Readiness defined only by the organization being assessed is a power arrangement dressed up as a process question. The practical implication for practitioners: if your readiness metrics were designed without the people those metrics are supposed to serve, you're not measuring readiness. You're measuring comfort.