Date   

Re: Using NVDA to Create a Digital Signature in Word

Tony Ballou
 

Hi Dave,


I think you're thinking about something different here. This is for
using Microsoft word as the program for inserting the digital signature
rather than scanning it into a document. Although that is also a very
plausible way to get the same job done.


Tony

On 5/25/2017 7:38 PM, David Mehler wrote:
Hello,

Is this digital signature the same as scanning in a signature and
using that as a signature? Or am I thinking of something else?

'm needing a way to make documents legally binding.

Thanks.
Dave.


On 5/25/17, Tony Ballou <cyberpro224@outlook.com> wrote:
Hello David,


If my memory serves me correct, Using the doc format will work as long
as Microsoft word is installed The rtf format works on any windows based
system regardless. As for a digital signature here's how to do it.


Press alt+n for Insert, then g to open a signature menu. From here,
either a Microsoft Office Signature Line or "Add signature services" can
be selected. There are a number of services which can be subscribed to,
which allow digitally signing various types of documents (not only Word
documents). Many of these can be integrated into Word.
When a Microsoft Office signature line is added, a dialog opens allowing
you to include: the name, title and contact details of the signatory.
The document can be signed by selecting the signature line and choosing
"sign" from the context menu. In the dialog which appears, the focus is
on an edit field to type your name. There is also a link to select an
image of your actual signature instead. Personal details and also the
signing service to use can also be updated.
If no signing service is selected, the document can still be signed,
however, it will not be as secure or verifiable.


Hope this helps.


Tony



On 5/25/2017 2:52 PM, David Russell wrote:
Hello NVDA Group,

I am looking for a set of instructions -user-friendly for sightless
NVDA users that would tell someone how to set up a digital signature
in a document for others to add their signature and date, then return
by email attachment. It is for a Publisher Agreement.

I also wonder would it be best to send this as a doc file or RTF since
not everyone can use PDF?
Thanks in advance. I need an answer within a few hours.



Re: Using NVDA to Create a Digital Signature in Word

Tony Ballou
 

Hi Dave,


I think you're thinking about something different here. This is for
using Microsoft word as the program for inserting the digital signature
rather than scanning it into a document. Although that is also a very
plausible way to get the same job done.


Tony

On 5/25/2017 7:38 PM, David Mehler wrote:
Hello,

Is this digital signature the same as scanning in a signature and
using that as a signature? Or am I thinking of something else?

'm needing a way to make documents legally binding.

Thanks.
Dave.


On 5/25/17, Tony Ballou <cyberpro224@outlook.com> wrote:
Hello David,


If my memory serves me correct, Using the doc format will work as long
as Microsoft word is installed The rtf format works on any windows based
system regardless. As for a digital signature here's how to do it.


Press alt+n for Insert, then g to open a signature menu. From here,
either a Microsoft Office Signature Line or "Add signature services" can
be selected. There are a number of services which can be subscribed to,
which allow digitally signing various types of documents (not only Word
documents). Many of these can be integrated into Word.
When a Microsoft Office signature line is added, a dialog opens allowing
you to include: the name, title and contact details of the signatory.
The document can be signed by selecting the signature line and choosing
"sign" from the context menu. In the dialog which appears, the focus is
on an edit field to type your name. There is also a link to select an
image of your actual signature instead. Personal details and also the
signing service to use can also be updated.
If no signing service is selected, the document can still be signed,
however, it will not be as secure or verifiable.


Hope this helps.


Tony



On 5/25/2017 2:52 PM, David Russell wrote:
Hello NVDA Group,

I am looking for a set of instructions -user-friendly for sightless
NVDA users that would tell someone how to set up a digital signature
in a document for others to add their signature and date, then return
by email attachment. It is for a Publisher Agreement.

I also wonder would it be best to send this as a doc file or RTF since
not everyone can use PDF?
Thanks in advance. I need an answer within a few hours.



Re: a more r less finished draft of my transition guide from Window-eyes

Gene
 

That's fine but it's not completely in its final form yet. 
 
Gene

----- Original Message -----
From: Joseph Lee
Sent: Thursday, May 25, 2017 6:41 PM
Subject: Re: [nvda] a more r less finished draft of my transition guide from Window-eyes

Hi,

I’ll wikify it and publish it on the NVDA community wiki page (with your permission of course).

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Tony Ballou
Sent: Thursday, May 25, 2017 4:39 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] a more r less finished draft of my transition guide from Window-eyes

 

Hey Gene,

 

You just have to put the website URL in there from what I can see, otherwise, all's gravy.

 

Tony

 

On 5/25/2017 6:59 PM, Gene wrote:

Thanks.

 

Gene

----- original Message -----

From: Tony Ballou

Sent: Thursday, May 25, 2017 5:16 PM

Subject: Re: [nvda] a more r less finished draft of my transition guide from Window-eyes

 

Hey Gene,

 

This is really working brother I like it! 


Tony

On 5/25/2017 5:52 PM, Gene wrote:

Here is my mostly finished draft of a transition guide for users of Window-eyes.  Comments and suggestions are welcome.  I'll send it to the list in its final form for distribution by whomever wants to do so.

 

the brief tutorial begins below my signature.

Gene

 

Moving from Window-eyes to NVDA
A very short tutorial telling you just what you need to know to do a lot of what

 

you did before.

 

Many people are apprehensive about switching to NVDA or any other screen-reader

 

from Window-eyes.  This tutorial will explain and demonstrate that such

 

apprehensions are largely based on misunderstandings. 

 

Before I discuss the misunderstanding that causes most of this apprehension, I'll

 

briefly discuss installing NVDA and changing the synthesizer used and speech

 

parameters.

 

NVDA has a talking installer.  run the file as you would any installation file. 

 

you may get a dialog asking if you want to run the file.  Use the command alt r

 

for run.  If you get a UAC prompt, answer alt y. 
Run narrator.  Then run the NVDA installer. 
when you run the installer, there will be a pause and then a bit of music will

 

play.  Not long after, the talking installer will run.  Unload Narrator at that

 

point.  return to the install dialog.
Tab through the dchoices.  Accept the license agreement and then tab to install. 

 

You will get other options but install is the one you want.
Don't stop using NvDA because of the voice.  A lot of people don't try NVDA because

 

of the voice.  As soon as you get it set up, I'll tell you how to change the

 

synthesizer used.

 

After NVDA is installed and running, it's time to learn how to change the

 

synthesizer. 
Issue the command control insert s.  Use either insert.  From now on, assume you

 

can use either insert unless I state differently.
A synthesizer selection dialog will open.
You will see a list of different possibly available synthesizers.  Choose SAPI 5. 

 

I know everyone has at least one SAPI 5 voice on their machine.  Up and down arrow

 

through the list and stop on SAPI five.  Press enter.
You will now hear another voice.  It may be the same voice you hear in Narrator. 
Now issue the command control insert v.
You are now in the voice selection and adjustment dialog. 
Up and down arrow to see what voices are available.  Stop on the one you want. 
Now tab through the dialog and change settings for the voice. 
Once you find a voice you want and tab through and set whatever you want such as

 

speed and punctuation, press the ok button. 

 

Now, let's continue with what I spoke of at the start of this tutorial.  The

 

misunderstanding that makes the switch seem daunting is that the user doesn't

 

realize that most of the commands he/she uses are Windows commands and program

 

commands and they won't change.

 

Consider the following examples:
Opening menus was and still is alt.  That's a Windows command to open menus in

 

programs.  It's the same no matter which screen-reader you use. 
Control o for open doesn't change.  Using the arrow keys to move in a document

 

doesn't change.  Tabbing through dialogs doesn't change.  Neither does how you move

 

in a list or a treeview or work with a combo box, and the list goes on. 
Screen-reader commands, many of which may change, such as read title bar, provide

 

access to information you can't get or can't get conveniently by using Windows or

 

program commands.  for example, read title bar.  In Window-eyes, the command is

 

control shift t.  In NVDA, it's insert t.  I am assuming throughout this tutorial

 

that you are using the default desktop layout in NVDA.  All commands are given in

 

that layout.  The title bar is something a sighted person looks at.  You can't move

 

to it with the pc cursor or application cursor, whatever you wish to call it,

 

because there is no need.  A sighted person can just see it.  So the screen-reader

 

has a command, read title bar.  That command is not a Windows nor a program

 

command.

 

Here are the screen-reader commands you will need to know to allow you to do a lot

 

of what you did before.
Read title bar, insert t. 
Time, insert f12. 
Read current Window, insert b.  In Window-eyes the command is control shift w. 
Read to end, insert down arrow.  Use the down arrow on the main keyboard.
Stop speech with control, as with screen-readers in general. 
Commands such as control home, control end, control left and right arrow are

 

Windows movement commands for moving in any standard edit field including word

 

processor edit fields.  None of them will change.
More screen-reader commands:
Screen review commands:
Note the pattern as I give these commands:
Read previous line, numpad 7. 
Read current line, numpad 8.
Read next line numpad nine.
You move in screen review to the previous or next line when you issue those

 

commands.  You can keep moving and reading until you get to the top or bottom of

 

the screen.
Read previous word, numpad 4.
Read current word, numpad 5.
Read next word, numpad 6.
Read previous character, numpad 1.
Read current character, numpad 2.
Read next character, numpad 3.
Note the pattern.  Read current is the key in the middle of each of these rows.
Move to and read previous is the key on the left. 
Move to and read next is the key to the right.
The lower the numbers the smaller the movement unit.  1 2 and 3 move by character. 

 

4 5 and 6 move by word.  Etc.
Here are two more important commands:
Jump to top of window, shift numpad 7.
Jump to bottom of window is shift numpad 9.

 

I've said top and bottom of Window but that's oversimplified.  It depends what kind

 

of review mode you are using.  I won't go into that to any extent in this very

 

short tutorial. 
that is the one you should be in usually.  Unless you change it, you will remain

 

there.  If you use another review mode, afterword, make sure you return to object

 

reviewIf you don't, you won't hear what you expect to hear at various times. 
To make sure you are in object review, issue the command numpad insert nummpad 1. 

 

When you are already in object review and can't move to another review mode, you

 

will hear no previous review mode.  You will then know you are in the right one. 

 

Or if you are returning from another review mode, when you hear object review, you

 

will know you are back in the right one.
I won't describe its use here, but screen review is similar not in commands, but in

 

how you review the screen to the Window-eyes cursor.  Object review is different

 

from any review mode available in Window-eyes.  It is valuable to know for various

 

uses.  Depending on how you use your computer, you may find it valuable or not.  I'm

 

simply making you aware that it is different and that you may want to learn it.

 

I'll provide a resource that teaches in great detail how to use NVDA.
This tutorial is to get you going using NVDA and to show you that even with the

 

little I will teach, you can still do a good deal of what you used to do.  You may

 

then learn more as you wish.

 

Believe it or not, that is just about all I will teach in this very short tutorial

 

but  I'll tell you a few more things.
Internet browsing:
When you are on a web page, quick navigation commands are almost identical whether

 

you are using NVDA or Window-eyes. 
Move by headings is h.  Skip blocks of links is n. 
Move to next button is b, 
Next combo box is c.
Next check box is x.
NVDA has an input help mode which is similar to what is in Window-eyes.  Insert and

 

1 on the main keyboard turns it on.  When you press a key or combination of keys

 

that might be a command, you will hear what the keys are and what, if any command

 

they execute.  This varies cdepending on where you are.
When in a browser that supports browse mode, typing a lot of individual letters

 

will give you information about what the keys do in browse mode.  I already gave

 

much of that information above but you may want to press a lot of keys using input

 

mode in a browser. 

 

To turn input mode off use the same command you used to turn it on, insert 1.

 

to learn more about NVDA, a popular tutorial is available at (insert URL.) 
On that page, you will see links to download different sections dealing with

 

different subjects.  You can also download the entire tutorial as a zip file.

 

There is also an e-mail list for NVDA users.  To join, send a blank message to this

 

 

I hope that this tutorial has removed much of your apprehension about switching to

 

NVDA.  Now, as you wish or need, you may consult the tutorial I gave a link to. 

 

NVDA is a powerful screen-reader and it will meet a lot of users needs as well as

 

JAWS or Window-eyes does.  I hope this very short tutorial gives you a good

 

foundation on which to build confidence that the transition should be much easier

 

than you may have thought and that it will help make it much more enjoyable.

 

 


Re: a more r less finished draft of my transition guide from Window-eyes

Gene
 

I'm not sure I have the current address.  If I don't, I'll ask Joseph lee about it.
 
Gene

----- Original Message -----
Sent: Thursday, May 25, 2017 6:39 PM
Subject: Re: [nvda] a more r less finished draft of my transition guide from Window-eyes

Hey Gene,


You just have to put the website URL in there from what I can see, otherwise, all's gravy.


Tony


On 5/25/2017 6:59 PM, Gene wrote:
Thanks.
 
Gene
----- original Message -----
Sent: Thursday, May 25, 2017 5:16 PM
Subject: Re: [nvda] a more r less finished draft of my transition guide from Window-eyes

