Why Silicon Valley Hates Me and You: The Disability Dongle

The author is seeing that it's easier for one team to get backing (VC money, course credit, design awards, TED talk applause, etc.) for "solving" an accessibility problem than for us to enforce that entire industries follow good accessibility practices in new work and retrofit existing work. In theory industry-wide enforcement is the sort of thing legislation like the ADA solves, but obviously that hasn't been completely effective. Not sure how to fix it.

There was a subthread recently complaining about password managers and their UX problems. These aren't aimed specifically at "disabled" users, but I think it's a similar situation. We can't reliably enforce good standards for sign-in (whether that's just setting the autofill attribute correctly and choosing the correct event handlers for Javascript validators or something far more ambitious), so we expect a password manager to just deal with the web as it is. IMHO they work remarkably well given that constraint, but it's not optimal overall.

The author is simultaneously correct and incorrect.

The author is correct that simple and cheap changes such as ramps and door knobs are the logical fixes. And yes, based on personal experience, companies hate disabled people at the first sign that they will be an inconvenience to the company.

However, nature has no such things. If you enjoy nature and the outdoors, then user-specific equipment can provide capabilities not available through cheap alternatives. The prototypes shown are always marketing with some flair to it. Yes, the noise and bulk are terrible, but proof of concept can lead to improvements over time - eg you're looking at a some no-name competitor to the Model T (prototype suit), just imagine what the 2026 civic will look like (suits 75 years from now).

> I don’t need a stair-climbing wheelchair that costs $30,000 and requires a maintenance crew. I need better doorknobs and/or a ramp. But a ramp is boring. You can't make investors have a hard on for a ramp that doesn't connect to the cloud. You can’t give a TED Talk about a ramp. You can’t get venture capital funding for a slightly wider doorframe.

I thought the idea behind exoskeletons and fancy wheelchairs was that they allow handicapped people to go more places, not to substitute for better infrastructure. I haven't seen any of the companies behind these devices claim that they make such improvements obsolete. And as the post mentions, such infrastructure is useful for anyone with luggage, a stroller, or a hand truck.

And yes, the cost of such devices is high today, but that's true of any new technology. The first print reading devices were huge machines that cost tens of thousands of dollars. Now the technology is free on your phone. Early hearing aids were bulky, expensive, and not much better than an ear horn. Now they're affordable, compact, and have handy features like bluetooth connectivity. My guess is that most of these prototypes will fizzle and go nowhere, but some will succeed, and the lives of disabled people will be improved by them.

Edit: Pangram says the entire post is written by AI. I've flagged it for misrepresenting the author. https://www.pangram.com/history/06093378-dcca-42d8-b683-5ed7...

The real problem IMO is for most SV companies, the audience is the investors and the press, not the actual customer. Which I guess kind of makes sense structurally -- if the idea is to grow fast and exit, then you gotta know who butters your bread, but I think it's bad structurally for problem solving and building sustainable businesses. I know in the past "small" businesses got kind of denigrated as "lifestyle" businesses, but I think we structurally need more funding around things that solve real problems but aren't going to "CHANGE EVERYTHING!!!" and maybe only end up worth a few tens of millions instead of billions or trillions.

Totally blind person. I once had this bright idea that the blind community could fix Linux into our perfect platform. I don't care all that much anymore about anything being fixed, foss or not. FOSS is everyone scratching their own itch, and if a developer who can see creates a program that scratches his itch but isn't accessible, but his itch is scratched, why would he then spend time fixing it up for the one blind Linux user that made an issue on Github about it?

For non-FOSS products, it's even worse. There is no way to tell Amazon that, for the past several months, their library view for Kindle on iOS was inaccessible to VoiceOver, with the books having no accessibility label, and the only way one can tell what book they're about to open is through VoiceOver's tiny on-device image describer model. Of course, in iOS 27 (beta currently) this is improved, but it shouldn't have to be. The last few versions of Kindle has begun fixing this, but last time I tried, about a week ago, it could easily break even just by my scrolling the view a few times.

So I don't even bother anymore. If Google can stand having poor Braille support on Android, fine, I'll use an iPhone. If Apple can stand having awful Google Docs support, which I use at work, on MacOS, I'll use Windows or even Linux where it works fine. If an image isn't described, I will put it through AI. If a page doesn't work well with a screen reader, I'll send it through AI too. If I want to play a video game where 99% of them […]

Specifically about accessible websites: I’m a web developer. At the request of a designer I work with, I spent a couple hours making a Claude skill that would run through WCAG AA and AAA, check contrast, screen reader experience etc. Since then, we’ve caught many little issues and a few big ones like adding a parallel screen reading element for a visually-oriented search tool. Building and testing the skill gave me better insight into WCAG, too.

I auto-run the skill when certain changes are detected in a branch and it takes just a few minutes. Recommended if your work shows up in browsers.