6 replies to this topic

[pscEx]

Last days i got to know an issue, which has been unknown for me right now:

Blind users using a screen reader like NVDA, have troubles with selecting / unselecting scripts in a project.
NVDA only reports the scripts' titles in the project tree. Because information like Selected, Unselected, Mandatory, Script, Folder, etc. is displayed by graphical elements, NVDA has no chance to report.

Let me explain here the most important information for blind people:

Generally a script is included in the build, when it is Selected.
The user can toggle between Selected and Unselected by clicking the checkbox in the according script treeview node.
A script can be Mandatory. That means that the script is necessary for the functioning PE and it is allways selected. When the user tries to unselect such a script, then a warning beep is fired, and the script remains selected.
There exists one more script type, the Not Selectable. These scripts are not added to the build, but their GUI information and script commands are used by other scripts, or they perform stand alone functions like RegEditPE.

For clarity of the projects, the scripts are classified and displayed in Folders.
The folder appears Selected, when at least one child (script or subfolder) is selected, either unselected.
Toggling the selection of a folder toggles all selectable childs to the new selection state.

I added three menu items to the project tree context menu:

Status, Select, Unselect

Status shows a message box with information about the current treeview node, like

• Unselected Expanded Folder
• Mandatory Script
• Unselectable Script
• etc.

Depending on Script or Folder, Select and Unselect appear as

• Select this Script
• Unselect this Script

or

• Select this Folder
• Unselect this Folder

This addon to WinBuilder is made in version 83.0.0.15.
WinBuilder 83.0.0.15 is contained in multiPE 61.

From an installed multiPE project WinBuilder 83.0.0.15 can be downloaded by the the script multiPE >> Tools >> RestartWBEx

Peter

[eye0]

Hello, Peter! ;Thank you very much for your attention to us!
In conjunction "Winbuilder and NVDA" there are still many problems: for example, you can not include a toolbar button, such as "Play", "Options", "Download."
As a solution to propose to supply them with hotkeys.
For example, "Play" - CTRL + P, etc.
Alternatively, can ask the community to create a NVDA-support module for WinBuilder.
If I was looking into this question, I begin to write it.
Still, as an option, you can use Jaws, but not everyone has the money to buy this reader screen.
Sorry for my English - I write with a translator Google.
Thank you for your understanding! ;Good luck to you!

[Brito]

Hello eye0, welcome to reboot.

 

Your request is already fully taken into account on the new winbuilder generation. Please sign up at the following link for early access to test the NVDA support: http://reboot.pro/to...he-new-edition/

 

Now it is possible to control winbuilder with keyboard commands. For example, the play button to build a project can now be called when you type "build".

 

To select a Windows source, you can either type "source" to get a dialog asking to choose a folder or just type something like "source c:\sources\win7sp1" to specify a source without need for the dialog box.

 

The settings for each script on the new wb can be configured directly from a web browser without Javascript (plain HMTL) for easy access to read the page and apply your changes as needed.

 

And if these options are not enough, we will be working for everyone to easily use the builder.

 

[eye0]

Hallo, Nuno! Thanks for the information.

[pscEx]

@Nuno, @eye0!

 

Sorry, but I have to decrease your optimism a bit.

 

I tried WinBuilder with NVDA running.

The only item recognised by NVDA, was the caption in the GUI.

 

Inside the GUI NVDA did not "see" anything.

 

IMO in WinBuilder besides log and console output, a speech message as optional log is necessary.

 

Maybe the "Java Access Bridge" helps. But this runs only on Windows hosts.

 

Peter

[Brito]

Thanks for testing Peter.

 

IMO in WinBuilder besides log and console output, a speech message as optional log is necessary.

 

Yes, this is a solution to consider. NVDA is indeed exclusive to Windows hosts but this is a UI and no functionality of the builder will depend on it.

 

Since you're already testing, I don't see why we can't already start looking to into this matter.

 

 

I've tested the web UI and this is working more or less ok with NVDA. Good news is that the web page is read fine, bad news is that:

- The date part of the log takes a long time to be spoken and is redundant for this case. Can be omitted on the dedicated UI.

- The log places new lines of info at the bottom which is more intuitive to visual readers but more difficult to find with NVDA. Would probably make more sense to place lines on top rather than bottom on this case, making it easier to follow progress of the build.

 

 

How can we connect to NVDA to directly output log messages?

 

 

[eye0]

Hello friends!
To quickly view a log, you need to go to the menu NVDA/Tools/View Log.
HotKey - NVDAKey+n. Default, NVDAKey Equal Insert. If you are using a laptop, then Capslock.
In addition to general settings to enable a report to the developers.
The report file is written to the %Temp%\NVDA.log.
Perhaps this is partly to help: http://www.webbie.org.uk/nvda/ - I still poorly understand this.
Yet there is a program "SkypeTalking", she somehow takes the messages from Skype Api and directs them to a file nvdaControllerClient32.dll.
From this "DLL" message comes in NVDA. ;Skype window is not involved in this - everything happens through the Api.
Skype Talking Home Page is: http://skypetalking.googlecode.com/.
Sorry for my English.