Re: Getting a custom Chromium-based application to work with NVDA
|
Hi, For situations like this, an app module for the app must tell NVDA that a certain window is a Chrome document (via chooseNVDAObjectOverlayClasses method). A simple app aliasing (which is essentially what you’re doing with JAWS) won’t work in NVDA at the moment (in Python, app module aliasing is done by “from something import *”), as there is no app module for Chrome, as NV Access believes that the rendering engine used by Chrome is used in other situations. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Graham McDermott
Hi, I have an application that is using an embedded Chromium browser to render to the screen. As such it exposes the accessibility interfaces available from Chrome. What do I need to do to get my application to be recognised by NVDA as a chromium-based browser, and use the Chromium ia2 code? In Jaws I can specify in a config file that my task (say "myapp.exe") is Chromium by putting an entry "myapp=Chrome" in the ConfigNames.ini file. Is there an equivalent in NVDA? Thanks, Graham
|
|
|