Elektrine lite

← Feed

@JonathanMosen@caneandable.social

Post #3939891

2026-07-19 16:39 UTC

I have been putting Leasey 11.5 through its paces for the last day or so and am very impressed, even amazed. Not everyone will want every feature as is the case with any application or suite of applications. For example, I know Microsoft Word like the back of my hand and use its increasingly capable Copilot features. But others will appreciate a word processor with a good old menu bar, ChatGPT, and comprehensive features. Hartgen Consultancy has published here comprehensive summaries of all the new features, and there are a lot of them, so I won’t go over what has already been well-covered, but I will make a couple of general points. First, if there is one way many developers short-change their users, its through poor documentation, or even no documentation at all. As far as I’m concerned, when you’ve got stable code, you are still not finished until you’ve written proper documentation. A user guide is great, but in this case, the truly context-sensitive help in Leasey 11.5 is exemplary. Anyone teaching a class on how to do proper context-sensitive help needs to use Leasey as a case study. You can be on any control, press Insert+F1, and get help based on that specific control as well as help relating to what you are clearly trying to do given the control you’re seeking help with. The user interface paradigms are similar across applications. So once you understand how to engage with one Leasey application, you can take those concepts to others. This is one of the things that made KeySoft, when HumanWare used to do proper KeySoft, so successful. Consistency is key. That said, talking about applications in this context brings me to an issue I have been pondering as I’ve been exploring. Leasey started off as a tool to maximize efficiency with JAWS. I bought it because I am an efficiency nut. All the features I use are still there, and in fact some have been improved. But with this release, the scope of Leasey has changed a lot. To some extent, this has been a gradual thing, with the introduction in previous releases of features like radio and podcasts. But this release adds many new tools, all of which are very well developed. Since we’ve now gone well beyond optimizing JAWS, and there are now applications that are of interest to those who do not use JAWS, it seems a pity that there is currently no way for those users to take advantage of these applications. If you try to run any of the apps with another screen reader running, you will get a message that they have detected that JAWS isn’t running, and they quit. Since many of these features are now stand-alone executables, I hope a way can be found to create a suite of applications that those who do not use JAWS can purchase. NVDA is incredibly vibrant and continues to gain traction, and Narrator is increasingly viable. I am not suggesting the business model should change at all. Leasey is a commercial product. But with this suite of applications, it seems to me it would make business sense to let people who want to use the product hand over their money, even if they don’t use JAWS. This is not just a Leasey thing either. There are one or two add-ons for NVDA that aren’t really screen reading enhancements that others may want to use as well. In the end though, those who write the code and put the work in have the right to distribute it however they want. They can make whatever business decision they see fit, and to me, that’s the end of it. The second thing I have been reflecting on is putting so many eggs in one basket. If one is using all these tools in the one suite produced by an indie developer, and for any number of very valid and understandable reasons something happens to cause development to cease temporarily or permanently, that is a lot of functionality affected in one hit. Something developed by a team, or by the community through open source, is less at risk of this happening but of course not immune. That does not, however, take anything away from the remarkably good quality of this whole suite, and for the record I also have this same worry with other tools I use such as the StationPlaylist suite. If you are a JAWS user, I highly recommend trying the demo of Leasey 11.5, it is quite something.

Replies (1)

  • @brian@leaseysocial.com 2026-07-19 17:51

    @JonathanMosen Hi Jonathan Long time no speak. I hope you are keeping well. I wanted to thank you very much indeed for the comments you posted here in respect of Leasey 11.5. You didn't have to do that, and it was incredibly kind of you. Wouldn't it be wonderful if the BrailleNote Evolve had that level of context sensitive help? If Humanware could strive for that it would be great. Now, about other screen-readers. I've just had this discussion with someone else, so first, I am going to quote myself. I wrote: What people need to understand is that what makes the apps as good quality as they are, or I hope they are, is because of the combination of coding with external sources and JAWS scripting. And that is what it is, a combination. Many hours have also been put into the scripting for these apps especially with Braille output. I am having a discussion on Mastodon outside of this thread concerning problems with a standalone app to support various screen-readers, and those problems are occurring precisely because there is no scripting or configuration involved. So thank you for your suggestion, but I will stand by this decision to the grave. I will never compromise on quality. End of quote. I can only do what I am comfortable supporting and what I personally want for my users. I want people to have the features they seem to like and where I hope the quality is as good as I can get it to be. I like very few open source apps. Lots of people love them; that's wonderful and I respect that they do. But I do not. I find there is almost no consideration given to Braille output at all of the kind that you will find in Leasey and there is just so much extra chatter, and I do mean, a lot of extra chatter. If people are content with that, I'm glad that is what they want to use. But I do not want it. As you said, I like tools to be efficient. I would rather pack it all in and stop work tomorrow rather than create products where JAWS is not the framework. People can like me or hate me for that; I don't mind. I've had my fair share of both over the years. That is what I know, and I guess people can choose to purchase the products or not, as the case may be. Fortunately, I'm not quite in that position yet. But I am absolutely passionate about this specific issue. Just to be accurate, radio listening was introduced in Leasey version 1 back in 2014. Podcasts, you are right about that. They were introduced just a few years ago. Anyway, thanks again for your comments and the best of luck with your creations on Suno. Again, we have that in common I think.

    Open ##3939890