Hey Gene,


This is really working brother I like it! 


Tony
On 5/25/2017 5:52 PM, Gene wrote:
Here is my mostly finished draft of a transition guide for users of Window-eyes.  Comments and suggestions are welcome.  I'll send it to the list in its final form for distribution by whomever wants to do so.
 
the brief tutorial begins below my signature.
Gene
 
Moving from Window-eyes to NVDA
A very short tutorial telling you just what you need to know to do a lot of what
 
you did before.
 
Many people are apprehensive about switching to NVDA or any other screen-reader
 
from Window-eyes.  This tutorial will explain and demonstrate that such
 
apprehensions are largely based on misunderstandings. 
 
Before I discuss the misunderstanding that causes most of this apprehension, I'll
 
briefly discuss installing NVDA and changing the synthesizer used and speech
 
parameters.
 
NVDA has a talking installer.  run the file as you would any installation file. 
 
you may get a dialog asking if you want to run the file.  Use the command alt r
 
for run.  If you get a UAC prompt, answer alt y. 
Run narrator.  Then run the NVDA installer. 
when you run the installer, there will be a pause and then a bit of music will
 
play.  Not long after, the talking installer will run.  Unload Narrator at that
 
point.  return to the install dialog.
Tab through the dchoices.  Accept the license agreement and then tab to install. 
 
You will get other options but install is the one you want.
Don't stop using NvDA because of the voice.  A lot of people don't try NVDA because
 
of the voice.  As soon as you get it set up, I'll tell you how to change the
 
synthesizer used.
 
After NVDA is installed and running, it's time to learn how to change the
 
synthesizer. 
Issue the command control insert s.  Use either insert.  From now on, assume you
 
can use either insert unless I state differently.
A synthesizer selection dialog will open.
You will see a list of different possibly available synthesizers.  Choose SAPI 5. 
 
I know everyone has at least one SAPI 5 voice on their machine.  Up and down arrow
 
through the list and stop on SAPI five.  Press enter.
You will now hear another voice.  It may be the same voice you hear in Narrator. 
Now issue the command control insert v.
You are now in the voice selection and adjustment dialog. 
Up and down arrow to see what voices are available.  Stop on the one you want. 
Now tab through the dialog and change settings for the voice. 
Once you find a voice you want and tab through and set whatever you want such as
 
speed and punctuation, press the ok button. 
 
Now, let's continue with what I spoke of at the start of this tutorial.  The
 
misunderstanding that makes the switch seem daunting is that the user doesn't
 
realize that most of the commands he/she uses are Windows commands and program
 
commands and they won't change.
 
Consider the following examples:
Opening menus was and still is alt.  That's a Windows command to open menus in
 
programs.  It's the same no matter which screen-reader you use. 
Control o for open doesn't change.  Using the arrow keys to move in a document
 
doesn't change.  Tabbing through dialogs doesn't change.  Neither does how you move
 
in a list or a treeview or work with a combo box, and the list goes on. 
Screen-reader commands, many of which may change, such as read title bar, provide
 
access to information you can't get or can't get conveniently by using Windows or
 
program commands.  for example, read title bar.  In Window-eyes, the command is
 
control shift t.  In NVDA, it's insert t.  I am assuming throughout this tutorial
 
that you are using the default desktop layout in NVDA.  All commands are given in
 
that layout.  The title bar is something a sighted person looks at.  You can't move
 
to it with the pc cursor or application cursor, whatever you wish to call it,
 
because there is no need.  A sighted person can just see it.  So the screen-reader
 
has a command, read title bar.  That command is not a Windows nor a program
 
command.
 
Here are the screen-reader commands you will need to know to allow you to do a lot
 
of what you did before.
Read title bar, insert t. 
Time, insert f12. 
Read current Window, insert b.  In Window-eyes the command is control shift w. 
Read to end, insert down arrow.  Use the down arrow on the main keyboard.
Stop speech with control, as with screen-readers in general. 
Commands such as control home, control end, control left and right arrow are
 
Windows movement commands for moving in any standard edit field including word
 
processor edit fields.  None of them will change.
More screen-reader commands:
Screen review commands:
Note the pattern as I give these commands:
Read previous line, numpad 7. 
Read current line, numpad 8.
Read next line numpad nine.
You move in screen review to the previous or next line when you issue those
 
commands.  You can keep moving and reading until you get to the top or bottom of
 
the screen.
Read previous word, numpad 4.
Read current word, numpad 5.
Read next word, numpad 6.
Read previous character, numpad 1.
Read current character, numpad 2.
Read next character, numpad 3.
Note the pattern.  Read current is the key in the middle of each of these rows.
Move to and read previous is the key on the left. 
Move to and read next is the key to the right.
The lower the numbers the smaller the movement unit.  1 2 and 3 move by character. 
 
4 5 and 6 move by word.  Etc.
Here are two more important commands:
Jump to top of window, shift numpad 7.
Jump to bottom of window is shift numpad 9.
 
I've said top and bottom of Window but that's oversimplified.  It depends what kind
 
of review mode you are using.  I won't go into that to any extent in this very
 
short tutorial. 
that is the one you should be in usually.  Unless you change it, you will remain
 
there.  If you use another review mode, afterword, make sure you return to object
 
reviewIf you don't, you won't hear what you expect to hear at various times. 
To make sure you are in object review, issue the command numpad insert nummpad 1. 
 
When you are already in object review and can't move to another review mode, you
 
will hear no previous review mode.  You will then know you are in the right one. 
 
Or if you are returning from another review mode, when you hear object review, you
 
will know you are back in the right one.
I won't describe its use here, but screen review is similar not in commands, but in
 
how you review the screen to the Window-eyes cursor.  Object review is different
 
from any review mode available in Window-eyes.  It is valuable to know for various
 
uses.  Depending on how you use your computer, you may find it valuable or not.  I'm
 
simply making you aware that it is different and that you may want to learn it.
 
I'll provide a resource that teaches in great detail how to use NVDA.
This tutorial is to get you going using NVDA and to show you that even with the
 
little I will teach, you can still do a good deal of what you used to do.  You may
 
then learn more as you wish.
 
Believe it or not, that is just about all I will teach in this very short tutorial
 
but  I'll tell you a few more things.
Internet browsing:
When you are on a web page, quick navigation commands are almost identical whether
 
you are using NVDA or Window-eyes. 
Move by headings is h.  Skip blocks of links is n. 
Move to next button is b, 
Next combo box is c.
Next check box is x.
NVDA has an input help mode which is similar to what is in Window-eyes.  Insert and
 
1 on the main keyboard turns it on.  When you press a key or combination of keys
 
that might be a command, you will hear what the keys are and what, if any command
 
they execute.  This varies cdepending on where you are.
When in a browser that supports browse mode, typing a lot of individual letters
 
will give you information about what the keys do in browse mode.  I already gave
 
much of that information above but you may want to press a lot of keys using input
 
mode in a browser. 
 
To turn input mode off use the same command you used to turn it on, insert 1.
 
to learn more about NVDA, a popular tutorial is available at (insert URL.) 
On that page, you will see links to download different sections dealing with
 
different subjects.  You can also download the entire tutorial as a zip file.
 
There is also an e-mail list for NVDA users.  To join, send a blank message to this
 
 
I hope that this tutorial has removed much of your apprehension about switching to
 
NVDA.  Now, as you wish or need, you may consult the tutorial I gave a link to. 
 
NVDA is a powerful screen-reader and it will meet a lot of users needs as well as
 
JAWS or Window-eyes does.  I hope this very short tutorial gives you a good
 
foundation on which to build confidence that the transition should be much easier
 
than you may have thought and that it will help make it much more enjoyable.



Re: a more r less finished draft of my transition guide from Window-eyes

Gene
 

Because if you run the installer with no screen-reader active, you may receive a message and not know it.  If you don't respond properly to the message, the installation won't begin.  No matter what screen-reader you install, you should have something running before you run the installer. 
 
I'll have to think about whether I want to include the laptop layout and information about how to switch to it.  I may do so or I may tell people how to find the quick keyboard commands reference in the documentation.
 
Gene

----- Original Message -----
Sent: Thursday, May 25, 2017 6:26 PM
Subject: Re: [nvda] a more r less finished draft of my transition guide from Window-eyes

Hello Gene,

I just read your tutorial draft. I have a thanks, a question, and a comment.

The thanks, thanks for the information on the switching synth method and sapi5.

The question, you mentioned that your using desktop mode. Can you
extend the tutorial to include the laptop keystrokes for those
transitioning from a laptop.

And the comment, during the install you load narrator then a little
later unload it. Why is this?

Thanks.
Dave.


