Is there a possibility to deactivate NVDA for a single application and only use my own data to let NVDA speak #16096
-
Hello Everyone, I have been testing our Software with NVDA and came to the conclusion, that it didn't really work as I expected. So I tried an other approach: I used the controllerClient to give NVDA the strings to read on my own. This works great, but NVDA keeps going and starts speaking the texts it would as usual. I would like to disable this. So my Question is: is there any way to tell NVDA to "ignore" a application? So it only "speaks" if triggered programmatically via "speakText"? Is this best practice to give the wanted/correct audio output? Best regards, |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
I think there may be some confusion here.
You say you have alt+n as your NVDA key, but that is impossible.
Alt+n may be what you use to start NVDA, but the actual NVDA key is going to be
either insert, numpad insert, the capslock key, or all three, depending on what
you selected in the welcome dialog.
Thus, to activate sleep mode, the key sequence is one of:
Capslock+shift+s
Insert+shift+s
Numpad insert+shift+s
|
Beta Was this translation helpful? Give feedback.
-
While it is really nice you're trying to make PowerBuilder accessible for screen reader users, the proposed approach is not really scalable. It will not work for Braille users, will make all familiar NVDA shortcuts such as |
Beta Was this translation helpful? Give feedback.
-
Yes I'd discourage making the app self voicing merely because you will, at some point need access to explorer or other in built windows system and many self voicing programs end up being silent here as they are in effect in Windows. Take Newsbridge, a program I use a lot but the author went to self voicing and hence in Windows routines, there are either two voices, or a big lag while windows sorts out what the heck its meant to be doing before the snappy nvda voice catches up. so as your program needs to be snappy, it really does need to be using its input from the software and using this to make a screenreader talk. Brian
…--
***@***.***
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
***@***.***, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: Łukasz Golonka
To: nvaccess/nvda
Cc: Subscribed
Sent: Friday, January 26, 2024 11:24 AM
Subject: Re: [nvaccess/nvda] Is there a possibility to deactivate NVDA for a single application and only use my own data to let NVDA speak (Discussion #16096)
While it is really nice you're trying to make PowerBuilder accessible for screen reader users, the proposed approach is not really scalable. It will not work for Braille users, will make all familiar NVDA shortcuts such as NVDA+Tab not working etc. In general controller client is only usable to present simple text notifications and in games, where standard keyboard interactions paradigms are not applicable. It will really be better to improve accessibility of PowerBuilder's GUI, rather than trying to hack around the problem.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
See: https://www.nvaccess.org/files/nvda/documentation/developerGuide.html#toc26