Date   

Re: is new NVDA released?

Quentin Christensen
 

As others have said, the release candidate is out.  If we don't find any really big bugs in that, then the final 2017.2 will look identical be out in a week or so.  If we do encounter any showstopping bugs, then we'll endeavour to fix them, put out 2017.2rc2 and reset for another week or so.

Kind regards

Quentin.

On Thu, May 25, 2017 at 1:35 AM, Brian's Mail list account <bglists@...> wrote:
This sounds decidedly odd being mixed chines and English.

Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "rowen brian" <manchen0528@...>
To: <nvda@nvda.groups.io>
Sent: Wednesday, May 24, 2017 12:22 PM
Subject: 答复: [nvda] is new NVDA released?


No

发送自 Windows 10 版邮件应用

发件人: Dennis L
发送时间: 2017年5月24日 11:58
收件人: nvda@nvda.groups.io
主题: [nvda] is new NVDA released?

Hi, is the new NVDA released??









--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: nvda 2017.2 rc1

Quentin Christensen
 

Hi everyone,

Just to follow up on the comments re the NV Access site.  Yes, we are aware it has outgrown its current setup.  As many of you know, we are (slowly) going through a rebranding (same name, new logo), and part of that is a new website.  The new site is currently being worked on and unfortunately isn't ready yet.

I'll be sure and pass on when the new site is ready to explore!

Kind regards

Quentin.

On Wed, May 24, 2017 at 12:52 PM, Brian Vogel <britechguy@...> wrote:
On Tue, May 23, 2017 at 07:33 pm, David Tanner wrote:
Could someone please post the link to the new release candidate I can't seem to find it anywhere.

 See:  https://nvda.groups.io/g/nvda/message/18634 
--
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

 

 




--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: The latest rc1 download clarification

Quentin Christensen
 

Hi Lenron,

For NVDA 2017.2 rc1:


Kind regards

Quentin.

On Tue, May 23, 2017 at 7:56 PM, Brian's Mail list account <bglists@...> wrote:
I hhave no links to emails. I use ofline email.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Lenron" <lenron93@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, May 23, 2017 8:53 AM
Subject: Re: [nvda] The latest rc1 download clarification



Would you happen to have the link to the email. I need to grab it from?

On 5/23/17, Brian's Mail list account <bglists@...> wrote:

Basically its certainly working.
 When you click the link in the email you go to the blog post which
describes the changes and has a link to the normal download site.
 This then presents you with an option to donate, If you select  not this
time there, ust below the donate options, you just enter your email chooses

if you want email updates then the download link is active and it works fine

from there. its exactly the same as with the full version
.
They like to track downloads  for  data purposes,which is why they ask for
the email and do not promote downloads from the snapshot pages. Of course if

you go to the snapshot page, you get a version of the RC but not the release

version of it, ie it still has error noise etc.
 As the RC is meant to be exactly like the release it uses the same download

procedure.

I hope this helps new people. Its a slight annoyance to go via the donation

and registration page but no passwords are needed and you can opt  out of
emails and you do not have to donate. In my view, simply moving the  not now

link to above the donation options would have been better from the logical
layout point of view.

Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.







--
Lenron Brown
Cell: 985-271-2832
Skype: ron.brown762










--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: NVDA RC1

Quentin Christensen
 

Hi everyone,

I wasn't aware of a problem with the download server but in any case, it certainly seems to be working at the moment.  Could those who were having problems (or anyone else) please let me know if you are still having difficulty downloading the release candidate?

The snapshots page (where you can download not only the release candidate builds, but also next and master builds), is here: https://www.nvaccess.org/files/nvda/snapshots/

Kind regards

Quentin.

On Tue, May 23, 2017 at 5:31 PM, Brian's Mail list account <bglists@...> wrote:
That would certainly do it but this morning at least I auto downloaded a master snap from that site so its working again I'd suggest.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Gene" <gsasner@...>
To: <nvda@nvda.groups.io>
Sent: Monday, May 22, 2017 5:18 PM
Subject: Re: [nvda] NVDA RC1


