win10XPE and accessibility, nvda integration

Hello everyone,

I have been trying to get nvda working in win10XPE. Although the included narrator works, it lags behind keyboard presses. There are several issues though:
After I integrated nvda into the iso by adding a portable copy to the iso root, when starting the copy, it does load but no sounds are played. Upon closer inspection with narrator I found out that the sound devices list is empty. In the log is also displayed that an index is out of range, while trying to access an audio device.

Web browsers don't work properly with screen readers. This issue does exist for some time, it also existed in win10PESE. Tested with firefox, integrating internet explorer crashed narrator, maybe switch to admin pluggin breaks it? I have no idea.

Also, there is a syntax error in the nvda script for win10pese when running with PEBakery. PEBakery is very accessible, so if the nvda script can work with PEBakery, that would be very nice. Or is win10PESE at end of life? When checking most of the apps, winnt setup, firefox were out of date. Should we just focus on win10XPE or also aim for the winXXPESE projects?

Thanks in advance

Also, there is a syntax error in the nvda script for win10pese when running with PEBakery.

If you provide the error ? It can be fixed on either PEBakery side or inside plugin.

We do not test projects with PEBakery but when reported and If possible plugins updated.
Eg: I recently updated some plugins following APT requests for PEBakery compatibility.

Why not use BuilderSE.exe or Win10XPE.exe ?

Or is win10PESE at end of life?

Not yet, Bob.Omb working on it
http://theoven.org/index.php?topic=2594.0

When checking most of the apps, winnt setup, firefox were out of date. Should we just focus on win10XPE or also aim for the winXXPESE projects?

I am sure Bob.Omb will update WinNTSetup and FireFox in a short time.

Both projects are good having some internal differences. 

 It is up to your preference to use one or another. 

ps: I use both and more (total 4). 

Hello lancelot,

Thanks for your reply. The syntax error is in the file 1-10_NVDA.Script, on line 79. When removing the if-statement there the project builds in PeBakery. Please note that this statement only errors when the second build is started, at least when I tested it with win1809. I have also tried building win10PeSe with builderSE.exe, but after updating with update exact and secure (with preserve plugin settings disabled, since it was freshly downloaded), I can't select a source: the set source button does nothing, and the other buttons are unlabeled and seem to give me upload/download/compare options.

I've just got nvda working under win10PeSe, by altering line 79 to remove the if-statement causing the problem, but I have no idea if that statement is important. I will do some more research to determine which file is missing, it has to do with UIA support, the log only states that the specified module could not be found. Will rebuild win10PeSe with the latest version of nvda, then check the sourcecode to check which dll it needs.

It would also be cool if nvda could work under win10xpe. I wouldn't know how to get started though, the audio scripts would probably need some modification, maybe we can adapt some part of the win10pese nvda script, but I really don't know.

Hello lancelot,

Thanks for your reply. The syntax error is in the file 1-10_NVDA.Script, on line 79.

NVDA plugin is not part of the project.
better you post this error to its topic
http://theoven.org/index.php?topic=1382

A quick fix would be:
If,%CompareVersions%,Equal,Bigger,,Require_FileQ,RTWorkQ.dll
-->
If,%CompareVersions%,Equal,Bigger,Require_FileQ,RTWorkQ.dll

I have also tried building win10PeSe with builderSE.exe, but after updating with update exact and secure (with preserve plugin settings disabled, since it was freshly downloaded), I can't select a source: the set source button does nothing, and the other buttons are unlabeled and seem to give me upload/download/compare options.

I can not reproduce here.

I need
1) a log after you select source and click "Set Source" button.
2) after Step 1, I need you provide see 2 files
\Projects\Win10PESE\script.project
\Projects\Win10PESE\Config SourceCD.Script

so I am asking for 3 files from you so I can figure out and fix.
log...html
\Projects\Win10PESE\script.project
\Projects\Win10PESE\Config SourceCD.Script

It would also be cool if nvda could work under win10xpe. I wouldn't know how to get started though, the audio scripts would probably need some modification, maybe we can adapt some part of the win10pese nvda script, but I really don't know.

Time, NVDA plugin will work one way or another with Win10XPE

Hello Lancelot,

I've tried one more time with windows defender disabled and by following some other advice from the win10pese forum, apparently the browse button is the third button after the first edit box. This will be helpful in discovering if a bug is pebakery specific. Also thank you for your nvda fix. I'll continue the discussion about nvda in win10pese in it's topic.

apparently the browse button is the third button after the first edit box.

I have not used PEBakery since a year I guess.

Why not use BuilderSE.exe or Win10XPE.exe ?

?

Winbuilder is not very accessible: separate text labels are unreadable with nvda, and in order to know if a plugin is enabled or not I need to look at it's script file. Also, in order to build a project, I need to use the mouse, which is very hard to do. In PEBakery, I can read the instructions as well, which saves me a lot of time wondering threw scripts. In pebakery the buttons also have labels, so I am not forced to guess the right button. Also, dialogs during building, error messages, etc are not accessible; I can use ocr to scan them but it's not always accurate. In PEBakery there are none of these issues. I need to use some complex navigation commands to get if a script is enabled or not, but once you know the commands it's very doable.

apparently the browse button is the third button after the first edit box.

Now I understand what you wrote about.

Selecting "Source" is different between project.

Current SE/Gena projects It is at:
Left tree box - Select: "Config Source" plugin (2nd from top) -> there is Select Source Box

Current Win10XPE:
Left tree box - Main Plugin "Win10XPE" -> There is a big button to Select Source

In time SE/Gena will follow Win10XPE.

**
Thanks for reminding me this.
It is the only disadvantage of wb, sadly there is no news on this,
 and there is very few nvda user on this area.
   

Hi,

Is there any update to get NVDA to work with the latest versions of NVDA and Windows XPE?

Thanks.

@BlindTango

Is there any update to get NVDA to work with the latest versions of NVDA and Windows XPE?

on the nvda xpeplugin interface ensure the 'Program Version' window has either 2020.3 or 2020.4beta4  and run xpeplugin to download new file
these seem to be the latest full and beta versions available

2020.4beta4 has January 13, 2021 release date