On 5/25/17, Gene <gsasner@...> wrote:
> Thanks.
>
> Gene
> ----- original Message -----
>
> From: Tony Ballou
> Sent: Thursday, May 25, 2017 5:16 PM
> To: nvda@nvda.groups.io
> Subject: Re: [nvda] a more r less finished draft of my transition guide from
> Window-eyes
>
>
> Hey Gene,
>
>
>
>
> This is really working brother I like it!
>
>
>
> Tony
>
> On 5/25/2017 5:52 PM, Gene wrote:
>
>   Here is my mostly finished draft of a transition guide for users of
> Window-eyes.  Comments and suggestions are welcome.  I'll send it to the
> list in its final form for distribution by whomever wants to do so.
>
>   the brief tutorial begins below my signature.
>   Gene
>
>   Moving from Window-eyes to NVDA
>   A very short tutorial telling you just what you need to know to do a lot
> of what
>
>   you did before.
>
>   Many people are apprehensive about switching to NVDA or any other
> screen-reader
>
>   from Window-eyes.  This tutorial will explain and demonstrate that such
>
>   apprehensions are largely based on misunderstandings.
>
>   Before I discuss the misunderstanding that causes most of this
> apprehension, I'll
>
>   briefly discuss installing NVDA and changing the synthesizer used and
> speech
>
>   parameters.
>
>   NVDA has a talking installer.  run the file as you would any installation
> file.
>
>   you may get a dialog asking if you want to run the file.  Use the command
> alt r
>
>   for run.  If you get a UAC prompt, answer alt y.
>   Run narrator.  Then run the NVDA installer.
>   when you run the installer, there will be a pause and then a bit of music
> will
>
>   play.  Not long after, the talking installer will run.  Unload Narrator at
> that
>
>   point.  return to the install dialog.
>   Tab through the dchoices.  Accept the license agreement and then tab to
> install.
>
>   You will get other options but install is the one you want.
>   Don't stop using NvDA because of the voice.  A lot of people don't try
> NVDA because
>
>   of the voice.  As soon as you get it set up, I'll tell you how to change
> the
>
>   synthesizer used.
>
>   After NVDA is installed and running, it's time to learn how to change the
>
>
>   synthesizer.
>   Issue the command control insert s.  Use either insert.  From now on,
> assume you
>
>   can use either insert unless I state differently.
>   A synthesizer selection dialog will open.
>   You will see a list of different possibly available synthesizers.  Choose
> SAPI 5.
>
>   I know everyone has at least one SAPI 5 voice on their machine.  Up and
> down arrow
>
>   through the list and stop on SAPI five.  Press enter.
>   You will now hear another voice.  It may be the same voice you hear in
> Narrator.
>   Now issue the command control insert v.
>   You are now in the voice selection and adjustment dialog.
>   Up and down arrow to see what voices are available.  Stop on the one you
> want.
>   Now tab through the dialog and change settings for the voice.
>   Once you find a voice you want and tab through and set whatever you want
> such as
>
>   speed and punctuation, press the ok button.
>
>   Now, let's continue with what I spoke of at the start of this tutorial.
> The
>
>   misunderstanding that makes the switch seem daunting is that the user
> doesn't
>
>   realize that most of the commands he/she uses are Windows commands and
> program
>
>   commands and they won't change.
>
>   Consider the following examples:
>   Opening menus was and still is alt.  That's a Windows command to open
> menus in
>
>   programs.  It's the same no matter which screen-reader you use.
>   Control o for open doesn't change.  Using the arrow keys to move in a
> document
>
>   doesn't change.  Tabbing through dialogs doesn't change.  Neither does how
> you move
>
>   in a list or a treeview or work with a combo box, and the list goes on.
>   Screen-reader commands, many of which may change, such as read title bar,
> provide
>
>   access to information you can't get or can't get conveniently by using
> Windows or
>
>   program commands.  for example, read title bar.  In Window-eyes, the
> command is
>
>   control shift t.  In NVDA, it's insert t.  I am assuming throughout this
> tutorial
>
>   that you are using the default desktop layout in NVDA.  All commands are
> given in
>
>   that layout.  The title bar is something a sighted person looks at.  You
> can't move
>
>   to it with the pc cursor or application cursor, whatever you wish to call
> it,
>
>   because there is no need.  A sighted person can just see it.  So the
> screen-reader
>
>   has a command, read title bar.  That command is not a Windows nor a
> program
>
>   command.
>
>   Here are the screen-reader commands you will need to know to allow you to
> do a lot
>
>   of what you did before.
>   Read title bar, insert t.
>   Time, insert f12.
>   Read current Window, insert b.  In Window-eyes the command is control
> shift w.
>   Read to end, insert down arrow.  Use the down arrow on the main keyboard.
>   Stop speech with control, as with screen-readers in general.
>   Commands such as control home, control end, control left and right arrow
> are
>
>   Windows movement commands for moving in any standard edit field including
> word
>
>   processor edit fields.  None of them will change.
>   More screen-reader commands:
>   Screen review commands:
>   Note the pattern as I give these commands:
>   Read previous line, numpad 7.
>   Read current line, numpad 8.
>   Read next line numpad nine.
>   You move in screen review to the previous or next line when you issue
> those
>
>   commands.  You can keep moving and reading until you get to the top or
> bottom of
>
>   the screen.
>   Read previous word, numpad 4.
>   Read current word, numpad 5.
>   Read next word, numpad 6.
>   Read previous character, numpad 1.
>   Read current character, numpad 2.
>   Read next character, numpad 3.
>   Note the pattern.  Read current is the key in the middle of each of these
> rows.
>   Move to and read previous is the key on the left.
>   Move to and read next is the key to the right.
>   The lower the numbers the smaller the movement unit.  1 2 and 3 move by
> character.
>
>   4 5 and 6 move by word.  Etc.
>   Here are two more important commands:
>   Jump to top of window, shift numpad 7.
>   Jump to bottom of window is shift numpad 9.
>
>   I've said top and bottom of Window but that's oversimplified.  It depends
> what kind
>
>   of review mode you are using.  I won't go into that to any extent in this
> very
>
>   short tutorial.
>   that is the one you should be in usually.  Unless you change it, you will
> remain
>
>   there.  If you use another review mode, afterword, make sure you return to
> object
>
>   reviewIf you don't, you won't hear what you expect to hear at various
> times.
>   To make sure you are in object review, issue the command numpad insert
> nummpad 1.
>
>   When you are already in object review and can't move to another review
> mode, you
>
>   will hear no previous review mode.  You will then know you are in the
> right one.
>
>   Or if you are returning from another review mode, when you hear object
> review, you
>
>   will know you are back in the right one.
>   I won't describe its use here, but screen review is similar not in
> commands, but in
>
>   how you review the screen to the Window-eyes cursor.  Object review is
> different
>
>   from any review mode available in Window-eyes.  It is valuable to know for
> various
>
>   uses.  Depending on how you use your computer, you may find it valuable or
> not.  I'm
>
>   simply making you aware that it is different and that you may want to
> learn it.
>
>   I'll provide a resource that teaches in great detail how to use NVDA.
>   This tutorial is to get you going using NVDA and to show you that even
> with the
>
>   little I will teach, you can still do a good deal of what you used to do.
> You may
>
>   then learn more as you wish.
>
>   Believe it or not, that is just about all I will teach in this very short
> tutorial
>
>   but  I'll tell you a few more things.
>   Internet browsing:
>   When you are on a web page, quick navigation commands are almost identical
> whether
>
>   you are using NVDA or Window-eyes.
>   Move by headings is h.  Skip blocks of links is n.
>   Move to next button is b,
>   Next combo box is c.
>   Next check box is x.
>   NVDA has an input help mode which is similar to what is in Window-eyes.
> Insert and
>
>   1 on the main keyboard turns it on.  When you press a key or combination
> of keys
>
>   that might be a command, you will hear what the keys are and what, if any
> command
>
>   they execute.  This varies cdepending on where you are.
>   When in a browser that supports browse mode, typing a lot of individual
> letters
>
>   will give you information about what the keys do in browse mode.  I
> already gave
>
>   much of that information above but you may want to press a lot of keys
> using input
>
>   mode in a browser.
>
>   To turn input mode off use the same command you used to turn it on, insert
> 1.
>
>   to learn more about NVDA, a popular tutorial is available at (insert URL.)
>
>   On that page, you will see links to download different sections dealing
> with
>
>   different subjects.  You can also download the entire tutorial as a zip
> file.
>
>   There is also an e-mail list for NVDA users.  To join, send a blank
> message to this
>
>   address:
>   nvda+subscribe@nvda.groups.io
>
>   I hope that this tutorial has removed much of your apprehension about
> switching to
>
>   NVDA.  Now, as you wish or need, you may consult the tutorial I gave a
> link to.
>
>   NVDA is a powerful screen-reader and it will meet a lot of users needs as
> well as
>
>   JAWS or Window-eyes does.  I hope this very short tutorial gives you a
> good
>
>   foundation on which to build confidence that the transition should be much
> easier
>
>   than you may have thought and that it will help make it much more
> enjoyable.
>
>
>
>



Re: a more r less finished draft of my transition guide from Window-eyes

Tony Ballou
 

Hi David,


The reason why you'll want to unload narrator after NVDA starts talking
is to avoid the double speak that occurs between the 2 synthesizers.
That tends to be quite a royal pain.


Tony

On 5/25/2017 7:26 PM, David Mehler wrote:
Hello Gene,

I just read your tutorial draft. I have a thanks, a question, and a comment.

The thanks, thanks for the information on the switching synth method and sapi5.

The question, you mentioned that your using desktop mode. Can you
extend the tutorial to include the laptop keystrokes for those
transitioning from a laptop.

And the comment, during the install you load narrator then a little
later unload it. Why is this?

Thanks.
Dave.


On 5/25/17, Gene <gsasner@ripco.com> wrote:
Thanks.

Gene
----- original Message -----

From: Tony Ballou
Sent: Thursday, May 25, 2017 5:16 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] a more r less finished draft of my transition guide from
Window-eyes


Hey Gene,




This is really working brother I like it!



Tony

On 5/25/2017 5:52 PM, Gene wrote:

Here is my mostly finished draft of a transition guide for users of
Window-eyes. Comments and suggestions are welcome. I'll send it to the
list in its final form for distribution by whomever wants to do so.

the brief tutorial begins below my signature.
Gene

Moving from Window-eyes to NVDA
A very short tutorial telling you just what you need to know to do a lot
of what

you did before.

Many people are apprehensive about switching to NVDA or any other
screen-reader

from Window-eyes. This tutorial will explain and demonstrate that such

apprehensions are largely based on misunderstandings.

Before I discuss the misunderstanding that causes most of this
apprehension, I'll

briefly discuss installing NVDA and changing the synthesizer used and
speech

parameters.

NVDA has a talking installer. run the file as you would any installation
file.

you may get a dialog asking if you want to run the file. Use the command
alt r

for run. If you get a UAC prompt, answer alt y.
Run narrator. Then run the NVDA installer.
when you run the installer, there will be a pause and then a bit of music
will

play. Not long after, the talking installer will run. Unload Narrator at
that

point. return to the install dialog.
Tab through the dchoices. Accept the license agreement and then tab to
install.

You will get other options but install is the one you want.
Don't stop using NvDA because of the voice. A lot of people don't try
NVDA because

of the voice. As soon as you get it set up, I'll tell you how to change
the

synthesizer used.

After NVDA is installed and running, it's time to learn how to change the


synthesizer.
Issue the command control insert s. Use either insert. From now on,
assume you

can use either insert unless I state differently.
A synthesizer selection dialog will open.
You will see a list of different possibly available synthesizers. Choose
SAPI 5.

I know everyone has at least one SAPI 5 voice on their machine. Up and
down arrow

through the list and stop on SAPI five. Press enter.
You will now hear another voice. It may be the same voice you hear in
Narrator.
Now issue the command control insert v.
You are now in the voice selection and adjustment dialog.
Up and down arrow to see what voices are available. Stop on the one you
want.
Now tab through the dialog and change settings for the voice.
Once you find a voice you want and tab through and set whatever you want
such as

speed and punctuation, press the ok button.

Now, let's continue with what I spoke of at the start of this tutorial.
The

misunderstanding that makes the switch seem daunting is that the user
doesn't

realize that most of the commands he/she uses are Windows commands and
program

commands and they won't change.

Consider the following examples:
Opening menus was and still is alt. That's a Windows command to open
menus in

programs. It's the same no matter which screen-reader you use.
Control o for open doesn't change. Using the arrow keys to move in a
document

doesn't change. Tabbing through dialogs doesn't change. Neither does how
you move

in a list or a treeview or work with a combo box, and the list goes on.
Screen-reader commands, many of which may change, such as read title bar,
provide

access to information you can't get or can't get conveniently by using
Windows or

program commands. for example, read title bar. In Window-eyes, the
command is

control shift t. In NVDA, it's insert t. I am assuming throughout this
tutorial

that you are using the default desktop layout in NVDA. All commands are
given in

that layout. The title bar is something a sighted person looks at. You
can't move

to it with the pc cursor or application cursor, whatever you wish to call
it,

because there is no need. A sighted person can just see it. So the
screen-reader

has a command, read title bar. That command is not a Windows nor a
program

command.

Here are the screen-reader commands you will need to know to allow you to
do a lot

of what you did before.
Read title bar, insert t.
Time, insert f12.
Read current Window, insert b. In Window-eyes the command is control
shift w.
Read to end, insert down arrow. Use the down arrow on the main keyboard.
Stop speech with control, as with screen-readers in general.
Commands such as control home, control end, control left and right arrow
are

Windows movement commands for moving in any standard edit field including
word

processor edit fields. None of them will change.
More screen-reader commands:
Screen review commands:
Note the pattern as I give these commands:
Read previous line, numpad 7.
Read current line, numpad 8.
Read next line numpad nine.
You move in screen review to the previous or next line when you issue
those

commands. You can keep moving and reading until you get to the top or
bottom of

the screen.
Read previous word, numpad 4.
Read current word, numpad 5.
Read next word, numpad 6.
Read previous character, numpad 1.
Read current character, numpad 2.
Read next character, numpad 3.
Note the pattern. Read current is the key in the middle of each of these
rows.
Move to and read previous is the key on the left.
Move to and read next is the key to the right.
The lower the numbers the smaller the movement unit. 1 2 and 3 move by
character.

4 5 and 6 move by word. Etc.
Here are two more important commands:
Jump to top of window, shift numpad 7.
Jump to bottom of window is shift numpad 9.

I've said top and bottom of Window but that's oversimplified. It depends
what kind

of review mode you are using. I won't go into that to any extent in this
very

short tutorial.
that is the one you should be in usually. Unless you change it, you will
remain

there. If you use another review mode, afterword, make sure you return to
object

reviewIf you don't, you won't hear what you expect to hear at various
times.
To make sure you are in object review, issue the command numpad insert
nummpad 1.

When you are already in object review and can't move to another review
mode, you

will hear no previous review mode. You will then know you are in the
right one.

Or if you are returning from another review mode, when you hear object
review, you

will know you are back in the right one.
I won't describe its use here, but screen review is similar not in
commands, but in

how you review the screen to the Window-eyes cursor. Object review is
different

from any review mode available in Window-eyes. It is valuable to know for
various

uses. Depending on how you use your computer, you may find it valuable or
not. I'm

simply making you aware that it is different and that you may want to
learn it.

I'll provide a resource that teaches in great detail how to use NVDA.
This tutorial is to get you going using NVDA and to show you that even
with the

little I will teach, you can still do a good deal of what you used to do.
You may

then learn more as you wish.

Believe it or not, that is just about all I will teach in this very short
tutorial

but I'll tell you a few more things.
Internet browsing:
When you are on a web page, quick navigation commands are almost identical
whether

you are using NVDA or Window-eyes.
Move by headings is h. Skip blocks of links is n.
Move to next button is b,
Next combo box is c.
Next check box is x.
NVDA has an input help mode which is similar to what is in Window-eyes.
Insert and

1 on the main keyboard turns it on. When you press a key or combination
of keys

that might be a command, you will hear what the keys are and what, if any
command

they execute. This varies cdepending on where you are.
When in a browser that supports browse mode, typing a lot of individual
letters

will give you information about what the keys do in browse mode. I
already gave

much of that information above but you may want to press a lot of keys
using input

mode in a browser.

To turn input mode off use the same command you used to turn it on, insert
1.

to learn more about NVDA, a popular tutorial is available at (insert URL.)

On that page, you will see links to download different sections dealing
with

different subjects. You can also download the entire tutorial as a zip
file.

There is also an e-mail list for NVDA users. To join, send a blank
message to this

address:
nvda+subscribe@nvda.groups.io

I hope that this tutorial has removed much of your apprehension about
switching to

NVDA. Now, as you wish or need, you may consult the tutorial I gave a
link to.

NVDA is a powerful screen-reader and it will meet a lot of users needs as
well as

JAWS or Window-eyes does. I hope this very short tutorial gives you a
good

foundation on which to build confidence that the transition should be much
easier

than you may have thought and that it will help make it much more
enjoyable.




Re: a more r less finished draft of my transition guide from Window-eyes

Tony Ballou
 

Hi David,


I think Gene and I will more than likely do that. At least I'm giving it
very good odds


Tony

On 5/25/2017 7:26 PM, David Mehler wrote:

Hello Gene,