When I go to the NVDA snapshots page, I get a standard browser message that the site can't be found.  There is evidently a problem with the site that hosts snapshots and, presumably, the RC versions.

I'm not sure whom you contact to alert them of the situation.  I suspect they already know.

Gene







--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: Nvda 2017-rc1 up for testing.

Quentin Christensen
 

The page at  https://www.nvaccess.org/post/nvda-2017-2rc1-released/ has just the highlights and the link to download the release candidate: https://www.nvaccess.org/download?nvdaVersion=2017.2rc1

For the full "What's new", run the release candidate itself and go to NVDA menu, help, what's new.

Kind regards

Quentin.

On Tue, May 23, 2017 at 3:27 AM, The Wolf <hank.smith966@...> wrote:
all I found was a link to download the rc1 and it gave the main highlights of the new version I didn't see the actual change log, perhaps I am missing it?



On 5/22/2017 10:21 AM, Lino Morales wrote:
Same place as NVDA.

www.nvaccess.org/


On 5/22/2017 9:26 AM, Don H wrote:
Where do you get the Rc1 download?

On 5/22/2017 3:10 AM, Brian's Mail list account wrote:

Messag from Jamie in case nobody saw it yet..
Hi all,

NVDA 2017.2rc1 has just been released for testing. Please see this post for details.

Thanks to everyone who helped to make this release possible.

Jamie

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Nvda-devel mailing list
Nvda-devel@...et
https://lists.sourceforge.net/lists/listinfo/nvda-devel

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.


















--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: there is a better driver for the hims smartbeetle

 

Hi,
If you've attached it, it got lost. Also, I believe NV Access has experimented with this driver, and last time I checked, they had mixed results.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of P. Otter
Sent: Thursday, May 25, 2017 11:30 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] there is a better driver for the hims smartbeetle

no, i had replaced the driver after that all was working properly.

before i've tryed but that was the same old problem, it was not possible to go back with the left scrol key.

i was hopeful there was a better driver in this new version but there was'nt.

so i have deleted the original version of HansoneConnect.dll and replaced it with my version.

here it is.



Op 26-5-2017 om 07:20 schreef Joseph Lee:
Hi,
And this was without replacing the driver?
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of P.
Otter
Sent: Thursday, May 25, 2017 10:18 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] there is a better driver for the hims smartbeetle

hi i've already tested it because i have a smart beetle and it works
great with version 2017.2 rc1

can i send you the driver?

cheers

paul otter



Op 26-5-2017 om 06:24 schreef Joseph Lee:
Hi,
Can you test your scenario after using NVDA 2017.2 RC1 for a while without replacing the driver in question? Thanks.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of P.
Otter
Sent: Thursday, May 25, 2017 9:22 PM
To: nvda@nvda.groups.io
Subject: [nvda] there is a better driver for the hims smartbeetle

hello, there is a better version for the hims braille displays like the smartbeetle.

the version that is delivered with nvda there are problems in it.

when you press scroll down, the display will go to the right, but when i press theleft scrol up, nothing happens.

this is one of the examples i want to mention.

per haps it is possible that the better driver will be implemented in the new version of nvda.

i'll send here the new driver that works nice.

now, every time i update nvda i have to replace the file
HansoneConnect.dll

if you want, i can send you the file.

cheers

paul otter















Re: there is a better driver for the hims smartbeetle

P. Otter
 

no, i had replaced the driver after that all was working properly.

before i've tryed but that was the same old problem, it was not possible to go back with the left scrol key.

i was hopeful there was a better driver in this new version but there was'nt.

so i have deleted the original version of HansoneConnect.dll and replaced it with my version.

here it is.



Op 26-5-2017 om 07:20 schreef Joseph Lee:

Hi,
And this was without replacing the driver?
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of P. Otter
Sent: Thursday, May 25, 2017 10:18 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] there is a better driver for the hims smartbeetle

hi i've already tested it because i have a smart beetle and it works great with version 2017.2 rc1

can i send you the driver?

cheers

paul otter



