-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
windows: ability to output to the currently running screenreader #2
Comments
Actually I was trying to get this going with dkager/tolk, but I hit a roadblock and put it aside for now. |
Hi, |
Hi again, after looking at dkager/tolk#23 it appears that the main issue is that the dlls for nvda etc aren't on path. After the recent pyinstaller changes, might it be worth trying to place the dlls in the base path where the python script is being called from? |
Even before Pyinstaller, I couldn't get it to work. I just made a very simple testing script put the dlls where the main script was. |
Hi,
It can be installed with pip install accessible-output2 |
It's for Windows only right, no MacOs? It mentioned about multi platform, but I didn't see VoiceOver Mentioned in the ReadMe. |
The readme doesn't specify, although from looking at the docs it appears to have both mac and linux support as well. |
Hi,
First off, great work on this utility and thanks for making it.
I was first made aware of it via your recent reddit post on the local llama subreddit.
As someone who's been using the cli to interact with llms over the past few years, it's great to have an accessible graphical option that isn't a webui.
It's still early days of course, although a small wishlist item of mine is to be able to output model responses to a screenreader such as jaws or nvda if possible.
I'm not sure how things are on Mac, although on windows the main option currently is to be able to output via the system's main tts which is probably sapi.
I'm not sure how easy something like this would be to implement whilst still staying cross-platform, though.
The text was updated successfully, but these errors were encountered: