Re: Process to make an NVDA app-specific addon for a web-based application
Julie Stoltz <jstoltz@...>
Thank you for the information. Your suggestion is actually in the works already. Our developers are creating a new implementation that will not be browser dependent. Unfortunately, that is about a year away, and we have a client that needs accessibility much sooner than that, so I was hoping to create a solution for the interim.
From: firstname.lastname@example.org <email@example.com> On Behalf Of Joseph Lee via groups.io
Sent: Wednesday, June 17, 2020 2:15 PM
Subject: Re: [nvda-devel] Process to make an NVDA app-specific addon for a web-based application
At the moment there is no way of creating domain specific add-ons. I think a better approach might be looking into making your app usable with browsers other than (or in addition to) Internet Explorer, as IE is under maintenance mode at the moment.
I am very new to this group and the NVDA application, and I apologize if I have missed anything critical in the steps to address this.
I searched the archives and development guide and did not find an answer to my question.
Our company provides a web-based app to our clients. I have been looking into NVDA and I see that it can be used to create application-specific behavior. However, such addons are named for the executable file that opens the application. In our case, our application is opened with a web address in an Internet Explorer 11 browser.
Can NVDA work with domain-specific web applications? If so, how should the addon be named? Are there any config settings I could use to create an alias (I believe this is how JAWS addresses this issue)?
I know I can create an addon for IE itself, but that option would likely interfere with other sites or applications run through IE, so I don’t want to go that route unless absolutely necessary.
Any guidance at all is greatly appreciated.
Technical Communications Specialist
Cycom Data Systems, Inc.