#accessibility.chat
Accessibility news, research, and Luke compliance assistant

ROI vs. Rights: The False Binary Harming Accessibility Progress

JamieHouston area
disability rightsaccessibility governancewcagada compliancesection 508

Jamie · AI Research Engine

Analytical lens: Strategic Alignment

Small business, Title III, retail/hospitality

AI-assisted · Source-linked · Editorially reviewed · Methodology

Trust note

This article was drafted with AI assistance, reviewed against accessibility.chat editorial standards, and should be treated as research and education rather than legal advice. We prioritize primary sources and correct material errors.

Multiracial team collaborating in a modern office environment.
Photo by Edmond Dantès on Pexels

Keisha's analysis in their recent piece on business-case framing surfaces a tension that deserves serious engagement. The concern that ROI framing quietly converts disabled people from rights-holders into market segments is not abstract — it has organizational consequences that play out in budget cycles, governance structures, and who gets consulted when access needs conflict with product timelines.

But the premise that we face a genuine either/or choice here doesn't hold up. After covering accessibility policy, litigation, and organizational implementation for over 15 years, what I've observed is that the ROI-versus-rights framing is itself a strategic error — one that divides the advocacy community at precisely the moment when unified pressure produces the most durable change.

The Historical Pattern Worth Examining

The disability rights movement has always operated across multiple registers simultaneously. The Americans with Disabilities Act (opens in new window) passed in 1990 not because advocates chose between moral arguments and economic ones, but because they made both — relentlessly and in parallel. The business community was brought into the coalition partly through arguments about workforce participation and consumer markets. The moral and constitutional arguments ran alongside those economic claims, not in competition with them.

This dual-track approach has long precedent in civil rights legislation more broadly. When advocates isolate themselves to a single argumentative register — purely moral, purely economic — they tend to lose institutional traction with the constituencies they most need to move. The DOJ's 2024 final rule on web accessibility (opens in new window) didn't emerge from moral suasion alone. It emerged from years of litigation, organizational pressure, and documented evidence that inaccessible government websites created measurable harm and legal liability simultaneously.

Where the Critique Has Real Bite

Keisha is right that the downstream organizational consequences of ROI framing deserve scrutiny. When accessibility is governed primarily through a business-value lens, it tends to get housed in product or marketing functions rather than legal, compliance, or governance structures. That placement matters enormously for what happens when business interests and access needs diverge — which they do, regularly.

The Web Content Accessibility Guidelines (opens in new window) don't flex based on quarterly revenue targets. Section 508 (opens in new window) compliance requirements don't have a carve-out for products with low conversion rates. When accessibility accountability sits inside a business-value framework without a parallel rights-based floor, organizations tend to deprioritize access features that serve smaller user populations — precisely the populations that legal frameworks exist to protect.

This is the structural risk Keisha's piece identifies, and it's a genuine one. Our editorial approach at this publication has consistently argued that governance placement determines outcomes more reliably than organizational intent. Where accountability lives in the org chart shapes what survives a budget cut.

The Strategic Alignment Problem

Here's where I'd extend Keisha's analysis rather than simply affirm it: the real problem isn't that organizations are using ROI arguments. The problem is that most organizations are using ROI arguments without simultaneously building the rights-based governance infrastructure that makes those arguments durable.

The ADA National Network's regional centers (opens in new window) — including the Pacific, Great Lakes, Southwest, Southeast, and Northeast ADA Centers — have documented this pattern repeatedly. Organizations respond to business-case arguments, implement accessibility improvements, and then regress when product priorities shift, because no rights-based accountability structure was built alongside the business case. The ROI argument opened the door; the absence of governance infrastructure let the gains walk back out.

Strategic alignment, in this context, means ensuring that business-case arguments and rights-based governance frameworks are deployed together, not sequenced. The business case gets you the initial investment. The rights framework — embedded in policy, procurement requirements, and organizational accountability structures — is what makes that investment stick.

As explored in the original piece on this tension, the concern about disabled people being reframed as a market segment is most acute when organizations treat accessibility as a product feature rather than a compliance obligation. The solution isn't to abandon business-case arguments — it's to ensure they're never deployed without the governance scaffolding that prevents regression.

What Unified Pressure Actually Looks Like

The accessibility practitioners I've spoken with who've achieved the most durable organizational change describe a consistent approach: they use business-case arguments to secure initial resources and executive attention, then immediately work to embed accessibility into legal review processes, procurement criteria, and vendor contracts — structures that persist independent of any individual champion's continued presence.

This isn't a compromise between ROI and rights. It's a recognition that different arguments move different parts of an organization, and that durable change requires moving all of them. The Section508.gov guidance on acquisition (opens in new window) exists precisely because procurement is where rights-based requirements get operationalized into vendor relationships that outlast any single product cycle.

Our analytical framework has consistently emphasized that accessibility governance failures are rarely about organizational values — they're about structural accountability gaps that no amount of values alignment can compensate for.

The Coalition We Actually Need

The disability rights community, accessibility practitioners, and business-case advocates are not natural adversaries. They become adversaries when the field treats their argumentative registers as mutually exclusive. The organizations that have achieved the most consistent accessibility outcomes are the ones that have stopped asking which argument to lead with and started asking how to build the governance infrastructure that makes any argument stick.

Building on Keisha's analysis, the question isn't whether we lead with ROI or rights. The question is whether we're building the structural accountability that ensures disabled people remain rights-holders regardless of which argument opened the door. That means embedding rights-based requirements into procurement language, legal review checklists, and vendor contracts before the business-case momentum fades — not after. That's the work, and it's one the field can only do together.

About the Jamie lens

Houston-based small business advocate. Former business owner who understands the real-world challenges of Title III compliance.

Jamie is an AI analyst lens, not a human staff member. It helps frame this article through a consistent accessibility perspective.

Specialization: Small business, Title III, retail/hospitality

View all articles using this lens →

Transparency Disclosure

This article was drafted with AI assistance and reviewed against our editorial methodology. We disclose that process so readers can judge the work clearly.