I just read your tutorial draft. I have a thanks, a question, and a comment.

The thanks, thanks for the information on the switching synth method and sapi5.

The question, you mentioned that your using desktop mode. Can you
extend the tutorial to include the laptop keystrokes for those
transitioning from a laptop.

And the comment, during the install you load narrator then a little
later unload it. Why is this?

Thanks.
Dave.


On 5/25/17, Gene <gsasner@ripco.com> wrote:
Thanks.

Gene
----- original Message -----

From: Tony Ballou
Sent: Thursday, May 25, 2017 5:16 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] a more r less finished draft of my transition guide from
Window-eyes


Hey Gene,




This is really working brother I like it!



Tony

On 5/25/2017 5:52 PM, Gene wrote:

Here is my mostly finished draft of a transition guide for users of
Window-eyes. Comments and suggestions are welcome. I'll send it to the
list in its final form for distribution by whomever wants to do so.

the brief tutorial begins below my signature.
Gene

Moving from Window-eyes to NVDA
A very short tutorial telling you just what you need to know to do a lot
of what

you did before.

Many people are apprehensive about switching to NVDA or any other
screen-reader

from Window-eyes. This tutorial will explain and demonstrate that such

apprehensions are largely based on misunderstandings.

Before I discuss the misunderstanding that causes most of this
apprehension, I'll

briefly discuss installing NVDA and changing the synthesizer used and
speech

parameters.

NVDA has a talking installer. run the file as you would any installation
file.

you may get a dialog asking if you want to run the file. Use the command
alt r

for run. If you get a UAC prompt, answer alt y.
Run narrator. Then run the NVDA installer.
when you run the installer, there will be a pause and then a bit of music
will

play. Not long after, the talking installer will run. Unload Narrator at
that

point. return to the install dialog.
Tab through the dchoices. Accept the license agreement and then tab to
install.

You will get other options but install is the one you want.
Don't stop using NvDA because of the voice. A lot of people don't try
NVDA because

of the voice. As soon as you get it set up, I'll tell you how to change
the

synthesizer used.

After NVDA is installed and running, it's time to learn how to change the


synthesizer.
Issue the command control insert s. Use either insert. From now on,
assume you

can use either insert unless I state differently.
A synthesizer selection dialog will open.
You will see a list of different possibly available synthesizers. Choose
SAPI 5.

I know everyone has at least one SAPI 5 voice on their machine. Up and
down arrow

through the list and stop on SAPI five. Press enter.
You will now hear another voice. It may be the same voice you hear in
Narrator.
Now issue the command control insert v.
You are now in the voice selection and adjustment dialog.
Up and down arrow to see what voices are available. Stop on the one you
want.
Now tab through the dialog and change settings for the voice.
Once you find a voice you want and tab through and set whatever you want
such as

speed and punctuation, press the ok button.

Now, let's continue with what I spoke of at the start of this tutorial.
The

misunderstanding that makes the switch seem daunting is that the user
doesn't

realize that most of the commands he/she uses are Windows commands and
program

commands and they won't change.

Consider the following examples:
Opening menus was and still is alt. That's a Windows command to open
menus in

programs. It's the same no matter which screen-reader you use.
Control o for open doesn't change. Using the arrow keys to move in a
document

doesn't change. Tabbing through dialogs doesn't change. Neither does how
you move

in a list or a treeview or work with a combo box, and the list goes on.
Screen-reader commands, many of which may change, such as read title bar,
provide

access to information you can't get or can't get conveniently by using
Windows or

program commands. for example, read title bar. In Window-eyes, the
command is

control shift t. In NVDA, it's insert t. I am assuming throughout this
tutorial

that you are using the default desktop layout in NVDA. All commands are
given in

that layout. The title bar is something a sighted person looks at. You
can't move

to it with the pc cursor or application cursor, whatever you wish to call
it,

because there is no need. A sighted person can just see it. So the
screen-reader

has a command, read title bar. That command is not a Windows nor a
program

command.

Here are the screen-reader commands you will need to know to allow you to
do a lot

of what you did before.
Read title bar, insert t.
Time, insert f12.
Read current Window, insert b. In Window-eyes the command is control
shift w.
Read to end, insert down arrow. Use the down arrow on the main keyboard.
Stop speech with control, as with screen-readers in general.
Commands such as control home, control end, control left and right arrow
are

Windows movement commands for moving in any standard edit field including
word

processor edit fields. None of them will change.
More screen-reader commands:
Screen review commands:
Note the pattern as I give these commands:
Read previous line, numpad 7.
Read current line, numpad 8.
Read next line numpad nine.
You move in screen review to the previous or next line when you issue
those

commands. You can keep moving and reading until you get to the top or
bottom of

the screen.
Read previous word, numpad 4.
Read current word, numpad 5.
Read next word, numpad 6.
Read previous character, numpad 1.
Read current character, numpad 2.
Read next character, numpad 3.
Note the pattern. Read current is the key in the middle of each of these
rows.
Move to and read previous is the key on the left.
Move to and read next is the key to the right.
The lower the numbers the smaller the movement unit. 1 2 and 3 move by
character.

4 5 and 6 move by word. Etc.
Here are two more important commands:
Jump to top of window, shift numpad 7.
Jump to bottom of window is shift numpad 9.

I've said top and bottom of Window but that's oversimplified. It depends
what kind

of review mode you are using. I won't go into that to any extent in this
very

short tutorial.
that is the one you should be in usually. Unless you change it, you will
remain

there. If you use another review mode, afterword, make sure you return to
object

reviewIf you don't, you won't hear what you expect to hear at various
times.
To make sure you are in object review, issue the command numpad insert
nummpad 1.

When you are already in object review and can't move to another review
mode, you

will hear no previous review mode. You will then know you are in the
right one.

Or if you are returning from another review mode, when you hear object
review, you

will know you are back in the right one.
I won't describe its use here, but screen review is similar not in
commands, but in

how you review the screen to the Window-eyes cursor. Object review is
different

from any review mode available in Window-eyes. It is valuable to know for
various

uses. Depending on how you use your computer, you may find it valuable or
not. I'm

simply making you aware that it is different and that you may want to
learn it.

I'll provide a resource that teaches in great detail how to use NVDA.
This tutorial is to get you going using NVDA and to show you that even
with the

little I will teach, you can still do a good deal of what you used to do.
You may

then learn more as you wish.

Believe it or not, that is just about all I will teach in this very short
tutorial

but I'll tell you a few more things.
Internet browsing:
When you are on a web page, quick navigation commands are almost identical
whether

you are using NVDA or Window-eyes.
Move by headings is h. Skip blocks of links is n.
Move to next button is b,
Next combo box is c.
Next check box is x.
NVDA has an input help mode which is similar to what is in Window-eyes.
Insert and

1 on the main keyboard turns it on. When you press a key or combination
of keys

that might be a command, you will hear what the keys are and what, if any
command

they execute. This varies cdepending on where you are.
When in a browser that supports browse mode, typing a lot of individual
letters

will give you information about what the keys do in browse mode. I
already gave

much of that information above but you may want to press a lot of keys
using input

mode in a browser.

To turn input mode off use the same command you used to turn it on, insert
1.

to learn more about NVDA, a popular tutorial is available at (insert URL.)

On that page, you will see links to download different sections dealing
with

different subjects. You can also download the entire tutorial as a zip
file.

There is also an e-mail list for NVDA users. To join, send a blank
message to this

address:
nvda+subscribe@nvda.groups.io

I hope that this tutorial has removed much of your apprehension about
switching to

NVDA. Now, as you wish or need, you may consult the tutorial I gave a
link to.

NVDA is a powerful screen-reader and it will meet a lot of users needs as
well as

JAWS or Window-eyes does. I hope this very short tutorial gives you a
good

foundation on which to build confidence that the transition should be much
easier

than you may have thought and that it will help make it much more
enjoyable.




Re: a more r less finished draft of my transition guide from Window-eyes

 

Hi,

I’ll wikify it and publish it on the NVDA community wiki page (with your permission of course).

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Tony Ballou
Sent: Thursday, May 25, 2017 4:39 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] a more r less finished draft of my transition guide from Window-eyes

 

Hey Gene,

 

You just have to put the website URL in there from what I can see, otherwise, all's gravy.

 

Tony

 

On 5/25/2017 6:59 PM, Gene wrote:

Thanks.

 

Gene

----- original Message -----

Sent: Thursday, May 25, 2017 5:16 PM

Subject: Re: [nvda] a more r less finished draft of my transition guide from Window-eyes

 

Hey Gene,

 

This is really working brother I like it! 


Tony

On 5/25/2017 5:52 PM, Gene wrote:

Here is my mostly finished draft of a transition guide for users of Window-eyes.  Comments and suggestions are welcome.  I'll send it to the list in its final form for distribution by whomever wants to do so.

 

the brief tutorial begins below my signature.

Gene

 

Moving from Window-eyes to NVDA
A very short tutorial telling you just what you need to know to do a lot of what

 

you did before.

 

Many people are apprehensive about switching to NVDA or any other screen-reader

 

from Window-eyes.  This tutorial will explain and demonstrate that such

 

apprehensions are largely based on misunderstandings. 

 

Before I discuss the misunderstanding that causes most of this apprehension, I'll

 

briefly discuss installing NVDA and changing the synthesizer used and speech

 

parameters.

 

NVDA has a talking installer.  run the file as you would any installation file. 

 

you may get a dialog asking if you want to run the file.  Use the command alt r

 

for run.  If you get a UAC prompt, answer alt y. 
Run narrator.  Then run the NVDA installer. 
when you run the installer, there will be a pause and then a bit of music will

 

play.  Not long after, the talking installer will run.  Unload Narrator at that

 

point.  return to the install dialog.
Tab through the dchoices.  Accept the license agreement and then tab to install. 

 

You will get other options but install is the one you want.
Don't stop using NvDA because of the voice.  A lot of people don't try NVDA because

 

of the voice.  As soon as you get it set up, I'll tell you how to change the

 

synthesizer used.

 

After NVDA is installed and running, it's time to learn how to change the

 

synthesizer. 
Issue the command control insert s.  Use either insert.  From now on, assume you

 

can use either insert unless I state differently.
A synthesizer selection dialog will open.
You will see a list of different possibly available synthesizers.  Choose SAPI 5. 

 

I know everyone has at least one SAPI 5 voice on their machine.  Up and down arrow

 

through the list and stop on SAPI five.  Press enter.
You will now hear another voice.  It may be the same voice you hear in Narrator. 
Now issue the command control insert v.
You are now in the voice selection and adjustment dialog. 
Up and down arrow to see what voices are available.  Stop on the one you want. 
Now tab through the dialog and change settings for the voice. 
Once you find a voice you want and tab through and set whatever you want such as

 

speed and punctuation, press the ok button. 

 

Now, let's continue with what I spoke of at the start of this tutorial.  The

 

misunderstanding that makes the switch seem daunting is that the user doesn't

 

realize that most of the commands he/she uses are Windows commands and program

 

commands and they won't change.

 

Consider the following examples:
Opening menus was and still is alt.  That's a Windows command to open menus in

 

programs.  It's the same no matter which screen-reader you use. 
Control o for open doesn't change.  Using the arrow keys to move in a document

 

doesn't change.  Tabbing through dialogs doesn't change.  Neither does how you move

 

in a list or a treeview or work with a combo box, and the list goes on. 
Screen-reader commands, many of which may change, such as read title bar, provide

 

access to information you can't get or can't get conveniently by using Windows or

 

program commands.  for example, read title bar.  In Window-eyes, the command is

 

control shift t.  In NVDA, it's insert t.  I am assuming throughout this tutorial

 

that you are using the default desktop layout in NVDA.  All commands are given in

 

that layout.  The title bar is something a sighted person looks at.  You can't move

 

to it with the pc cursor or application cursor, whatever you wish to call it,

 

because there is no need.  A sighted person can just see it.  So the screen-reader

 

has a command, read title bar.  That command is not a Windows nor a program

 

command.

 

Here are the screen-reader commands you will need to know to allow you to do a lot

 

of what you did before.
Read title bar, insert t. 
Time, insert f12. 
Read current Window, insert b.  In Window-eyes the command is control shift w. 
Read to end, insert down arrow.  Use the down arrow on the main keyboard.
Stop speech with control, as with screen-readers in general. 
Commands such as control home, control end, control left and right arrow are

 

Windows movement commands for moving in any standard edit field including word

 

processor edit fields.  None of them will change.
More screen-reader commands:
Screen review commands:
Note the pattern as I give these commands:
Read previous line, numpad 7. 
Read current line, numpad 8.
Read next line numpad nine.
You move in screen review to the previous or next line when you issue those

 

commands.  You can keep moving and reading until you get to the top or bottom of

 

the screen.
Read previous word, numpad 4.
Read current word, numpad 5.
Read next word, numpad 6.
Read previous character, numpad 1.
Read current character, numpad 2.
Read next character, numpad 3.
Note the pattern.  Read current is the key in the middle of each of these rows.
Move to and read previous is the key on the left. 
Move to and read next is the key to the right.
The lower the numbers the smaller the movement unit.  1 2 and 3 move by character. 

 