Op 26-5-2017 om 06:24 schreef Joseph Lee:
Hi,
Can you test your scenario after using NVDA 2017.2 RC1 for a while without replacing the driver in question? Thanks.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of P.
Otter
Sent: Thursday, May 25, 2017 9:22 PM
To: nvda@nvda.groups.io
Subject: [nvda] there is a better driver for the hims smartbeetle

hello, there is a better version for the hims braille displays like the smartbeetle.

the version that is delivered with nvda there are problems in it.

when you press scroll down, the display will go to the right, but when i press theleft scrol up, nothing happens.

this is one of the examples i want to mention.

per haps it is possible that the better driver will be implemented in the new version of nvda.

i'll send here the new driver that works nice.

now, every time i update nvda i have to replace the file
HansoneConnect.dll

if you want, i can send you the file.

cheers

paul otter














Re: Focus Highlighter

Quentin Christensen
 

Hi William,

Focus Highlight should just work without needing too much interaction (it is a purely visual indication on screen of where the focus currently is).

The following colors are used by this addon:

  • Green jagged line, to indicate the navigator object.
  • Red thin rectangle, to indicate the focused object/control.
  • Red thick rectangle, to indicate when navigator object and focused object are overlapping.
  • Blue thick rectangle with thin slashes, to indicate NVDA is in focus mode, i.e. key types are passed to the control.
Otherwise, what problems are you having with it?

Kind regards

Quentin.

On Tue, May 16, 2017 at 6:24 PM, willmac@... <willmac@...> wrote:
Hi,

I am presently trying to use the Focus Highlighter Add-on in a sort of haphazard way.
Can anyone help me to use it in a more constructive way to get the most out of the add-on.
Regards,

William




--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: Has NVDA 2017.2 RC1 been made available?

Quentin Christensen
 

Hi everyone,

Apologies for my own absence.  NVDA 2017.2 RC1 is now out.  See here for the notes and to download: https://www.nvaccess.org/post/nvda-2017-2rc1-released/

Kind regards

Quentin.

On Sun, May 14, 2017 at 6:23 AM, Kevin Cussick via Groups.Io <the.big.white.shepherd@...> wrote:
Hi,   rc1 should come out real soon.

On 13/05/2017 00:52, Brian Vogel wrote:
On Fri, May 12, 2017 at 04:19 pm, Andre Fisher wrote:

    Actually, these changes are already part of Master snapshots. It is
    expected that the release will come out this month.

