Embed Notice

@tspivey I wanted to mention @NVAccess on this so we can discuss this as I'm not in favor of completely disabling add-ons on secure screens at all and I will not update my NVDA if this happens. Apart from Remote, we need to think about people who prefer a certain speech synthesizer due to, for instance, hearing loss, or cases where the built-in synthesizers do not have very good language support for a given language (for instance, I heard that eSpeak has some foreign languages that are not good at all and there are some OneCore voices that also do not have high quality support for certain languages). Please consider these points before enforcing the inability to use add-ons on the secure screens. The correct approach is to either allow the add-on developer to indicate in the manifest whether the add-on is allowed to run on a secure screen, or to allow a user to individually select which add-ons to copy to the secure screen. The fact that the plan is to just completely disable all add-ons on the secure screen, instead of allowing users to selectively copy add-ons over to the secure screen, when users express that they want this, is not good and it is not in the user's best interest. I am hoping that this thread can start a dialogue about this so that this can be discussed further, as opposed to completely disabling add-ons on the secure screens without considering the possible ramifications.