4 5 and 6 move by word.  Etc.
Here are two more important commands:
Jump to top of window, shift numpad 7.
Jump to bottom of window is shift numpad 9.

 

I've said top and bottom of Window but that's oversimplified.  It depends what kind

 

of review mode you are using.  I won't go into that to any extent in this very

 

short tutorial. 
that is the one you should be in usually.  Unless you change it, you will remain

 

there.  If you use another review mode, afterword, make sure you return to object

 

reviewIf you don't, you won't hear what you expect to hear at various times. 
To make sure you are in object review, issue the command numpad insert nummpad 1. 

 

When you are already in object review and can't move to another review mode, you

 

will hear no previous review mode.  You will then know you are in the right one. 

 

Or if you are returning from another review mode, when you hear object review, you

 

will know you are back in the right one.
I won't describe its use here, but screen review is similar not in commands, but in

 

how you review the screen to the Window-eyes cursor.  Object review is different

 

from any review mode available in Window-eyes.  It is valuable to know for various

 

uses.  Depending on how you use your computer, you may find it valuable or not.  I'm

 

simply making you aware that it is different and that you may want to learn it.

 

I'll provide a resource that teaches in great detail how to use NVDA.
This tutorial is to get you going using NVDA and to show you that even with the

 

little I will teach, you can still do a good deal of what you used to do.  You may

 

then learn more as you wish.

 

Believe it or not, that is just about all I will teach in this very short tutorial

 

but  I'll tell you a few more things.
Internet browsing:
When you are on a web page, quick navigation commands are almost identical whether

 

you are using NVDA or Window-eyes. 
Move by headings is h.  Skip blocks of links is n. 
Move to next button is b, 
Next combo box is c.
Next check box is x.
NVDA has an input help mode which is similar to what is in Window-eyes.  Insert and

 

1 on the main keyboard turns it on.  When you press a key or combination of keys

 

that might be a command, you will hear what the keys are and what, if any command

 

they execute.  This varies cdepending on where you are.
When in a browser that supports browse mode, typing a lot of individual letters

 

will give you information about what the keys do in browse mode.  I already gave

 

much of that information above but you may want to press a lot of keys using input

 

mode in a browser. 

 

To turn input mode off use the same command you used to turn it on, insert 1.

 

to learn more about NVDA, a popular tutorial is available at (insert URL.) 
On that page, you will see links to download different sections dealing with

 

different subjects.  You can also download the entire tutorial as a zip file.

 

There is also an e-mail list for NVDA users.  To join, send a blank message to this

 

 

I hope that this tutorial has removed much of your apprehension about switching to

 

NVDA.  Now, as you wish or need, you may consult the tutorial I gave a link to. 

 

NVDA is a powerful screen-reader and it will meet a lot of users needs as well as

 

JAWS or Window-eyes does.  I hope this very short tutorial gives you a good

 

foundation on which to build confidence that the transition should be much easier

 

than you may have thought and that it will help make it much more enjoyable.

 

 


Re: a more r less finished draft of my transition guide from Window-eyes

Tony Ballou
 

Hey Gene,


You just have to put the website URL in there from what I can see, otherwise, all's gravy.


Tony


On 5/25/2017 6:59 PM, Gene wrote:
Thanks.
 
Gene
----- original Message -----
Sent: Thursday, May 25, 2017 5:16 PM
Subject: Re: [nvda] a more r less finished draft of my transition guide from Window-eyes

Hey Gene,


This is really working brother I like it! 


Tony
On 5/25/2017 5:52 PM, Gene wrote:
Here is my mostly finished draft of a transition guide for users of Window-eyes.  Comments and suggestions are welcome.  I'll send it to the list in its final form for distribution by whomever wants to do so.
 
the brief tutorial begins below my signature.
Gene
 
Moving from Window-eyes to NVDA
A very short tutorial telling you just what you need to know to do a lot of what
 
you did before.
 
Many people are apprehensive about switching to NVDA or any other screen-reader
 
from Window-eyes.  This tutorial will explain and demonstrate that such
 
apprehensions are largely based on misunderstandings. 
 
Before I discuss the misunderstanding that causes most of this apprehension, I'll
 
briefly discuss installing NVDA and changing the synthesizer used and speech
 
parameters.
 
NVDA has a talking installer.  run the file as you would any installation file. 
 
you may get a dialog asking if you want to run the file.  Use the command alt r
 
for run.  If you get a UAC prompt, answer alt y. 
Run narrator.  Then run the NVDA installer. 
when you run the installer, there will be a pause and then a bit of music will
 
play.  Not long after, the talking installer will run.  Unload Narrator at that
 
point.  return to the install dialog.
Tab through the dchoices.  Accept the license agreement and then tab to install. 
 
You will get other options but install is the one you want.
Don't stop using NvDA because of the voice.  A lot of people don't try NVDA because
 
of the voice.  As soon as you get it set up, I'll tell you how to change the
 
synthesizer used.
 
After NVDA is installed and running, it's time to learn how to change the
 
synthesizer. 
Issue the command control insert s.  Use either insert.  From now on, assume you
 
can use either insert unless I state differently.
A synthesizer selection dialog will open.
You will see a list of different possibly available synthesizers.  Choose SAPI 5. 
 
I know everyone has at least one SAPI 5 voice on their machine.  Up and down arrow
 
through the list and stop on SAPI five.  Press enter.
You will now hear another voice.  It may be the same voice you hear in Narrator. 
Now issue the command control insert v.
You are now in the voice selection and adjustment dialog. 
Up and down arrow to see what voices are available.  Stop on the one you want. 
Now tab through the dialog and change settings for the voice. 
Once you find a voice you want and tab through and set whatever you want such as
 
speed and punctuation, press the ok button. 
 
Now, let's continue with what I spoke of at the start of this tutorial.  The
 
misunderstanding that makes the switch seem daunting is that the user doesn't
 
realize that most of the commands he/she uses are Windows commands and program
 
commands and they won't change.
 
Consider the following examples:
Opening menus was and still is alt.  That's a Windows command to open menus in
 
programs.  It's the same no matter which screen-reader you use. 
Control o for open doesn't change.  Using the arrow keys to move in a document
 
doesn't change.  Tabbing through dialogs doesn't change.  Neither does how you move
 
in a list or a treeview or work with a combo box, and the list goes on. 
Screen-reader commands, many of which may change, such as read title bar, provide
 
access to information you can't get or can't get conveniently by using Windows or
 
program commands.  for example, read title bar.  In Window-eyes, the command is
 
control shift t.  In NVDA, it's insert t.  I am assuming throughout this tutorial
 
that you are using the default desktop layout in NVDA.  All commands are given in
 
that layout.  The title bar is something a sighted person looks at.  You can't move
 
to it with the pc cursor or application cursor, whatever you wish to call it,
 
because there is no need.  A sighted person can just see it.  So the screen-reader
 
has a command, read title bar.  That command is not a Windows nor a program
 
command.
 
Here are the screen-reader commands you will need to know to allow you to do a lot
 
of what you did before.
Read title bar, insert t. 
Time, insert f12. 
Read current Window, insert b.  In Window-eyes the command is control shift w. 
Read to end, insert down arrow.  Use the down arrow on the main keyboard.
Stop speech with control, as with screen-readers in general. 
Commands such as control home, control end, control left and right arrow are
 
Windows movement commands for moving in any standard edit field including word
 
processor edit fields.  None of them will change.
More screen-reader commands:
Screen review commands:
Note the pattern as I give these commands:
Read previous line, numpad 7. 
Read current line, numpad 8.
Read next line numpad nine.
You move in screen review to the previous or next line when you issue those
 
commands.  You can keep moving and reading until you get to the top or bottom of
 
the screen.
Read previous word, numpad 4.
Read current word, numpad 5.
Read next word, numpad 6.
Read previous character, numpad 1.
Read current character, numpad 2.
Read next character, numpad 3.
Note the pattern.  Read current is the key in the middle of each of these rows.
Move to and read previous is the key on the left. 
Move to and read next is the key to the right.
The lower the numbers the smaller the movement unit.  1 2 and 3 move by character. 
 
4 5 and 6 move by word.  Etc.
Here are two more important commands:
Jump to top of window, shift numpad 7.
Jump to bottom of window is shift numpad 9.
 
I've said top and bottom of Window but that's oversimplified.  It depends what kind
 
of review mode you are using.  I won't go into that to any extent in this very
 
short tutorial. 
that is the one you should be in usually.  Unless you change it, you will remain
 
there.  If you use another review mode, afterword, make sure you return to object
 
reviewIf you don't, you won't hear what you expect to hear at various times. 
To make sure you are in object review, issue the command numpad insert nummpad 1. 
 
When you are already in object review and can't move to another review mode, you
 
will hear no previous review mode.  You will then know you are in the right one. 
 
Or if you are returning from another review mode, when you hear object review, you
 
will know you are back in the right one.
I won't describe its use here, but screen review is similar not in commands, but in
 
how you review the screen to the Window-eyes cursor.  Object review is different
 
from any review mode available in Window-eyes.  It is valuable to know for various
 
uses.  Depending on how you use your computer, you may find it valuable or not.  I'm
 
simply making you aware that it is different and that you may want to learn it.
 
I'll provide a resource that teaches in great detail how to use NVDA.
This tutorial is to get you going using NVDA and to show you that even with the
 
little I will teach, you can still do a good deal of what you used to do.  You may
 
then learn more as you wish.
 
Believe it or not, that is just about all I will teach in this very short tutorial
 
but  I'll tell you a few more things.
Internet browsing:
When you are on a web page, quick navigation commands are almost identical whether
 
you are using NVDA or Window-eyes. 
Move by headings is h.  Skip blocks of links is n. 
Move to next button is b, 
Next combo box is c.
Next check box is x.
NVDA has an input help mode which is similar to what is in Window-eyes.  Insert and
 
1 on the main keyboard turns it on.  When you press a key or combination of keys
 
that might be a command, you will hear what the keys are and what, if any command
 
they execute.  This varies cdepending on where you are.
When in a browser that supports browse mode, typing a lot of individual letters
 
will give you information about what the keys do in browse mode.  I already gave
 
much of that information above but you may want to press a lot of keys using input
 
mode in a browser. 
 
To turn input mode off use the same command you used to turn it on, insert 1.
 
to learn more about NVDA, a popular tutorial is available at (insert URL.) 
On that page, you will see links to download different sections dealing with
 
different subjects.  You can also download the entire tutorial as a zip file.
 
There is also an e-mail list for NVDA users.  To join, send a blank message to this
 
 
I hope that this tutorial has removed much of your apprehension about switching to
 
NVDA.  Now, as you wish or need, you may consult the tutorial I gave a link to. 
 
NVDA is a powerful screen-reader and it will meet a lot of users needs as well as
 
JAWS or Window-eyes does.  I hope this very short tutorial gives you a good
 
foundation on which to build confidence that the transition should be much easier
 
than you may have thought and that it will help make it much more enjoyable.



Re: Using NVDA to Create a Digital Signature in Word

David Mehler
 

Hello,

Is this digital signature the same as scanning in a signature and
using that as a signature? Or am I thinking of something else?

'm needing a way to make documents legally binding.

Thanks.
Dave.

On 5/25/17, Tony Ballou <cyberpro224@outlook.com> wrote:
Hello David,


If my memory serves me correct, Using the doc format will work as long
as Microsoft word is installed The rtf format works on any windows based
system regardless. As for a digital signature here's how to do it.


Press alt+n for Insert, then g to open a signature menu. From here,
either a Microsoft Office Signature Line or "Add signature services" can
be selected. There are a number of services which can be subscribed to,
which allow digitally signing various types of documents (not only Word
documents). Many of these can be integrated into Word.
When a Microsoft Office signature line is added, a dialog opens allowing
you to include: the name, title and contact details of the signatory.
The document can be signed by selecting the signature line and choosing
"sign" from the context menu. In the dialog which appears, the focus is
on an edit field to type your name. There is also a link to select an
image of your actual signature instead. Personal details and also the
signing service to use can also be updated.
If no signing service is selected, the document can still be signed,
however, it will not be as secure or verifiable.


Hope this helps.


Tony



On 5/25/2017 2:52 PM, David Russell wrote:
Hello NVDA Group,

I am looking for a set of instructions -user-friendly for sightless
NVDA users that would tell someone how to set up a digital signature
in a document for others to add their signature and date, then return
by email attachment. It is for a Publisher Agreement.

I also wonder would it be best to send this as a doc file or RTF since
not everyone can use PDF?
Thanks in advance. I need an answer within a few hours.




Re: a more r less finished draft of my transition guide from Window-eyes

David Mehler
 

Hello Gene,

I just read your tutorial draft. I have a thanks, a question, and a comment.

The thanks, thanks for the information on the switching synth method and sapi5.

The question, you mentioned that your using desktop mode. Can you
extend the tutorial to include the laptop keystrokes for those
transitioning from a laptop.

