The Business Case Is Real — But Who Gets Left Behind When We Lead With ROI?

Jamie's analysis in their recent piece on icon menu failures is strategically sharp. The argument that product teams respond to retention metrics and revenue signals more readily than moral or legal framing reflects a real dynamic I've watched play out across hundreds of organizational accessibility audits. The business case is real. The data holds up. And I've used versions of that argument myself when other approaches stalled.

But after 15 years covering this space, I want to sit with a tension that the ROI framing tends to paper over: when we lead with market opportunity, we quietly reframe disabled people as a consumer segment rather than as rights-holders. That reframing has downstream consequences for how organizations structure accountability, who gets a seat at the table, and what happens when business interests and access needs diverge.

This isn't an argument against Jamie's approach. It's a question about what we're building toward.

The Rights Framework Didn't Fail — Implementation Did

The claim that moral and legal framing has failed to move product organizations deserves scrutiny. The Americans with Disabilities Act (opens in new window) has been law for more than 30 years. Section 508 (opens in new window) has required federal agencies to maintain accessible electronic content since 1998. The DOJ's 2024 final rule (opens in new window) establishing WCAG 2.1 AA as the accessibility standard for state and local government websites represents a significant enforcement escalation.

These aren't weak levers. They're under-enforced ones. The argument that rights framing hasn't worked often conflates a failure of organizational will with a failure of the framework itself. When companies settle web accessibility lawsuits (opens in new window) for amounts that don't exceed the cost of remediation, the problem isn't the legal theory — it's that consequences remain insufficient to change the calculus.

Pivoting to ROI arguments in that environment risks letting organizations off a hook they should remain on.

Community Signal Isn't a Market Research Problem

As I explored in my analysis of community documentation patterns, disabled users have been reporting icon menu failures through forums, social media, app store reviews, and direct feedback channels for years. Jamie frames this as a retention signal that organizations are failing to capture. That's accurate. But it's also a governance failure.

The Great Lakes ADA Center (opens in new window) and peer regional centers have long emphasized that meaningful accessibility requires ongoing community consultation — not just post-hoc analysis of churn data. When organizations treat disabled user feedback as a market signal to be harvested rather than a community voice to be integrated into design processes, they produce different outcomes. Market signals optimize for the majority of disabled users whose behavior is legible in aggregate data. Community governance surfaces the needs of users whose experiences don't aggregate cleanly: people with multiple disabilities, users of less common assistive technologies, people in lower-income brackets who may use older screen readers or mobile-only access.

The WCAG development process (opens in new window) itself is instructive here. The Web Content Accessibility Guidelines emerge from a community of practice that includes disabled people as contributors, not just as test subjects. That participatory structure is why WCAG has remained technically credible across multiple iterations. Organizations that want to replicate that credibility internally need governance structures that match it — not just better analytics dashboards.

When ROI Arguments Reach Their Ceiling

The business case for accessibility has real limits that the field doesn't discuss enough. Return on Disability Group market estimates are frequently cited, and the figures are large. But market opportunity arguments work best when the population in question has purchasing power that companies want to capture. They work less well for disabled users who are disproportionately represented in lower income brackets — a pattern the CDC's disability and health data (opens in new window) consistently documents.

For those users, the business case is thinner. The rights case is not. If accessibility advocacy has fully migrated to ROI framing by the time a product team runs the numbers and decides the market isn't large enough to justify remediation costs, we've lost the argument we should have been making.

This is where our editorial approach at this publication diverges from pure strategic consulting. We're not trying to find the argument that closes the sale. We're trying to build the analytical infrastructure that makes rights-based accessibility sustainable across economic conditions.

The Governance Structure Question

Jamie's piece focuses on where to apply pressure — product reviews, retention metrics, revenue conversations. That's the right tactical question for practitioners working inside organizations right now. But the strategic question is what organizational structures produce durable accessibility, not just accessibility that survives the current product cycle.

Research from the Pacific ADA Center (opens in new window) and others consistently points toward the same answer: organizations with formal disability inclusion in governance — disabled employees in decision-making roles, structured community feedback mechanisms, accessibility embedded in procurement and vendor requirements — outperform organizations that rely on periodic audits and compliance checklists. The business case can open a door. It rarely builds the room.

Building on Jamie's framework, the next analytical step is asking what it would take to make that business case unnecessary — not because accessibility has been achieved, but because the governance structures are robust enough that icon menu failures get caught before they ship, regardless of whether someone has run the retention numbers. That's a different kind of argument, aimed at a different kind of organizational change.

What Community-Centered Analysis Adds

Our analytical framework here treats community input as a primary data source, not a validation layer applied after strategic decisions have been made. That distinction matters for icon menu failures specifically because the technical fix is well understood. WCAG 4.1.2 (opens in new window) has been clear on name, role, and value requirements for interactive components for years. The WebAIM Million report (opens in new window) documents how consistently those requirements are ignored at scale.

The gap isn't analytical. Organizations don't need a better business case to know that unlabeled icon menus fail screen reader users. They need accountability structures that make ignoring that knowledge costly — through enforcement, through governance, through the kind of sustained community pressure that colleagues across this publication have been documenting.

Jamie is right that the business argument is underused. It's also insufficient on its own. The field needs both levers operating simultaneously, aimed at different parts of the organizational structure, to produce the durable change that disabled communities have been asking for, in plain language, for a very long time.