So I haven't dug in to find out if you're using Prism or something similar, or trying to do it with UI Automation etc. If the program reads something that would qualify as being configured to autoread even if not in the visible UI, it is making NVDA interrupt itself.
Usually what happens is that I am reading something in ED Sharp, using NVDA's say all feature, and it suddenly interrupts itself to tell me that someone just boosted a post of mine, and then does not go on with the say all. If you can change the announcement so that it is a polite, non-interrupting call, I don't think it'll make any negative impact on the value of the feature, and I do think it'll fix this problem.
Maybe if there's doubt, adding an item under the autoread page for each of the items, perhaps next to the separator field that says something along the lines of, interrupt current speech or borrow from Aria's term for doing this, assertive or what ever?
So I haven't dug in to find out if you're using Prism or something similar, or trying to do it with UI Automation etc. If the program reads something that would qualify as being configured to autoread even if not in the visible UI, it is making NVDA interrupt itself.
Usually what happens is that I am reading something in ED Sharp, using NVDA's say all feature, and it suddenly interrupts itself to tell me that someone just boosted a post of mine, and then does not go on with the say all. If you can change the announcement so that it is a polite, non-interrupting call, I don't think it'll make any negative impact on the value of the feature, and I do think it'll fix this problem.
Maybe if there's doubt, adding an item under the autoread page for each of the items, perhaps next to the separator field that says something along the lines of, interrupt current speech or borrow from Aria's term for doing this, assertive or what ever?