And the comment, during the install you load narrator then a little
later unload it. Why is this?

Thanks.
Dave.

On 5/25/17, Gene <gsasner@ripco.com> wrote:
Thanks.

Gene
----- original Message -----

From: Tony Ballou
Sent: Thursday, May 25, 2017 5:16 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] a more r less finished draft of my transition guide from
Window-eyes


Hey Gene,




This is really working brother I like it!



Tony

On 5/25/2017 5:52 PM, Gene wrote:

Here is my mostly finished draft of a transition guide for users of
Window-eyes. Comments and suggestions are welcome. I'll send it to the
list in its final form for distribution by whomever wants to do so.

the brief tutorial begins below my signature.
Gene

Moving from Window-eyes to NVDA
A very short tutorial telling you just what you need to know to do a lot
of what

you did before.

Many people are apprehensive about switching to NVDA or any other
screen-reader

from Window-eyes. This tutorial will explain and demonstrate that such

apprehensions are largely based on misunderstandings.

Before I discuss the misunderstanding that causes most of this
apprehension, I'll

briefly discuss installing NVDA and changing the synthesizer used and
speech

parameters.

NVDA has a talking installer. run the file as you would any installation
file.

you may get a dialog asking if you want to run the file. Use the command
alt r

for run. If you get a UAC prompt, answer alt y.
Run narrator. Then run the NVDA installer.
when you run the installer, there will be a pause and then a bit of music
will

play. Not long after, the talking installer will run. Unload Narrator at
that

point. return to the install dialog.
Tab through the dchoices. Accept the license agreement and then tab to
install.

You will get other options but install is the one you want.
Don't stop using NvDA because of the voice. A lot of people don't try
NVDA because

of the voice. As soon as you get it set up, I'll tell you how to change
the

synthesizer used.

After NVDA is installed and running, it's time to learn how to change the


synthesizer.
Issue the command control insert s. Use either insert. From now on,
assume you

can use either insert unless I state differently.
A synthesizer selection dialog will open.
You will see a list of different possibly available synthesizers. Choose
SAPI 5.

I know everyone has at least one SAPI 5 voice on their machine. Up and
down arrow

through the list and stop on SAPI five. Press enter.
You will now hear another voice. It may be the same voice you hear in
Narrator.
Now issue the command control insert v.
You are now in the voice selection and adjustment dialog.
Up and down arrow to see what voices are available. Stop on the one you
want.
Now tab through the dialog and change settings for the voice.
Once you find a voice you want and tab through and set whatever you want
such as

speed and punctuation, press the ok button.

Now, let's continue with what I spoke of at the start of this tutorial.
The

misunderstanding that makes the switch seem daunting is that the user
doesn't

realize that most of the commands he/she uses are Windows commands and
program

commands and they won't change.

Consider the following examples:
Opening menus was and still is alt. That's a Windows command to open
menus in

programs. It's the same no matter which screen-reader you use.
Control o for open doesn't change. Using the arrow keys to move in a
document

doesn't change. Tabbing through dialogs doesn't change. Neither does how
you move

in a list or a treeview or work with a combo box, and the list goes on.
Screen-reader commands, many of which may change, such as read title bar,
provide

access to information you can't get or can't get conveniently by using
Windows or

program commands. for example, read title bar. In Window-eyes, the
command is

control shift t. In NVDA, it's insert t. I am assuming throughout this
tutorial

that you are using the default desktop layout in NVDA. All commands are
given in

that layout. The title bar is something a sighted person looks at. You
can't move

to it with the pc cursor or application cursor, whatever you wish to call
it,

because there is no need. A sighted person can just see it. So the
screen-reader

has a command, read title bar. That command is not a Windows nor a
program

command.

Here are the screen-reader commands you will need to know to allow you to
do a lot

of what you did before.
Read title bar, insert t.
Time, insert f12.
Read current Window, insert b. In Window-eyes the command is control
shift w.
Read to end, insert down arrow. Use the down arrow on the main keyboard.
Stop speech with control, as with screen-readers in general.
Commands such as control home, control end, control left and right arrow
are

Windows movement commands for moving in any standard edit field including
word

processor edit fields. None of them will change.
More screen-reader commands:
Screen review commands:
Note the pattern as I give these commands:
Read previous line, numpad 7.
Read current line, numpad 8.
Read next line numpad nine.
You move in screen review to the previous or next line when you issue
those

commands. You can keep moving and reading until you get to the top or
bottom of

the screen.
Read previous word, numpad 4.
Read current word, numpad 5.
Read next word, numpad 6.
Read previous character, numpad 1.
Read current character, numpad 2.
Read next character, numpad 3.
Note the pattern. Read current is the key in the middle of each of these
rows.
Move to and read previous is the key on the left.
Move to and read next is the key to the right.
The lower the numbers the smaller the movement unit. 1 2 and 3 move by
character.

4 5 and 6 move by word. Etc.
Here are two more important commands:
Jump to top of window, shift numpad 7.
Jump to bottom of window is shift numpad 9.

I've said top and bottom of Window but that's oversimplified. It depends
what kind

of review mode you are using. I won't go into that to any extent in this
very

short tutorial.
that is the one you should be in usually. Unless you change it, you will
remain

there. If you use another review mode, afterword, make sure you return to
object

reviewIf you don't, you won't hear what you expect to hear at various
times.
To make sure you are in object review, issue the command numpad insert
nummpad 1.

When you are already in object review and can't move to another review
mode, you

will hear no previous review mode. You will then know you are in the
right one.

Or if you are returning from another review mode, when you hear object
review, you

will know you are back in the right one.
I won't describe its use here, but screen review is similar not in
commands, but in

how you review the screen to the Window-eyes cursor. Object review is
different

from any review mode available in Window-eyes. It is valuable to know for
various

uses. Depending on how you use your computer, you may find it valuable or
not. I'm

simply making you aware that it is different and that you may want to
learn it.

I'll provide a resource that teaches in great detail how to use NVDA.
This tutorial is to get you going using NVDA and to show you that even
with the

little I will teach, you can still do a good deal of what you used to do.
You may

then learn more as you wish.

Believe it or not, that is just about all I will teach in this very short
tutorial

but I'll tell you a few more things.
Internet browsing:
When you are on a web page, quick navigation commands are almost identical
whether

you are using NVDA or Window-eyes.
Move by headings is h. Skip blocks of links is n.
Move to next button is b,
Next combo box is c.
Next check box is x.
NVDA has an input help mode which is similar to what is in Window-eyes.
Insert and

1 on the main keyboard turns it on. When you press a key or combination
of keys

that might be a command, you will hear what the keys are and what, if any
command

they execute. This varies cdepending on where you are.
When in a browser that supports browse mode, typing a lot of individual
letters

will give you information about what the keys do in browse mode. I
already gave

much of that information above but you may want to press a lot of keys
using input

mode in a browser.

To turn input mode off use the same command you used to turn it on, insert
1.

to learn more about NVDA, a popular tutorial is available at (insert URL.)

On that page, you will see links to download different sections dealing
with

different subjects. You can also download the entire tutorial as a zip
file.

There is also an e-mail list for NVDA users. To join, send a blank
message to this

address:
nvda+subscribe@nvda.groups.io

I hope that this tutorial has removed much of your apprehension about
switching to

NVDA. Now, as you wish or need, you may consult the tutorial I gave a
link to.

NVDA is a powerful screen-reader and it will meet a lot of users needs as
well as

JAWS or Window-eyes does. I hope this very short tutorial gives you a
good

foundation on which to build confidence that the transition should be much
easier

than you may have thought and that it will help make it much more
enjoyable.




vocalizer voices for NVDA

Don H
 

OK so I see that the A T Guys sell the vocalizer voices for use with NVDA. They have a option to add a coupon to reduce the price of $ 69 for the voice package.
Anyone know where to get a coupon for A T Guys?


Re: a more r less finished draft of my transition guide from Window-eyes

Gene
 

Thanks.
 
Gene
----- original Message -----

Sent: Thursday, May 25, 2017 5:16 PM
Subject: Re: [nvda] a more r less finished draft of my transition guide from Window-eyes

Hey Gene,


This is really working brother I like it! 


Tony
On 5/25/2017 5:52 PM, Gene wrote:
Here is my mostly finished draft of a transition guide for users of Window-eyes.  Comments and suggestions are welcome.  I'll send it to the list in its final form for distribution by whomever wants to do so.
 
the brief tutorial begins below my signature.
Gene
 
Moving from Window-eyes to NVDA
A very short tutorial telling you just what you need to know to do a lot of what
 
you did before.
 
Many people are apprehensive about switching to NVDA or any other screen-reader
 
from Window-eyes.  This tutorial will explain and demonstrate that such
 
apprehensions are largely based on misunderstandings. 
 
Before I discuss the misunderstanding that causes most of this apprehension, I'll
 
briefly discuss installing NVDA and changing the synthesizer used and speech
 
parameters.
 
NVDA has a talking installer.  run the file as you would any installation file. 
 
you may get a dialog asking if you want to run the file.  Use the command alt r
 
for run.  If you get a UAC prompt, answer alt y. 
Run narrator.  Then run the NVDA installer. 
when you run the installer, there will be a pause and then a bit of music will
 
play.  Not long after, the talking installer will run.  Unload Narrator at that
 
point.  return to the install dialog.
Tab through the dchoices.  Accept the license agreement and then tab to install. 
 
You will get other options but install is the one you want.
Don't stop using NvDA because of the voice.  A lot of people don't try NVDA because
 
of the voice.  As soon as you get it set up, I'll tell you how to change the
 
synthesizer used.
 
After NVDA is installed and running, it's time to learn how to change the
 
synthesizer. 
Issue the command control insert s.  Use either insert.  From now on, assume you
 
can use either insert unless I state differently.
A synthesizer selection dialog will open.
You will see a list of different possibly available synthesizers.  Choose SAPI 5. 
 
I know everyone has at least one SAPI 5 voice on their machine.  Up and down arrow
 
through the list and stop on SAPI five.  Press enter.
You will now hear another voice.  It may be the same voice you hear in Narrator. 
Now issue the command control insert v.
You are now in the voice selection and adjustment dialog. 
Up and down arrow to see what voices are available.  Stop on the one you want. 
Now tab through the dialog and change settings for the voice. 
Once you find a voice you want and tab through and set whatever you want such as
 
speed and punctuation, press the ok button. 
 
Now, let's continue with what I spoke of at the start of this tutorial.  The
 
misunderstanding that makes the switch seem daunting is that the user doesn't
 
realize that most of the commands he/she uses are Windows commands and program
 
commands and they won't change.
 
Consider the following examples:
Opening menus was and still is alt.  That's a Windows command to open menus in
 
programs.  It's the same no matter which screen-reader you use. 
Control o for open doesn't change.  Using the arrow keys to move in a document
 
doesn't change.  Tabbing through dialogs doesn't change.  Neither does how you move
 
in a list or a treeview or work with a combo box, and the list goes on. 
Screen-reader commands, many of which may change, such as read title bar, provide
 
access to information you can't get or can't get conveniently by using Windows or
 
program commands.  for example, read title bar.  In Window-eyes, the command is
 
control shift t.  In NVDA, it's insert t.  I am assuming throughout this tutorial
 
that you are using the default desktop layout in NVDA.  All commands are given in
 
that layout.  The title bar is something a sighted person looks at.  You can't move
 
to it with the pc cursor or application cursor, whatever you wish to call it,
 
because there is no need.  A sighted person can just see it.  So the screen-reader
 
has a command, read title bar.  That command is not a Windows nor a program
 
command.
 
Here are the screen-reader commands you will need to know to allow you to do a lot
 
of what you did before.
Read title bar, insert t. 
Time, insert f12. 
Read current Window, insert b.  In Window-eyes the command is control shift w. 
Read to end, insert down arrow.  Use the down arrow on the main keyboard.
Stop speech with control, as with screen-readers in general. 
Commands such as control home, control end, control left and right arrow are
 
Windows movement commands for moving in any standard edit field including word
 
processor edit fields.  None of them will change.
More screen-reader commands:
Screen review commands:
Note the pattern as I give these commands:
Read previous line, numpad 7. 
Read current line, numpad 8.
Read next line numpad nine.
You move in screen review to the previous or next line when you issue those
 
commands.  You can keep moving and reading until you get to the top or bottom of
 
the screen.
Read previous word, numpad 4.
Read current word, numpad 5.
Read next word, numpad 6.
Read previous character, numpad 1.
Read current character, numpad 2.
Read next character, numpad 3.
Note the pattern.  Read current is the key in the middle of each of these rows.
Move to and read previous is the key on the left. 
Move to and read next is the key to the right.
The lower the numbers the smaller the movement unit.  1 2 and 3 move by character. 
 
4 5 and 6 move by word.  Etc.
Here are two more important commands:
Jump to top of window, shift numpad 7.
Jump to bottom of window is shift numpad 9.
 
I've said top and bottom of Window but that's oversimplified.  It depends what kind
 
of review mode you are using.  I won't go into that to any extent in this very
 
