Announcing a New Project: Building a JAWS-Inspired Screen Reader for macOS

By Uğur GĂŒrbĂŒz, 18 October, 2026

Forum
macOS and Mac Apps

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

Options

Comments

By Daniel Angus MacDonald on Sunday, October 18, 2026 - 21:55

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.

By Choom on Sunday, October 18, 2026 - 22:26

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?

By JC on Sunday, October 18, 2026 - 22:50

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!

By Urh Ć trakl on Sunday, October 18, 2026 - 23:40

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.

By Dennis Long on Monday, October 19, 2026 - 00:54

Go for it.

By Singer Girl on Monday, October 19, 2026 - 01:44

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.

By Igna Triay on Monday, October 19, 2026 - 02:00

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.

By Dennis Long on Monday, October 19, 2026 - 02:12

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.

By Igna Triay on Monday, October 19, 2026 - 02:28

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.

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.

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.

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.

By TheBlindGuy07 on Monday, October 19, 2026 - 03:16

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 :)

By Maldalain on Monday, October 19, 2026 - 03:32

Please do let me know what I can offer of help. I use Mac everyday for text editing, media consumption and browsing.

By ziixies on Monday, October 19, 2026 - 03:44

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

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.

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.

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

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

By Choom on Monday, October 19, 2026 - 04:14

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.

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.

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.

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

By ziixies on Monday, October 19, 2026 - 08:40

Why do we have to get AI to make and work on our code to create our screen reeders? Might seem a bit hypocritical with some of the stuff I've been doing, but that low-key seems a bit lazy especially if you're not testing your own code and taking vibecoding in the name way more then anyone else. again, might seem a bit hipocritical, but for a screen reeder, i would rather learn

By Maldalain on Monday, October 19, 2026 - 10:33

So that’s my answer to “Why rely on AI to develop a screen reader?” If Apple isn’t meeting our needs, someone has to step in. Would I prefer an experienced developer writing and maintaining the code? Absolutely. But that developer also needs to be willing and able to see the project through.
I appreciate anyone who takes on something this difficult, even if they eventually decide to move on. But if they step away because they haven’t received enough encouragement from the community, that shouldn’t mean everyone else has to keep waiting. There should be room for someone else to try, including someone using AI.
Nobody is asking for free software, and nobody is entitled to someone else’s code. If you’re uncomfortable using AI-built software, that’s entirely your choice. But those of us willing to consider it should have that choice too.

By Uğur GĂŒrbĂŒz on Monday, October 19, 2026 - 11:02

I’ve been a Windows and JAWS user since I first started using computers. I wouldn't say I've never touched NVDA, but unfortunately, we never quite bonded the way I did with JAWS.

On top of that, I spent many years working at Braille Teknik Ltd., the distributor of Freedom Scientific in Turkey, handling localization and technical support. Naturally, JAWS has always held a special place for me because it was literally part of my daily work.

I’ve been into programming since I was a kid, though I have to admit PHP was my go-to web language for a very long time. Later on, I started developing in C#, and recently, my path crossed heavily with Python.

I’m no longer at that company; today, I work on the software development and experience team at a company providing digital accessibility services in Turkey. And actually, that’s where my macOS adventure began.

I was developing a custom mobile application for iOS, and my goal was to track VoiceOver in real-time, pulling snapshot and view details of the focused element. That was basically my introduction to Swift and Objective-C. Once I reverse-engineered iOS VoiceOver APIs to get what I needed, I remembered my Mac Mini sitting at home running like a headless server for the past year, and I started digging into macOS accessibility APIs.

To be honest, I didn't trust Apple's AX UI APIs very much at first. But when I realized I could query AppleScript, system events, and other app APIs (like Microsoft Office APIs) to get way more than what standard AX could offer, I decided to dive right in.

I currently have a prototype ready. Even though some folks around here might say "there's nothing concrete yet," I wanted to share it with you all, even though it's still in its infancy. It's currently open for testing in apps like Finder, System Settings, Mail, Safari, and Chrome—but believe me, the roadmap I have in mind for this project goes way beyond that.

**So, why macOS when I already have JAWS?**

Macs have become incredibly powerful, especially with Apple Silicon. Nowadays, with models like the Mac Mini, you can get an M4 chip at a very affordable price. But the real game-changer is their ability to run local AI language models directly on the device.

Think about it: today, JAWS does smart image descriptions via OpenAI APIs. But with local language models running right on a Mac, we can do OCR, screen recognition, image description, and even run agent-based automated tasks without even connecting to the internet. Just running tests with Apple Vision on my M4 Mac Mini, I get OCR and screen recognition results in 0.50 seconds.

This whole journey started with the thought: *"We need to put the power of this processor into the hands of the blind community."* Trust me, you'll see the first beta release right here in a few days.

