Captive by Design: How Proprietary Tech Traps Disabled Americans—and What Open Standards Can Do About It

Consider what happens when a screen reader manufacturer discontinues a product line. For a sighted user, the loss of a favorite application is an inconvenience. For a blind professional who has spent years customizing that tool's settings, learning its keyboard shortcuts, and integrating it into every corner of their workflow, it can be a workplace crisis. Consider what happens when a wheelchair-mounted communication device runs on a proprietary operating system that the manufacturer stops supporting. The device still works—until it doesn't. And when it fails, the user may find that no independent technician can repair it, no open community can patch it, and no alternative device speaks the same protocol.

These are not hypothetical scenarios. They are recurring realities for the estimated 61 million adults in the United States living with some form of disability. And they share a common cause: the dominance of closed, proprietary technology ecosystems that treat accessibility features as add-ons, users as consumers rather than participants, and interoperability as a competitive threat rather than a public good.

The Lock-In Problem, Amplified

Vendor lock-in is a frustration familiar to anyone who has tried to migrate a decade of data from one platform to another. For disabled users, the stakes are categorically higher. Assistive technology is not discretionary. It is the infrastructure through which people communicate, work, navigate physical space, and exercise civic participation. When that infrastructure is proprietary, its users are not merely inconvenienced by switching costs—they are rendered dependent on the continued goodwill and commercial viability of a single vendor.

The problem manifests across the technology stack. Augmentative and alternative communication (AAC) devices frequently use proprietary symbol libraries and file formats that cannot be transferred between platforms. Smart home systems marketed as accessibility solutions—voice-controlled lighting, automated door locks, environmental sensors—often require hub hardware and cloud subscriptions that can be discontinued without notice. Major mobile operating systems implement accessibility APIs inconsistently, meaning that a feature working reliably on one version of iOS or Android may break silently after an update, leaving users stranded until a fix is issued.

Disabled technologist Haben Girma, the first deafblind graduate of Harvard Law School and a prominent digital rights advocate, has written and spoken extensively about how inaccessible design is not accidental—it reflects choices made by development teams that do not include disabled people and do not treat accessibility as a core requirement. The result, she argues, is systemic exclusion dressed up as technical limitation.

Open Standards as Infrastructure for Dignity

The Web Content Accessibility Guidelines (WCAG), maintained by the World Wide Web Consortium (W3C), represent one of the most successful examples of what open standards can accomplish. By establishing a shared, vendor-neutral framework for accessible web design, WCAG created a common language that developers, procurement officers, and advocates could all use. It made accessibility auditable, enforceable, and improvable through community consensus rather than corporate discretion.

The open-source community has extended this logic into hardware and software domains where proprietary systems have historically dominated. The OpenAAC initiative has developed open symbol libraries and file formats for augmentative communication, allowing families, therapists, and developers to build and modify tools without licensing fees or vendor dependency. The OpenAssistive project aggregates open-source assistive technology resources, from switch-access interfaces to braille display drivers, under a framework designed for community contribution.

In the smart home space, the Matter protocol—developed through a cross-industry consortium and released as an open standard—represents a significant, if incomplete, step toward interoperability. While Matter does not resolve every accessibility concern, it creates a foundation on which developers can build without being locked into a single ecosystem. Open-source home automation platforms such as Home Assistant have embraced Matter aggressively and built accessibility-focused community plugins that commercial vendors have not prioritized.

Disabled Technologists Building What the Market Won't

Some of the most consequential open-source accessibility work is being done by disabled technologists who have grown tired of waiting for the commercial sector to address their needs.

Blind Arduino developer and educator Chancey Fleet, based in New York, has championed low-cost, open-source tactile graphics tools that allow blind and low-vision users to create and interpret spatial information without expensive proprietary equipment. Her work at the New York Public Library's Andrew Heiskell Braille and Talking Book Library has demonstrated that open hardware and community knowledge-sharing can deliver capabilities that commercial products charge thousands of dollars to approximate.

In the Deaf and hard-of-hearing community, developers have built open-source captioning tools and sign language recognition projects that operate without the subscription fees attached to commercial equivalents. Projects like the Community Captions initiative have pushed back against the argument that automated captioning accuracy is inherently a premium feature, demonstrating that open models trained on diverse data can perform competitively when the community has both the tools and the motivation to improve them.

These efforts share a defining characteristic: accessibility is not retrofitted. It is the reason the project exists.

The Policy Gap

The legal framework governing accessible technology in the United States is fragmented and, in many respects, outdated. Section 508 of the Rehabilitation Act requires federal agencies and their contractors to procure accessible electronic and information technology, but enforcement has been inconsistent and the standards have lagged behind the pace of technological change. The Americans with Disabilities Act has been interpreted by courts to cover digital spaces, but litigation remains the primary enforcement mechanism—an approach that places the burden on disabled individuals to identify violations and pursue remedies.

What is largely absent from current policy is any meaningful requirement for interoperability or open standards in the accessibility context. A federal agency can purchase an inaccessible proprietary system, discover its limitations after deployment, and face no structural requirement to choose an open alternative. Procurement guidelines encourage accessibility compliance but do not systematically reward architectures that make future customization and community improvement possible.

Advocates including the American Foundation for the Blind and the National Federation of the Blind have called for updated Section 508 standards, stronger enforcement mechanisms, and procurement preferences for technology built on open, interoperable frameworks. The Access Board, the independent federal agency responsible for accessibility standards, has acknowledged the need for modernization, but progress has been slow.

Toward a Right to Modify

Underlying the technical and policy arguments is a more fundamental question about who technology is for. Proprietary assistive technology treats disabled users as consumers of a finished product. Open-source alternatives, at their best, treat them as participants in an ongoing process of refinement.

The difference matters enormously in practice. A user who can modify their AAC device's interface is not dependent on a product manager's priorities. A blind developer who can contribute to a screen reader's codebase is not waiting for a corporation to notice a bug. A deaf student whose school uses open captioning tools is not subject to a vendor's decision to discontinue an education tier.

Building that future requires investment: in open-source accessibility projects, in technical training for disabled developers, in procurement policies that value interoperability, and in standards processes that center disabled voices from the beginning. None of this is simple. But the alternative—a world in which the technology infrastructure of disability is permanently controlled by entities with no accountability to the people who depend on it—is not acceptable.

Open standards and open source are not sufficient conditions for accessible technology. But they are necessary ones. The work of building them belongs to all of us.