OK.  I'm just used to seeing an RC1 (and, on rare occasions, an RC2) come out prior to the main release and that post made me think I might have missed it when I was on vacation.
--
*/Brian/*

*//**/The real art of conversation is not only to say the right thing in the right place but to leave unsaid the wrong thing at the tempting moment./*

*/~ Dorothy Nevill/*








--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: there is a better driver for the hims smartbeetle

 

Hi,
And this was without replacing the driver?
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of P. Otter
Sent: Thursday, May 25, 2017 10:18 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] there is a better driver for the hims smartbeetle

hi i've already tested it because i have a smart beetle and it works great with version 2017.2 rc1

can i send you the driver?

cheers

paul otter



Op 26-5-2017 om 06:24 schreef Joseph Lee:
Hi,
Can you test your scenario after using NVDA 2017.2 RC1 for a while without replacing the driver in question? Thanks.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of P.
Otter
Sent: Thursday, May 25, 2017 9:22 PM
To: nvda@nvda.groups.io
Subject: [nvda] there is a better driver for the hims smartbeetle

hello, there is a better version for the hims braille displays like the smartbeetle.

the version that is delivered with nvda there are problems in it.

when you press scroll down, the display will go to the right, but when i press theleft scrol up, nothing happens.

this is one of the examples i want to mention.

per haps it is possible that the better driver will be implemented in the new version of nvda.

i'll send here the new driver that works nice.

now, every time i update nvda i have to replace the file
HansoneConnect.dll

if you want, i can send you the file.

cheers

paul otter










Re: there is a better driver for the hims smartbeetle

P. Otter
 

hi i've already tested it because i have a smart beetle and it works great with version 2017.2 rc1

can i send you the driver?

cheers

paul otter



Op 26-5-2017 om 06:24 schreef Joseph Lee:

Hi,
Can you test your scenario after using NVDA 2017.2 RC1 for a while without replacing the driver in question? Thanks.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of P. Otter
Sent: Thursday, May 25, 2017 9:22 PM
To: nvda@nvda.groups.io
Subject: [nvda] there is a better driver for the hims smartbeetle

hello, there is a better version for the hims braille displays like the smartbeetle.

the version that is delivered with nvda there are problems in it.

when you press scroll down, the display will go to the right, but when i press theleft scrol up, nothing happens.

this is one of the examples i want to mention.

per haps it is possible that the better driver will be implemented in the new version of nvda.

i'll send here the new driver that works nice.

now, every time i update nvda i have to replace the file HansoneConnect.dll

if you want, i can send you the file.

cheers

paul otter









how to prevent screen readers from saying search provider in Firefox when typing in address bar

Dennis L <dennisl1982@...>
 

Hi, how do I prevent NVDA or any screen reader from  saying something like m.yahoo when I start to type an address into the address bar?  I would love to get rid of all search engines but I don’t see how this is possible I looked under search.  I’m using latest Firefox  any help is appreciated.


Re: there is a better driver for the hims smartbeetle

 

Hi,
Can you test your scenario after using NVDA 2017.2 RC1 for a while without replacing the driver in question? Thanks.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of P. Otter
Sent: Thursday, May 25, 2017 9:22 PM
To: nvda@nvda.groups.io
Subject: [nvda] there is a better driver for the hims smartbeetle

hello, there is a better version for the hims braille displays like the smartbeetle.

the version that is delivered with nvda there are problems in it.

when you press scroll down, the display will go to the right, but when i press theleft scrol up, nothing happens.

this is one of the examples i want to mention.

per haps it is possible that the better driver will be implemented in the new version of nvda.

i'll send here the new driver that works nice.

now, every time i update nvda i have to replace the file HansoneConnect.dll

if you want, i can send you the file.

cheers

paul otter


there is a better driver for the hims smartbeetle

P. Otter
 

hello, there is a better version for the hims braille displays like the smartbeetle.

the version that is delivered with nvda there are problems in it.

when you press scroll down, the display will go to the right, but when i press theleft scrol up, nothing happens.

this is one of the examples i want to mention.

per haps it is possible that the better driver will be implemented in the new version of nvda.

i'll send here the new driver that works nice.

now, every time i update nvda i have to replace the file HansoneConnect.dll

if you want, i can send you the file.

cheers

paul otter


In-Process May 26

Quentin Christensen
 

Hi everyone,

NVDACon, NVDA 2017.2 RC1, a new training module about to drop and the number 42? Grab your towel, it's time for another edition of In-Process! https://www.nvaccess.org/post/in-process-26th-may-2017/

In other news, sorry I haven't been around much the past week or so, I'll have a read back through the posts but give me a shout if there's anything I missed that I can help with.

Regards

Quentin.

--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


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

 

Hi,

As part of Project Contact Lenses, I’m looking into some technical documentation on Window-Eyes, specifically scripting.

Cheers,

Joseph

 

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

 

Hi Gene,

 

Cool!  Looks like we're going to have a couple of things up about making the transition, and that's a heck of a lot better than one. This idea has taken off. Any other requests LOL! Just kiddin'!

 

Tony

 

On 5/25/2017 7:54 PM, Gene wrote:

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

Tony Ballou
 

Hi Gene,


Oh yeah, if you stumble over that step, that sure can happen to you, I forgot about that one.  


Tony

On 5/25/2017 7:52 PM, Gene wrote:
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 Gene,


Cool!  Looks like we're going to have a couple of things up about making the transition, and that's a heck of a lot better than one. This idea has taken off. Any other requests LOL! Just kiddin'!


Tony


On 5/25/2017 7:54 PM, Gene wrote:
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: 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@...> 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: vocalizer voices for NVDA

Andy
 

Try their other site, www.blindbargains.com

Andy

----- Original Message -----
From: "Don H" <lmddh50@comcast.net>
To: <nvda@nvda.groups.io>
Sent: Thursday, May 25, 2017 4:08 PM
Subject: [nvda] vocalizer voices for NVDA


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?