One quick note: my English is pretty terrible (I'm using AI to translate this post!). If anyone would like to help localize the app into other languages, let's definitely connect. The app will be open-source and expandable through plugins, much like NVDA. You can build plugins using Python, Node.js, or Swift—whatever you prefer, as long as it hooks into the app's APIs properly.

That’s all for now. I’ll be sharing my Google Drive link in the comments very soon. I'm just ironing out a few stability kinks right now. Since I'm announcing this before having a full production pipeline ready, it takes a little extra time.

Best regards,
Uğur GĂŒrbĂŒz

I don't think I can agree with "the vast majority..." I think it is actually a small minority but they are vocal enough for it to feel like that because it can derail the conversation. You probably do need to be thick skinned enough to put out anything in the public domain, but I don't agree that the majority of people are like that.

In a similar way, if I go out walking with my white cane and someone runs straight into me and then has a go at me, I can become of the opinion that no sighted people understand the white cane and that most people are rude. But I haven't noticed the 99% of people who just got silently out of my way. But even if I had, it would be the one incident I would personally dwell on, not the many that are fine.

Anyway, having said that I do thin it is reasonable to have questions, preferably if we could keep them courteous that would be best so we don't end up in another argument. Being kind should not take more effort than being rude.

I would be interested to know for sure if this is a 100% vibe coded project, and how far along it is. I would like to know whether it is a viable long-term option. These days there are so many apps and things being thrown out there because someone got excited vibe coding, that I personally wouldn't want to devote my own time to anything without knowing that it had a more solid foundations - particularly something so essential like this. I'm not saying this particular project is like this, but I would like to know more.

I'm not sure I personally need Jaws on the Mac, but I would like us to have a solid competitor to VoiceOver to give us some more choice, so it is definitely of interest, whether or not it is something I would personally use.

By Michael Hansen on Monday, October 19, 2026 - 13:26

Member of the AppleVis Editorial Team

Hi Igna and Dennis,

I want to address the personal insults directed at Choom in this thread.

You are both welcome to disagree with Choom and challenge his opinions. However, name-calling and personal attacks are not acceptable under our Community Agreement. Regardless of how strongly you disagree with someone or how you feel about their comments, please keep your criticism focused on what someone has said rather than insulting them personally.

Thanks,

Michael

By ziixies on Monday, October 19, 2026 - 14:58

In reply to by Dennis Long

you said.
"when your comments make you come across as an ass remember that."

just remenber that you don't have to personaly name someone to still insult a person

By Choom on Monday, October 19, 2026 - 15:53

In reply to by Uğur GĂŒrbĂŒz

I currently have a prototype ready. Even though some folks around here might say "there's nothing concrete yet," I wanted to share it with you all, even though it's still in its infancy. It's currently open for testing in apps like Finder, System Settings, Mail, Safari, and Chrome—but believe me, the roadmap I have in mind for this project goes way beyond that.

My question stands, now reinforced by the fact that you have a prototype ready. What's the point of announcing and not showing what you built, not even in a teaser video?

Also I don't think that you will get far using AppleEvents, since most applications including Apple's Messages don't support it properly. I tried that path while working on the AI assistant for the American company, and found it to be a dead end, not only due to the lack of support but also because users wouldn't feel very comfortable with constant prompts asking whether they would allow our service to control their applications after they had already granted accessibility privileges.

It is one thing to promise to try building something possibly with community assistance while having an initial prototype to share with the world, and another completely different thing to make a likely empty promise a solution that many others, including the JAWS developers themselves, have allegedly tried and failed to produce.

I don't care about your roadmap, because everyone including myself can have grandiose ideas which aren't really worth anything since all the value is in putting the effort into turning them into reality.

Talk is cheap, show me the code! -- Linus Torvalds

By Daniel Angus MacDonald on Monday, October 19, 2026 - 16:18

JAWS was the first screen reader I have used. back in 2000. NVDA, did not exist then. i wonder how this will work, and how similar or dissimilar it will be. TurnOver is coming along nicely, but since I never properly learned NVDA, I will be able to provide feedback to this screen reader in different ways. I used to be quite the poweruser of JAWS, before 2009, when I learned , what was then, Mac OS X snow leopard. VoiceOver was really maturing, AppleVis wasn't around. now, there are more bugs, butt people need to beta test. most blind people don't have jobs, and a new developer on the seen, is just more competition.. remember Window Eyes and system access, anyone? this screen reader will have it's strengths and weeknesses, just like how NVDA, JAWS, and Supernova do on Windows. regardless of how a screen reader is written, beit assisted by AI, or human, isn't it great we finally have choices as mac users?

By Daniel Angus MacDonald on Monday, October 19, 2026 - 16:37

In reply to by Daniel Angus MacDonald

FYI, makers of console games for Xbox , switch, n Playstation, do this as well. and heck, even Apple. remember the jurnal app anyone? it was supposed to lonch with iOS 18.1 but was delayed until 18.2. we never gave Apple Negative feedback about that? even the new health app isn't here yet, with Apple, saying, it will be available later this year. so don't trample this developer, the cited world has this all the time.

By Choom on Monday, October 19, 2026 - 16:43

In reply to by Daniel Angus MacDonald

I don't think that anyone here is against someone building an alternative screen-reader for macOS, but if someone whose only experience is in building Ikea chairs and tables tells you that they're gonna build a skyscraper next, it it's perfectly reasonable for you to doubt them.

To the developer, by all means, do prove me wrong, because me being wrong here is the best for the community! Go ahead and build that skyscraper! Show me that unlike myself and others, you really have what it takes to succeed! I genuinely want to be wrong here!

By ziixies on Monday, October 19, 2026 - 16:43

In reply to by Daniel Angus MacDonald

yea but tbf who uses the gernal app, no idea why it was even made just to give us less storage to play with ig, also i never new there was a new health app

By Serkan TĂŒrkyılmaz on Monday, October 19, 2026 - 16:45

Hello Ugur, I am a Mac user. I will support your project as much as I can. You continue on this path.
I think your approach is very nice. But apple, I wonder if I allow 3rd party accessibility support?
If you send me the link in the future, I will even send you an e-mail about it in Turkish.