short tutorial. 
that is the one you should be in usually.  Unless you change it, you will remain
 
there.  If you use another review mode, afterword, make sure you return to object
 
reviewIf you don't, you won't hear what you expect to hear at various times. 
To make sure you are in object review, issue the command numpad insert nummpad 1. 
 
When you are already in object review and can't move to another review mode, you
 
will hear no previous review mode.  You will then know you are in the right one. 
 
Or if you are returning from another review mode, when you hear object review, you
 
will know you are back in the right one.
I won't describe its use here, but screen review is similar not in commands, but in
 
how you review the screen to the Window-eyes cursor.  Object review is different
 
from any review mode available in Window-eyes.  It is valuable to know for various
 
uses.  Depending on how you use your computer, you may find it valuable or not.  I'm
 
simply making you aware that it is different and that you may want to learn it.
 
I'll provide a resource that teaches in great detail how to use NVDA.
This tutorial is to get you going using NVDA and to show you that even with the
 
little I will teach, you can still do a good deal of what you used to do.  You may
 
then learn more as you wish.
 
Believe it or not, that is just about all I will teach in this very short tutorial
 
but  I'll tell you a few more things.
Internet browsing:
When you are on a web page, quick navigation commands are almost identical whether
 
you are using NVDA or Window-eyes. 
Move by headings is h.  Skip blocks of links is n. 
Move to next button is b, 
Next combo box is c.
Next check box is x.
NVDA has an input help mode which is similar to what is in Window-eyes.  Insert and
 
1 on the main keyboard turns it on.  When you press a key or combination of keys
 
that might be a command, you will hear what the keys are and what, if any command
 
they execute.  This varies cdepending on where you are.
When in a browser that supports browse mode, typing a lot of individual letters
 
will give you information about what the keys do in browse mode.  I already gave
 
much of that information above but you may want to press a lot of keys using input
 
mode in a browser. 
 
To turn input mode off use the same command you used to turn it on, insert 1.
 
to learn more about NVDA, a popular tutorial is available at (insert URL.) 
On that page, you will see links to download different sections dealing with
 
different subjects.  You can also download the entire tutorial as a zip file.
 
There is also an e-mail list for NVDA users.  To join, send a blank message to this
 
 
I hope that this tutorial has removed much of your apprehension about switching to
 
NVDA.  Now, as you wish or need, you may consult the tutorial I gave a link to. 
 
NVDA is a powerful screen-reader and it will meet a lot of users needs as well as
 
JAWS or Window-eyes does.  I hope this very short tutorial gives you a good
 
foundation on which to build confidence that the transition should be much easier
 
than you may have thought and that it will help make it much more enjoyable.


Re: a more r less finished draft of my transition guide from Window-eyes

Tony Ballou
 

Hey Gene,


This is really working brother I like it! 


Tony

On 5/25/2017 5:52 PM, Gene wrote:
Here is my mostly finished draft of a transition guide for users of Window-eyes.  Comments and suggestions are welcome.  I'll send it to the list in its final form for distribution by whomever wants to do so.
 
the brief tutorial begins below my signature.
Gene
 
Moving from Window-eyes to NVDA
A very short tutorial telling you just what you need to know to do a lot of what
 
you did before.
 
Many people are apprehensive about switching to NVDA or any other screen-reader
 
from Window-eyes.  This tutorial will explain and demonstrate that such
 
apprehensions are largely based on misunderstandings. 
 
Before I discuss the misunderstanding that causes most of this apprehension, I'll
 
briefly discuss installing NVDA and changing the synthesizer used and speech
 
parameters.
 
NVDA has a talking installer.  run the file as you would any installation file. 
 
you may get a dialog asking if you want to run the file.  Use the command alt r
 
for run.  If you get a UAC prompt, answer alt y. 
Run narrator.  Then run the NVDA installer. 
when you run the installer, there will be a pause and then a bit of music will
 
play.  Not long after, the talking installer will run.  Unload Narrator at that
 
point.  return to the install dialog.
Tab through the dchoices.  Accept the license agreement and then tab to install. 
 
You will get other options but install is the one you want.
Don't stop using NvDA because of the voice.  A lot of people don't try NVDA because
 
of the voice.  As soon as you get it set up, I'll tell you how to change the
 
synthesizer used.
 
After NVDA is installed and running, it's time to learn how to change the
 
synthesizer. 
Issue the command control insert s.  Use either insert.  From now on, assume you
 
can use either insert unless I state differently.
A synthesizer selection dialog will open.
You will see a list of different possibly available synthesizers.  Choose SAPI 5. 
 
I know everyone has at least one SAPI 5 voice on their machine.  Up and down arrow
 
through the list and stop on SAPI five.  Press enter.
You will now hear another voice.  It may be the same voice you hear in Narrator. 
Now issue the command control insert v.
You are now in the voice selection and adjustment dialog. 
Up and down arrow to see what voices are available.  Stop on the one you want. 
Now tab through the dialog and change settings for the voice. 
Once you find a voice you want and tab through and set whatever you want such as
 
speed and punctuation, press the ok button. 
 
Now, let's continue with what I spoke of at the start of this tutorial.  The
 
misunderstanding that makes the switch seem daunting is that the user doesn't
 
realize that most of the commands he/she uses are Windows commands and program
 
commands and they won't change.
 
Consider the following examples:
Opening menus was and still is alt.  That's a Windows command to open menus in
 
programs.  It's the same no matter which screen-reader you use. 
Control o for open doesn't change.  Using the arrow keys to move in a document
 
doesn't change.  Tabbing through dialogs doesn't change.  Neither does how you move
 
in a list or a treeview or work with a combo box, and the list goes on. 
Screen-reader commands, many of which may change, such as read title bar, provide
 
access to information you can't get or can't get conveniently by using Windows or
 
program commands.  for example, read title bar.  In Window-eyes, the command is
 
control shift t.  In NVDA, it's insert t.  I am assuming throughout this tutorial
 
that you are using the default desktop layout in NVDA.  All commands are given in
 
that layout.  The title bar is something a sighted person looks at.  You can't move
 
to it with the pc cursor or application cursor, whatever you wish to call it,
 
because there is no need.  A sighted person can just see it.  So the screen-reader
 
has a command, read title bar.  That command is not a Windows nor a program
 
command.
 
Here are the screen-reader commands you will need to know to allow you to do a lot
 
of what you did before.
Read title bar, insert t. 
Time, insert f12. 
Read current Window, insert b.  In Window-eyes the command is control shift w. 
Read to end, insert down arrow.  Use the down arrow on the main keyboard.
Stop speech with control, as with screen-readers in general. 
Commands such as control home, control end, control left and right arrow are
 
Windows movement commands for moving in any standard edit field including word
 
processor edit fields.  None of them will change.
More screen-reader commands:
Screen review commands:
Note the pattern as I give these commands:
Read previous line, numpad 7. 
Read current line, numpad 8.
Read next line numpad nine.
You move in screen review to the previous or next line when you issue those
 
commands.  You can keep moving and reading until you get to the top or bottom of
 
the screen.
Read previous word, numpad 4.
Read current word, numpad 5.
Read next word, numpad 6.
Read previous character, numpad 1.
Read current character, numpad 2.
Read next character, numpad 3.
Note the pattern.  Read current is the key in the middle of each of these rows.
Move to and read previous is the key on the left. 
Move to and read next is the key to the right.
The lower the numbers the smaller the movement unit.  1 2 and 3 move by character. 
 
4 5 and 6 move by word.  Etc.
Here are two more important commands:
Jump to top of window, shift numpad 7.
Jump to bottom of window is shift numpad 9.
 
I've said top and bottom of Window but that's oversimplified.  It depends what kind
 
of review mode you are using.  I won't go into that to any extent in this very
 
short tutorial. 
that is the one you should be in usually.  Unless you change it, you will remain
 
there.  If you use another review mode, afterword, make sure you return to object
 
reviewIf you don't, you won't hear what you expect to hear at various times. 
To make sure you are in object review, issue the command numpad insert nummpad 1. 
 
When you are already in object review and can't move to another review mode, you
 
will hear no previous review mode.  You will then know you are in the right one. 
 
Or if you are returning from another review mode, when you hear object review, you
 
will know you are back in the right one.
I won't describe its use here, but screen review is similar not in commands, but in
 
how you review the screen to the Window-eyes cursor.  Object review is different
 
from any review mode available in Window-eyes.  It is valuable to know for various
 
uses.  Depending on how you use your computer, you may find it valuable or not.  I'm
 
simply making you aware that it is different and that you may want to learn it.
 
I'll provide a resource that teaches in great detail how to use NVDA.
This tutorial is to get you going using NVDA and to show you that even with the
 
little I will teach, you can still do a good deal of what you used to do.  You may
 
then learn more as you wish.
 
Believe it or not, that is just about all I will teach in this very short tutorial
 
but  I'll tell you a few more things.
Internet browsing:
When you are on a web page, quick navigation commands are almost identical whether
 
you are using NVDA or Window-eyes. 
Move by headings is h.  Skip blocks of links is n. 
Move to next button is b, 
Next combo box is c.
Next check box is x.
NVDA has an input help mode which is similar to what is in Window-eyes.  Insert and
 
1 on the main keyboard turns it on.  When you press a key or combination of keys
 
that might be a command, you will hear what the keys are and what, if any command
 
they execute.  This varies cdepending on where you are.
When in a browser that supports browse mode, typing a lot of individual letters
 
will give you information about what the keys do in browse mode.  I already gave
 
much of that information above but you may want to press a lot of keys using input
 
mode in a browser. 
 
To turn input mode off use the same command you used to turn it on, insert 1.
 
to learn more about NVDA, a popular tutorial is available at (insert URL.) 
On that page, you will see links to download different sections dealing with
 
different subjects.  You can also download the entire tutorial as a zip file.
 
There is also an e-mail list for NVDA users.  To join, send a blank message to this
 
 
I hope that this tutorial has removed much of your apprehension about switching to
 
NVDA.  Now, as you wish or need, you may consult the tutorial I gave a link to. 
 
NVDA is a powerful screen-reader and it will meet a lot of users needs as well as
 
JAWS or Window-eyes does.  I hope this very short tutorial gives you a good
 
foundation on which to build confidence that the transition should be much easier
 
than you may have thought and that it will help make it much more enjoyable.


Re: NVDA 2017 error

George McDermith - CDLE
 

Thanks all for your response.

I found the run command suggestion below seems to have fixed it.
Appreciated the swift response.

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Tyler
Spivey
Sent: Wednesday, May 24, 2017 1:09 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2017 error

Uninstalling NVDA won't fix this, because it doesn't delete the user
configuration.
The easiest way to fix this is:
1. Press Windows+r to bring up the Run dialog.
2. Type: %appdata%\nvda
3. Press enter.
4. Find nvda.ini and delete it.

This won't remove your addons, just the configuration file which tells NVDA
which synthesizer is currently active.

On 5/24/2017 10:38 AM, George McDermith - CDLE wrote:
Greetings all,



I am an adaptive technology instructor in Colorado,
and am attempting to use NVDA to meet client needs.



While attempting to demonstrate NVDA on a PC with
multiple accounts I was changing the built in voices and received an
error message saying I needed to enter a password in order to use the
True Voice selected. The dialog box continued to reappear despite
trying to dismiss it, and NVDA was subsequently unresponsive. I have
attempted removing NVDA from all the accounts on the computer,
reinstalling it from the web site, and I continue to get the same error
message.



Anyone have any work arounds or ideas? My thanks for
the assistance.



George McDermith

Adaptive Technology Specialist

Phone: 303-866-4999



2211 West Evans Avenue Bldg A

Denver, CO 80223

*Please click here to tell us how we’re doing.
<https://www.surveymonkey.com/r/5779VYB>*




a more r less finished draft of my transition guide from Window-eyes

Gene
 

Here is my mostly finished draft of a transition guide for users of Window-eyes.  Comments and suggestions are welcome.  I'll send it to the list in its final form for distribution by whomever wants to do so.
 
the brief tutorial begins below my signature.
Gene
 
Moving from Window-eyes to NVDA
A very short tutorial telling you just what you need to know to do a lot of what
 
you did before.
 
Many people are apprehensive about switching to NVDA or any other screen-reader
 
from Window-eyes.  This tutorial will explain and demonstrate that such
 
apprehensions are largely based on misunderstandings. 
 
Before I discuss the misunderstanding that causes most of this apprehension, I'll
 
briefly discuss installing NVDA and changing the synthesizer used and speech
 
parameters.
 
NVDA has a talking installer.  run the file as you would any installation file. 
 
you may get a dialog asking if you want to run the file.  Use the command alt r
 
for run.  If you get a UAC prompt, answer alt y. 
Run narrator.  Then run the NVDA installer. 
when you run the installer, there will be a pause and then a bit of music will
 
play.  Not long after, the talking installer will run.  Unload Narrator at that
 
point.  return to the install dialog.
Tab through the dchoices.  Accept the license agreement and then tab to install. 
 
