Hello AppleVis Community,
I hope you are all doing well. I am writing to share an exciting personal journey and a project that I have recently started developing: Armoni (working title), a brand-new screen reader designed specifically for macOS.
Please note that this is an early-stage announcement—there is no downloadable build or app to share just yet. However, as the architecture and core navigation layers take shape, I wanted to reach out to this amazing community to share the vision, talk about the motivation behind it, and invite beta testers who might want to join me on this journey.
The Motivation & Vision
As someone who deeply values efficiency and intuitive workflow, I found myself longing for the familiar, object-oriented, and structured navigation paradigm found in Windows screen readers like JAWS, rather than being strictly bound to the native VoiceOver paradigm on macOS.
The goal with Armoni is not to replace VoiceOver entirely, but to provide an alternative, highly optimized environment built from the ground up to offer a seamless, fast, and predictable user experience—especially for power users coming from a Windows/screen reader background.
What We Are Building
Armoni is designed to be a comprehensive, cross-application accessibility solution covering the environments we use every day:
Web Browsing: Smooth virtual cursor navigation across modern browsers like Safari and Chrome.
Productivity: Native handling of office applications (Word, Excel, etc.).
Developer & AI Tools: Comprehensive support for tools like Xcode, Terminal interfaces, and modern AI developer workflows (Codex, Claude, etc.).
macOS System Integration: Deep integration with system apps, alerts, notifications, and shell elements.
Call for Testers
Before opening up a broader public beta, I am looking to build a small, dedicated core group of testers who can provide feedback on the early workflows, keyboard maps, and structural navigation behavior.
If you are a macOS user who is excited about a JAWS-like interaction model and wants to help shape the future of accessibility on the Mac, please leave a comment below or drop a brief note about your experience and the tools you use daily.
Thank you so much for reading, and I look forward to connecting with you all as this project grows!
Best regards,
UÄŸur
Comments
interested
I have both Windows and macOS, with the former being a virtual machine with JAWS, because i don't know the URL by heart to download NVDA. I plan to install it. JAWS, i'm relearning, to keep my skills. I'm not sure how much of the Vispero screen reader you want to emmulate, ,,, it surtainly does a lot! I am beta testing TurnOver as well. it'll be interesting how they will differ. send me a download link when your screen reader has a first build. Competition is always a good thing. how will you code it? if it's yourself, that's a Win Win, because you won't need to pay for tokens. what programming language will it be written in, and with both intel and apple silicon macs be supported? i have an old intel macbook air, i use for tinkering. my primary mac is an m 5 macbook pro, which I use for beta testing. I personally have no data on it, I don't mind restoring, as it's stored in one of many cloud services; and, you get more bugs this way. more bug reports, mean more fixes, after all. i'm sure there will be bugs in your first build.
Why announce with nothing to show?
Is this a joke? What's the point of such an ambitious announcement with nothing to show? Are you even aware of the challenges ahead of you? Do you really think you can pull this off without community assistance?
I'm interested!
I'm interested! As a Jaws user, I know that this is going to take off very well. so send me the download link when it's ready. Looking forward to testing it!
Definitely interested!
As someone who has used Windows for 10+ years and has just now bought a Mac, I believe I am the type of person that could both benefit from this and also provide valuable feedback since I am accustomed to how Windows works for daily tasks. Because I am a student, my work primarily revolves around Office apps (Excel/Word), web browsing, media consumption and AI tools. I would be willing to help shape the future of this program and text extensively.
very interested
Go for it.
No need to be so dismissive
No need to be so dismissive. There’s an announcement on here because they’re trying to gage interest if he would want something like this. That should be encouraged rather than just automatically dismissed and calling it. A joke isn’t cool either. I think this is awesome. This should be commended. It might even make me switch to a Mac once it’s ready. I’m so used to the way jaws and windows works that if we could have something that’s jaws like on a Mac I might actually try a Mac someday. You never know. But with people‘s attitude like that it’s definitely not being very supportive. I think this is an awesome idea.
Re, Why announce with nothing to show? Bookmark
Too can play that game so here goes...
Do you have any idea how discouraging your words can be to new developers or people trying new projects? Do you realise that by your, dismissive arrogant attitude you can easily drive people away? If you going to post discouraging stuff like the above, what's the point? Your waisting everyone's time who reads it, and yeah, you waisted wat; 30 seconds to maybe 2 minutes writing that, non constructive post. Have reservations? Fine, but putting them here especially the way they come across? Not helping.
You don't have to be an, parden my language, an ass to get your point across. And no, before you say oh Insult? No; read the context. You can be direct without beeing, how to put it; condescending towards others. You could've said something like,
This will take time, and community effort, you should be aware that you might fall into x, y, and z pitfalls along the way.
The tldr? Think before you post.
Plus, guess who also does this all the time? Sirtain entities called oh I don't know... mainstream developers? Companies? You name it. I.e, ever seen say, oh so an so series or book etc will come out in 2028! Yeah its announced and yet? Nothing to show until... trailer, book etc comes out. This is no different.
I've considered doing something similar
Why won't I because of comments like above. The majority of the community doesn't appreciate what people try to do for it so screw it why should I spend hours to try and help? I just can't believe the attitudes of the community. and yes I'm speaking directly like the negative comments earlier in this thread. so when your comments make you come across as an ass remember that. I agree with the other person who said you could've been a lot more constructive and how is this diffent from a main stream company saying version 8 or 9 of x product will be out a year or 6 month before it is. Sighted people don't complain like the blind community.
re I've considered doing something similar
Same. Not as far as with scren readers but with other projects I've been working on. They'll be accessible because yeah, but, i'm, the blind comunity isn't my target audience, not my primary one anyway because of, yeah, stuff like the above, as an example.
To be fair though, people like that are in the minority. Now. They tend to be the loudest minority which tends to be the problem. But as a whole? Its not bad. Well that and yeah blind community isn't my target audience because, I mean, the sighted market tends to be bigger, so to speak. But things like the above give one pause for sure.
Re: No need to be so dismissive
My questions stand. It took me a single week to build the version of Vosh that I used to make its initial teaser video. and I did it without AI assistance or prior examples to learn from, so it's not even hard. What's hard about the whole thing is the amount of work that it takes to support lots of individual applications that change over time, which is why I question the viability of this project that at the moment has absolutely nothing to show for it and doesn't seem to expect community assistance.
My work on Vosh landed me a job at a US company using accessibility on macOS to build an AI service to summarize and advise people on their own lives, so although I did not provide support for any application in particular in Vosh, I do know how cumbersome it is to address the quirks in lots of applications and maintain support over time, because the company that I worked for had this problem. Although in the case of an AI assistant it's possible to rely on the AI itself to make sense of the content, which was something that I suggested doing shortly before leaving, a screen-reader is a completely different beast.
The reason why I ask whether this is a joke is because this comes right in the heels of Turnover, a vibe coded screen-reader project. In addition I know the public accessibility API all too well to know that this isn't viable without using the private CoreAccessibility framework. One example that I gave on the other thread are the custom accessibility rotors, which to my knowledge are not made available by the public accessibility API.
To me this sounds a lot like someone promising to accomplish a very ambitious goal without even researching the subject. It is likely that, like the developer of Turnover, they believe that vibe coding will carry them over the whole process, but the reality of vibe coding is that current AIs are very bad at software architecture so the code ends up becoming an unmaintainable mess as it grows. It's easy to build some initial version that impresses, but like they say, the devil is in the details, and in this case there isn't even an initial version to show.
Re: I've considered doing something similar
You shouldn't do it to get appreciation, you should do it because it's useful to you. I didn't start Vosh to be appreciated, I started Vosh to prove that building third-party screen-readers on macOS was possible and hopefully get the community to assist building one, which didn't materialize so I abandoned the project. I'd do it all over again under the same circumstances regardless of how well it was received, because at the end of the day it's the contributions not the opinions that matter, and at the time I did not know that the community wouldn't engage.
Editing to switch the formatting to mark down, as well as to add that the reception I had to my initial teaser video for Vosh was a bit scary, because people had very high expectations that I knew that I wouldn't be able to fulfill alone. Also, I have no idea why you think that this kind of announcement is well received by sighted people, because it's not. Vaporware is very poorly received by the sighted, and for that reason alone sighted developers rarely announce things before they have initial implementations to show. In case you don't know most open-source projects fail to gain traction and are simply ignored, which is worse than getting negative criticism because people never end up learning why their projects fail.
Just another AI noise
No thank you. Even turnover was more credible. Fyi it's easy to find if you look for long enough that even some of the OG jaws devs said that it will be virtually impossible to dev a screen reader for macos way back then.
And why base it on jaws while nvda is wide open to inspect so one can get a theoretical idea of how a screen reader general components should interface with specific elements of the OS?
Fun how linux desktop is actually open but no vibe code screen reader is being attempted there but within a month we've got two now, and I can at least respect turnover.
Fun, an llm would happily say hey what keyboard schemas do you want? While this should be among the last steps when making any screen reader like app. Like it's the shortcuts that are the bigger problem with voiceover, well spoiler alert we can customize almost evrything now. But who wants to rewrite or overide some a11y closed apis? As this is what would be ultimately needed for the mac. I honestly wonder though with one of latest apple paper about this comuter vision model about UI detection for app intents if attempting the off screen model trend again could go somewhere, a question for you @choom and other knowledgeable developers out there.
See? This is the kind of words / questions we should see in such threads, a 15-20% people who are developers and or at least can ask the right questions and other who know the technicalities and security risk of beta testing such a product. The "I use jaws and I'd want something similar on the mac" doesn't help anybody.
Just as a side note, I have theorized with gemini a couple days ago if I'd need to go and read / understand how to navigate in chromium full source code to get the accessibility tree of any page so maybe one can build a screen reader agnostic accessibility view, not at the os accessibility level but directly from what any dev can see in the console, and then it mentiones headless browsers and how chromium or similar can natively give the json of a given page. Then we would of course have the problem of the anti bot and anti scrapers, how to actually give real hardware profiles to mitigate that, and so on.
Of course I am just a student currently and centering a react div gives me a headache so this is way way above my knowledge, but this is at least the kind of technical discussions we should have whenever such topic is discussed.
Edit: I don't remember what was different in the 9 other drafts :)
Interested
Please do let me know what I can offer of help. I use Mac everyday for text editing, media consumption and browsing.
no thank you
i'm sorry, but why is it that after ternover was made, other people are trying to hop onto the bandwaggon.
ternover is better imo then what this would be, and i hav pretty bad issues with to
Re: Just another AI noise
I have considered training such a model myself, it is actually something that I have planned to do at some point to work on once I get my Mac Studio back. My first idea will be to just build an OCR trained on rasterized characters using the San Francisco and Menlo fonts for variable and mono space characters respectively on a 32x32 pixel square, that will be then vectorized and classified based on intersections and curves so it will be a very robust OCR also capable of solving the old CAPTCHAs based on blurry contorted text. My second idea will be to recognize the shape of buttons, switches, sliders, and so on. The general idea is to build an iPad application that can recognize and generate accessibility elements for images captured using an HDMI dongle, to make navigating inaccessible interfaces like PC UEFIs possible, but I have no plans to target macOS specifically both because I've never experienced Liquid Glass visually and because it would require screen capturing privileges, which last I heard are automatically revoked after a certain amount of time by the system thus providing a bad user experience, but answering your question, I think that's a very viable option for Apple.
Re: No need to be so dismissive
yeah at least ternover had a virsion that we can look at.
also im not gonna say anything about this guys account, because this person has apparently been on this site for 4 years and 4 months, but this is his/her only post here
Re: I've considered doing something similar
Just as you have the right to criticize us for apparently being "asses we have the write to criticize someone who has most likely vibe coded this and hasn't even shared anything to show for it, which is even worse than turnover because at least turnover had something to show for it and at least we were able to actually discuss what the issues were I do agree about the blind community though there is some people who are definitely a lot more entitled than others, but that doesn't mean you put the branding on everybody. doing that, in my opinion just makes you as bad as them and that's something I really do not want to say on somewhere as public as this
Clarifying why I think this is a joke
As I said previously, this thread comes right on the heels of Turnover, which is still featured on the front page at the time of this comment. If the author wanted to gage interest, all they would have to do would be read the Turnover thread and then start their own thread with at least a teaser video and an explanation of what makes this screen-reader, which by the way doesn't even have a name, different or better than the alternatives. As it stands, it sounds like the original poster, who hasn't even replied to anyone on the thread yet, isn't really taking this seriously, so to me this is a joke until proven otherwise.
Re: Just another AI noise
This is why I respect you so much. I didn't understand some of what you said there 😂 but thank you! this is the kind of discussionbs applevis deserves. So cool my idea has something at least.
PS: my accessibility tree dump idea was more to get headless chromium and, still idea stage, then pipe everything in emacs / emacspeak with something that can then pass the events / other inputs back in the real browser behind so at least us blind can get everything inside one monolithic that can work pretty similarely everywhere. Will probably go nowhere more than the ideation itself, but who knows. I think tv raman theorized this a couple years ago, and he has always said that screen reader apis are a lossy way for us blind to in modern ui computing unlike the previous terminal world.
Re: Just another AI noise
I did not intend to make my comment cognitively inaccessible. Feel free to ask questions by private message if you wish because this is off-topic here, both you and anyone else wanting to understand what I said.
Re: Clarifying why I think this is a joke
To be fair, it is only like 8:30 AM for him so
Re: Just another AI noise
Looks like Linux has entered the conversation too! I recently came across gorca, a new screen reader for Linux, written from scratch in Rust by an experienced engineer working in DevOps and neural networks.
The project was started to address Orca's responsiveness issues under heavy workloads. The developer is openly using AI-assisted coding, but the project also has a clearly defined architecture and an engineering approach behind it.
I haven't tested it myself, as I don't currently have Linux installed, but I thought you'd find it interesting given your comment.
https://github.com/Ravino/gorca
Balls
It's impossible! Talking out his butt.
Also, moderately suspicious....
*Clears throat* Will it be open source?