Login
You're viewing the techdon.dev public feed.
  • May 18, 2026, 12:04 AM

    I just read about a blind person vibe-coding a new email client for Windows. Not linking because I don't want people to pile onto this person, who is a veteran of the software industry and a respected, persistent accessibility advocate and contributor to assistive technology. Instead, I want to point out how badly the commercial software industry, particularly Microsoft in this case, has failed us such that an individual feels the need to do this. Don't know what to do instead though.

    💬 3🔄 30⭐ 50

Replies

  • May 18, 2026, 10:50 AM

    On the one hand, it's good that blind people are taking initiative to solve our own problems, rather than begging big tech companies and/or under-resourced open-source projects to give us what we need.

    On the other hand, I still believe that relying heavily on an LLM to generate large volumes of code is dangerous, and that we don't fully understand the pitfalls.

    💬 1🔄 6⭐ 8
  • May 18, 2026, 10:54 AM

    Check out what Ron Pressler wrote about Anthropic's PR stunt of having agents build a C compiler. He looked at the actual results, not just the hype. news.ycombinator.com/item?id=4

    > Today's models are not yet capable enough to build non-trivial production software without close and careful human supervision, even with perfect specs and perfect tests. Without a perfect spec and a perfect human-written test suite the task is even harder.

    An email client falls in that latter category.

    💬 0🔄 2⭐ 0
  • May 18, 2026, 12:20 AM

    @matt Yeah, I'd be perfectly happy if Microsoft would open-source Outlook Express, especially if I could have it as a portable app.

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • May 18, 2026, 3:25 AM

    @matt vibe coded or hand coded, all that matters is it works, especially for the person who wanted it. I never understood the problem with how a person arrives at a working solution. I mean who would complain about taking a car to get to a shop that's 3 miles away, sure you could walk there, the weird thing here is "people piling on them" If the code works and does what is requested, who cares where it comes from. Vibe coding is not as simple as "Write me an accessible email client." For quality there's still testing, spec design, more testing, redesign, etc. Vibe coding done correctly is still a lot of work. I say congrats to this person for taking the initiative and solving not only their problem but the same problem for anyone else smart enough to use the working code whether written by machine or man, who cares?

    💬 0🔄 0⭐ 0
  • May 18, 2026, 1:06 PM

    @storm @matt People use email clients to access a lot of confidential information, or their workplace has specific email security requirements, or... the list of reasons that email security matters goes on and on.

    The problem with a vibe coded client is that the author did not write, and we can't assume they have read and understood, every character of the code to avoid security issues.

    💬 0🔄 4⭐ 3
  • 💬 0🔄 0⭐ 0
  • May 18, 2026, 2:47 PM

    @KyleBorah @jscholes @TheQuinbox @storm @matt I think we are to the point where the Blind will have no choice but to use what skills they have available to them to get a job done in an acceptable timeframe. Vibe coding software is now a tool in the toolbox. Would I like a senior software engineer to write all of the major software we use? Absolutely! The problem I see is that accessibility is not the priority it should be for many large organizations who certainly have the capital to make this happen. What else are we as Blind people supposed to do in this situation? We either put up with the miserable experiences that large organizations provide or attempt to develop our own. Thank God this is starting to happen. I'm enjoying the discussion from all sides. Keep it coming.

    💬 0🔄 1⭐ 0
  • May 18, 2026, 6:05 AM

    @matt There's a few of them now. As much as I'd love to find something fast, lightweight, portable and probably Win32, I'm not smart enough to audit security here. Rock and hard place comes to mind. I wonder whether anyone's forked Thunderbird and purely concentrated on GUI accessibility? Is the codebase too sprawling to do that with help from an LLM on a reasonably priced plan?

    💬 0🔄 0⭐ 0
  • May 18, 2026, 6:15 AM

    @Scott @matt While I have no influence or involvement where Thunderbird accessibility is concerned - completely different Mozilla subsidiary - I do know there are some folks over there that do care about accessibility, though they probably don't have anyone dedicated to it. Are there open bugs that are languishing or have the bugs not been filed? I can totally understand why they wouldn't be filed if there was no faith they'd be fixed - it's hardly worth putting in the effort if you get 0 back - but I thought I'd check.

    💬 0🔄 0⭐ 0
  • May 18, 2026, 6:16 AM

    @matt @Scott I know the calendar is completely inaccessible, for example, and I don't see that changing any time soon. But if it's core email stuff, there's a much bigger chance that would be addressed.

    💬 0🔄 0⭐ 1
  • May 18, 2026, 6:18 AM

    @Scott @matt I think I've fixed all the rendering engine accessibility bugs that were disproportionately impacting Thunderbird: the typing freeze, etc. But let me know if there are more of those I'm not aware of and I'll see what I can do within my Firefox remit.

    💬 0🔄 1⭐ 0
  • May 18, 2026, 6:43 AM

    @jcsteh @Scott @matt I use Thunderbird as my only email client, and I've learned to work around issues, but I think part of the problem is a11y sometimes is completely screwed in releases. For example I filed a bug on something I consider very serious and basic: https://bugzilla.mozilla.org/show_bug.cgi?id=2019407

    When an email got deleted, the selected/focused email on the list would not be read, and this results in very weird behaviour having to move up and down to know where one is. The bug got solved, as far as I can tell, by accident on a new release. But being in the situation of an email client failing to do very basic a11y things is not ideal.

    Even now, NVDA review cursor commands don't work on the email listview, so 4, 5, 6 won't read the words.

    💬 0🔄 0⭐ 0
  • 💬 0🔄 1⭐ 1
  • 💬 0🔄 0⭐ 0
  • May 18, 2026, 1:36 PM

    @jscholes @jcsteh @modulux @Scott @matt Well, given I'm the person talked about on part of this for the email app, one point of clarification. Sure I'm using vibe coding to write my Quickmail app but the guts of the email handling are coming from the MailKit library. My research says this is widely respected in the development community and pretty much the go to library for handling email in an app. I'm focusing on the user experience and accessibility.

    💬 0🔄 0⭐ 1
  • May 18, 2026, 1:41 PM

    @kellylford @jcsteh @modulux @Scott @matt Appreciate the explanation but at least for me, it doesn't significantly change the risk profile. The data ends up having to move in and out of MailKit to drive and be driven by the UI, and even a well-respected library is unlikely to prevent an LLM from doing something undesirable.

    💬 0🔄 0⭐ 0
  • May 18, 2026, 8:28 PM

    @matt I have seen some people talking about the boom of writing accessibility game mods, positioning it as empowering because we are able to write a solution for our own needs rather than having to wait for a day that never comes. I find this to be extremely misguided. It's true that we are now able to do something that we couldn't before, but calling it a solution is super premature. We still want--and need--the industry to think about us when designing their apps. If we do the work for them, they'll just think "cool, we don't have to worry about this. Thx!" Relying on a small army of unemployed college students paying Anthropic $100/mo to do the work of a AAA studio, for free, is just not sustainable. It is a stunning lack of foresight.

    💬 0🔄 1⭐ 0