Hi David,

I've just installed Visual Studio 2017, for which Microsoft has taken and is 
taking great pains to improve its accessibility.
The bulk of the code of my apps, and probably the same can be said for most 
Window-Eyes apps, is vbScript, and what else is this but a stripped-down 
version of Visual Basic.
Rick Thomas is a user of Visual Studio, and speaking with him on the phone a 
few times over the last year or so has encouraged me to see that it allows 
fairly easy development of Visual Basic programs with user interfaces that can 
be created quite easily, and certainly much easier than was possible in the 
past.
Further, the code can be compiled into stand-alone executables, and so they'll 
be accessible to any and all screen readers.
Here's an article from Cool Blind Tech about the improvements to the 
accessibility of Visual Studio with additional helpful links:

https://coolblindtech.com/microsoft-releases-visual-studio-2017-with-accessibility-improvements/

and here's the accessibility tips page they cite:

https://msdn.microsoft.com/en-us/library/bkxh4340.aspx?wt.mc_id=DX_879024

I installed Visual Studio just yesterday, and to get you going, I recommend 
going to Microsoft's Visual Studio installation page:

https://docs.microsoft.com/en-us/visualstudio/install/install-visual-studio

I had to go there myself because the current version of Visual Studio, which 
just came out last week, doesn't install any coding support whatsoever until 
you choose something from the installer, and I was scratching my head trying to 
figure out why I could not even create a simple dialog box with the 
corresponding code blocks, which used to be a basic feature of Visual Studio.

Anyway, off we go into a different world, with a new screen reader, and lots of 
work to do. (smile)

Let's keep in touch,

Rod

-----Original Message-----
From: Scripting 
[mailto:scripting-bounces+rod_hutton=hotmail....@lists.window-eyes.com] On 
Behalf Of David via Scripting
Sent: Monday, May 15, 2017 11:49 AM
To: Aaron Smith <ajsm...@vfogroup.com>; Window-Eyes Scripting List 
<scripting@lists.window-eyes.com>
Subject: migrating apps

I do understand that an app that has been developed under the great 
scripting capability of WineEyes, will not be possible to simply plug in 
under Jaws. At least, it is my understanding, that Jaws has its own 
dedicated scripting system.

Still, a number of apps, both officially released and many that I have 
developed for my personal usage, would be a great miss when migrating. 
Whenever the migrating will be. Smile.

Now, is there a way for me, to make my apps become stand-alone, in the 
sense that they could be run under any screen reader? That they still 
would be using features like the UI capabilities and other functionality 
of for instance GWToolkit? I do understand, that apps that make great 
usage of, or directly works with internal features of WinEyes, may not 
be possible to run under any other screen readers, since they won't have 
any functionality to hook on to. But an app like for instance the 
"remind me where", that Chip Orange developed, and which base its main 
functionality on information from the net, and greatly on the UI 
environment of WinEyes scripting, sould such a program be possible to 
make go general? Sure I could have thought of a good number of other 
apps that I have come to rely on, and which would have been great to see 
under other screen readers.

Guess my basic question is, what would I need to do in my app code, to 
make it possible to run outside the WinEyes environment, if that is at 
all possible? And if realistic, does there exist any sample code that I 
can look at, so as to see it done in practicality?

Thanks,

_______________________________________________
Any views or opinions presented in this email are solely those of the author 
and do not necessarily represent those of Ai Squared.

For membership options, visit 
http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/rod_hutton%40hotmail.com.
For subscription options, visit 
http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com
List archives can be found at 
http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com
_______________________________________________
Any views or opinions presented in this email are solely those of the author 
and do not necessarily represent those of Ai Squared.

For membership options, visit 
http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/archive%40mail-archive.com.
For subscription options, visit 
http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com
List archives can be found at 
http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com

Reply via email to