You will get other options but install is the one you want.
Don't stop using NvDA because of the voice.  A lot of people don't try NVDA because
 
of the voice.  As soon as you get it set up, I'll tell you how to change the
 
synthesizer used.
 
After NVDA is installed and running, it's time to learn how to change the
 
synthesizer. 
Issue the command control insert s.  Use either insert.  From now on, assume you
 
can use either insert unless I state differently.
A synthesizer selection dialog will open.
You will see a list of different possibly available synthesizers.  Choose SAPI 5. 
 
I know everyone has at least one SAPI 5 voice on their machine.  Up and down arrow
 
through the list and stop on SAPI five.  Press enter.
You will now hear another voice.  It may be the same voice you hear in Narrator. 
Now issue the command control insert v.
You are now in the voice selection and adjustment dialog. 
Up and down arrow to see what voices are available.  Stop on the one you want. 
Now tab through the dialog and change settings for the voice. 
Once you find a voice you want and tab through and set whatever you want such as
 
speed and punctuation, press the ok button. 
 
Now, let's continue with what I spoke of at the start of this tutorial.  The
 
misunderstanding that makes the switch seem daunting is that the user doesn't
 
realize that most of the commands he/she uses are Windows commands and program
 
commands and they won't change.
 
Consider the following examples:
Opening menus was and still is alt.  That's a Windows command to open menus in
 
programs.  It's the same no matter which screen-reader you use. 
Control o for open doesn't change.  Using the arrow keys to move in a document
 
doesn't change.  Tabbing through dialogs doesn't change.  Neither does how you move
 
in a list or a treeview or work with a combo box, and the list goes on. 
Screen-reader commands, many of which may change, such as read title bar, provide
 
access to information you can't get or can't get conveniently by using Windows or
 
program commands.  for example, read title bar.  In Window-eyes, the command is
 
control shift t.  In NVDA, it's insert t.  I am assuming throughout this tutorial
 
that you are using the default desktop layout in NVDA.  All commands are given in
 
that layout.  The title bar is something a sighted person looks at.  You can't move
 
to it with the pc cursor or application cursor, whatever you wish to call it,
 
because there is no need.  A sighted person can just see it.  So the screen-reader
 
has a command, read title bar.  That command is not a Windows nor a program
 
command.
 
Here are the screen-reader commands you will need to know to allow you to do a lot
 
of what you did before.
Read title bar, insert t. 
Time, insert f12. 
Read current Window, insert b.  In Window-eyes the command is control shift w. 
Read to end, insert down arrow.  Use the down arrow on the main keyboard.
Stop speech with control, as with screen-readers in general. 
Commands such as control home, control end, control left and right arrow are
 
Windows movement commands for moving in any standard edit field including word
 
processor edit fields.  None of them will change.
More screen-reader commands:
Screen review commands:
Note the pattern as I give these commands:
Read previous line, numpad 7. 
Read current line, numpad 8.
Read next line numpad nine.
You move in screen review to the previous or next line when you issue those
 
commands.  You can keep moving and reading until you get to the top or bottom of
 
the screen.
Read previous word, numpad 4.
Read current word, numpad 5.
Read next word, numpad 6.
Read previous character, numpad 1.
Read current character, numpad 2.
Read next character, numpad 3.
Note the pattern.  Read current is the key in the middle of each of these rows.
Move to and read previous is the key on the left. 
Move to and read next is the key to the right.
The lower the numbers the smaller the movement unit.  1 2 and 3 move by character. 
 
4 5 and 6 move by word.  Etc.
Here are two more important commands:
Jump to top of window, shift numpad 7.
Jump to bottom of window is shift numpad 9.
 
I've said top and bottom of Window but that's oversimplified.  It depends what kind
 
of review mode you are using.  I won't go into that to any extent in this very
 
short tutorial. 
that is the one you should be in usually.  Unless you change it, you will remain
 
there.  If you use another review mode, afterword, make sure you return to object
 
reviewIf you don't, you won't hear what you expect to hear at various times. 
To make sure you are in object review, issue the command numpad insert nummpad 1. 
 
When you are already in object review and can't move to another review mode, you
 
will hear no previous review mode.  You will then know you are in the right one. 
 
Or if you are returning from another review mode, when you hear object review, you
 
will know you are back in the right one.
I won't describe its use here, but screen review is similar not in commands, but in
 
how you review the screen to the Window-eyes cursor.  Object review is different
 
from any review mode available in Window-eyes.  It is valuable to know for various
 
uses.  Depending on how you use your computer, you may find it valuable or not.  I'm
 
simply making you aware that it is different and that you may want to learn it.
 
I'll provide a resource that teaches in great detail how to use NVDA.
This tutorial is to get you going using NVDA and to show you that even with the
 
little I will teach, you can still do a good deal of what you used to do.  You may
 
then learn more as you wish.
 
Believe it or not, that is just about all I will teach in this very short tutorial
 
but  I'll tell you a few more things.
Internet browsing:
When you are on a web page, quick navigation commands are almost identical whether
 
you are using NVDA or Window-eyes. 
Move by headings is h.  Skip blocks of links is n. 
Move to next button is b, 
Next combo box is c.
Next check box is x.
NVDA has an input help mode which is similar to what is in Window-eyes.  Insert and
 
1 on the main keyboard turns it on.  When you press a key or combination of keys
 
that might be a command, you will hear what the keys are and what, if any command
 
they execute.  This varies cdepending on where you are.
When in a browser that supports browse mode, typing a lot of individual letters
 
will give you information about what the keys do in browse mode.  I already gave
 
much of that information above but you may want to press a lot of keys using input
 
mode in a browser. 
 
To turn input mode off use the same command you used to turn it on, insert 1.
 
to learn more about NVDA, a popular tutorial is available at (insert URL.) 
On that page, you will see links to download different sections dealing with
 
different subjects.  You can also download the entire tutorial as a zip file.
 
There is also an e-mail list for NVDA users.  To join, send a blank message to this
 
 
I hope that this tutorial has removed much of your apprehension about switching to
 
NVDA.  Now, as you wish or need, you may consult the tutorial I gave a link to. 
 
NVDA is a powerful screen-reader and it will meet a lot of users needs as well as
 
JAWS or Window-eyes does.  I hope this very short tutorial gives you a good
 
foundation on which to build confidence that the transition should be much easier
 
than you may have thought and that it will help make it much more enjoyable.


Re: Window-Eyes Tutorials and Transition

Gene New Zealand <hurrikennyandopo@...>
 

Hi Kevin


Thanks for the link it gives food for thought of stuff that could be
added in if not already.


I will have a sus later on today i think reading some of the links i
have a good idea of what sort of stuff they would've put into the tutorials.


I knew the offer was coming to a end on it and thought some thing like
this was going to happen.


Gene nz

On 26/05/2017 6:41 AM, Kevin Huber wrote:
Hi Tonyy and all interested parties:

The link is:
www.gwmicro.com/window-eyes/migrate. You will find some good
tutorials on that page.
Kevin Huber


On 5/18/17, Brian Vogel <britechguy@gmail.com> wrote:
On Thu, May 18, 2017 at 12:20 pm, Tony Ballou wrote:

Is there a link out there for them?
I can't find anything obvious on the Freedom Scientific website under either
support or training with regard to being a new JAWS user coming from using
one screen reader to another.
--
Brian Version 1703, Build 15063.296, Home 64-bit



* * *Travel is fatal to prejudice, bigotry, and narrow-mindedness, and
many of our people need it sorely on these accounts. Broad, wholesome,
charitable views of men and things cannot be acquired by vegetating in one
little corner of the earth all one's lifetime.*

* ~ Mark Twain*
--
Check out my website for nvda tutorials and other blindness related
material at http://www.accessibilitycentral.net. Regardless of where you
are in New Zealand if you are near one of the APNK sites you can use a
copy of the NVDA screen reader on one of their computers. To find out
which locations or location is near to you please visit
http://www.aotearoapeoplesnetwork.org/content/partner-libraries |
Aotearoa People's Network Kaharoa -


Re: Window-Eyes Tutorials and Transition

Kevin Huber
 

Hi Tony:

I'm glad I could help.
Kevin Huber

On 5/25/17, Tony Ballou <cyberpro224@outlook.com> wrote:
Hi Kevin,


Thanks, Someone had said that there were some tutorials covering
migrating from window eyes to jaws up there however, none of us had the
link now we do. You never know what may come in handy around here.


Tony


On 5/25/2017 2:41 PM, Kevin Huber wrote:
Hi Tonyy and all interested parties:

The link is:
www.gwmicro.com/window-eyes/migrate. You will find some good
tutorials on that page.
Kevin Huber


On 5/18/17, Brian Vogel <britechguy@gmail.com> wrote:
On Thu, May 18, 2017 at 12:20 pm, Tony Ballou wrote:

Is there a link out there for them?
I can't find anything obvious on the Freedom Scientific website under
either
support or training with regard to being a new JAWS user coming from
using
one screen reader to another.
--
Brian Version 1703, Build 15063.296, Home 64-bit



* * *Travel is fatal to prejudice, bigotry, and narrow-mindedness,
and
many of our people need it sorely on these accounts. Broad, wholesome,
charitable views of men and things cannot be acquired by vegetating in
one
little corner of the earth all one's lifetime.*

* ~ Mark Twain*




Re: Window-Eyes Tutorials and Transition

Tony Ballou
 

Hi Kevin,


Thanks, Someone had said that there were some tutorials covering
migrating from window eyes to jaws up there however, none of us had the
link now we do. You never know what may come in handy around here.


Tony

On 5/25/2017 2:41 PM, Kevin Huber wrote:
Hi Tonyy and all interested parties:

The link is:
www.gwmicro.com/window-eyes/migrate. You will find some good
tutorials on that page.
Kevin Huber


On 5/18/17, Brian Vogel <britechguy@gmail.com> wrote:
On Thu, May 18, 2017 at 12:20 pm, Tony Ballou wrote:

Is there a link out there for them?
I can't find anything obvious on the Freedom Scientific website under either
support or training with regard to being a new JAWS user coming from using
one screen reader to another.
--
Brian Version 1703, Build 15063.296, Home 64-bit



* * *Travel is fatal to prejudice, bigotry, and narrow-mindedness, and
many of our people need it sorely on these accounts. Broad, wholesome,
charitable views of men and things cannot be acquired by vegetating in one
little corner of the earth all one's lifetime.*

* ~ Mark Twain*


Re: help pairing and using Xamarin live player with visualstudio on windows

Jessica D <jldail13@...>
 

Hi,
Can I have a tutorial on how to accomplish the task in my subject line?

I’ll need to use it later tonight?

On May 25, 2017, at 3:15 PM, Jessica D <jldail13@...> wrote:

 
 
Sent from Mail for Windows 10
 
From: Greg Wocher
Sent: Thursday, May 25, 2017 3:12 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] help pairing and using Xamarin live player with visualstudio on windows
 
Hello,
 
Here is the website where you can find the download links for the 
various versions of Visual Studio for the mac.
 
 
 
Regards,
 
Greg Wocher
 
 
On 5/25/2017 7:59 AM, Jessica D wrote:
> Hi,
> Can you please provide written instructions, on how to get setup, including any download links for software, that way I can ensure I'm going to the right place to download what I need.
> The last time I tried the preview, you couldn't read the start screen with voiceover.
> Is this still the case?
> Sent from my iPhone
>> On May 25, 2017, at 7:02 AM, Greg Wocher <gwocher@...> wrote:
>> 
>> Hello,
>> 
>> If you are saying that Visual Studio on the mac is inaccessible, you would be in error. The newest version of Visual Studio 2017 on the mac is quite accessible. I have it installed on my mac book air running the latest version of Sierra. The reason you have to use it is that the Visual Studio on mac is based on xamarin.
>> 
>> 
>> Regards,
>> 
>> Greg Wocher
>> 
>> 
>>> On 5/25/2017 3:28 AM, Brian's Mail list account wrote:
>>> If the Apple lot  have not rapped this app over the knuckles I'd ignore it myself. The only way to get these people to toe the line is to ignore them and use some other solution.
>>> Brian
>>> 
>>> Sent via blueyonder.
>>> Please address personal email to:-
>>> briang1@..., putting 'Brian Gaff'
>>> in the display name field.
>>> ----- Original Message ----- From: "Jessica D" <jldail13@...>
>>> Sent: Wednesday, May 24, 2017 5:33 PM
>>> Subject: [nvda] help pairing and using Xamarin live player with visual studio on windows
>>> 
>>> 
>>> Hi,
>>> 
>>> As some may have heard, Microsoft has released a new app.
>>> This app is called “Xamarin live player.”
>>> 
>>> It’s available for both ios and android.
>>> 
>>> I’m trying to pair visual studio  on Windows, which I’m running through VMwware fusion, to my iPhone so I can use the app, but everything I’ve found says that you have to use the mac version, which is totally enaccessible with voiceover.
>>> 
>>> What should I do?
>>> 
>>> Does this app work under Windows?
>>> 
>>> 
>>> Sent from Mail for Windows 10
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> 
>