I'm not sure what you are creating. You speak of a chart and that it is eight pages long. Evidently, you will send it to all who request it. I'll probably write off list and do so. But I really don't think anything that
long is needed nor desirable to provide a transition. In my opinion, the following should be discussed not in a chart, but in a document:
How to set speech parameters including synthesizer, reading speed and punctuation, how to open the menu. How to unload NVDA and how to run it. A brief discussion of the talking installer. Not much, but that you will be asked
if you want to create a portable version or install the screen-reader.
Aside from that, the following commands should be briefly stated:
Read current line. Read previous line, read next line.
Read current word, next word and previous word. The same with characters. the pattern may be very briefly noted.
Read title bar and that pressing the command twice quickly will spell the title bar. Pressing it three times copies the title bar text to the clipboard.
Very little discussion of browse mode need be done. the commands are very similar or perhaps just about identical. It should be explained how to make each link appear on its own line. It should be explained how to stop automatic
switching between browse and function mode and how to switch to words to notify the user when he is in browse mode or focus mode.
Screen review may be described but it might be better to refer the user to something like the chapter in the tutorial Joseph Lee did on the subject. It is still available on line. Object review as well can be referred to a
chapter in the tutorial.
A brief discussion of the NVDA users' list should be given and the syntax to join.
I wouldn't do anything other than what I've mentioned unless I happen to think of something that I've forgotten in this disscussion but even if I did, I would do very little more. This document is to provide a transition, not
to teach Windows nor NVDA in detail. It's purpose is to allow Window-eyes users to be able to use NVDA and refer them to resources for teaching such things as object navigation. If it is too long and detailed, it may discourage some people from making the
transition. The purpose is to allow basic NVDA use in as short a time and with as little to learn as possible.
I should add one more thing that should be mentioned. It should be pointed out that input help is available and that you use it in the same way as in Window-eyes. I believe the command is the same but whether it is or not,
the user should be told the following:
To go into input help, use insert 1 meaning 1 on the main keyboard. Either insert may be used. An example of use may be given. When in browse mode, for example, every browse mode letter such as h for heading, b for button,
etc. will name the command when pressed. the user may, if he/she wishes, push every letter of the alphabet to see what the quick navigation commands are. they are almost identical to Windo-eyes but this will allow the user to be aware of any differences
in an engaged and interactive, not a passive way.
Gene
----- Original Message -----
Sent: Wednesday, May 24, 2017 8:59 PM
Subject: Re: [nvda] Window-Eyes Tutorials and Transition
Hi
Food for thought. I do have a full list of windows commands i would have to check for windows 7, 8 and 10 that can be inserted into a page if its a webpage.
If you want them i can drop box them to you.
I know what you mean by 8 pages and counting the object navigation takes a little getting used to and i do not think there is some thing like that in other screen readers.
I thought some one said the idea was burrowed from voice over?
Text review is pretty good as it lets you read stuff that you can not with the system focus, but people have to get there head around that you can review a whole page without say moving the carrot cursor but you can not edit with it.
Gene nz
On 25/05/2017 1:35 PM, Tony Ballou wrote:
howdy Mate,
I've started working on the chart and would like your input and feedback on it so far. Because of it's length, 8 pages and probably counting, it is far too long to post here. I'm basically concentrating on the things I'm totally familiar with in both screen
readers and leaving the review and object navigation modes for another time. I for now just want to give anyone who is coming from window eyes to NVDA enough ammunition to get going and begin to feel comfortable with using the program.
In my own personal experience, I learned NVDA by knowing all of the basic windows commands, and studying the help documentation that came with it. And as a new weapon of choice, I've added the accessibilitycentral.net website to my arsenal of darn near all
things NVDA.
Contact me off list at
cyberpro224@... if you want to give this a go.
Tony
On 5/24/2017 1:49 PM, Gene wrote:
I don't think describing how to use object navigation is a good idea in this context. Giving resources for those interested, such as the tutorial chapter done by Joseph Lee would probably be a much better idea in terms of use
of those creating such materials' time. Also, the user in most cases, doesn't have to know about object navigation when first making the transition. Better not to overload the user with a difficult concept to teach such as this at the outset.
Using screen review mode can easily be explained in a work such as you are creating and it must be emphasized that after using screen review, the user must return to object navigation mode because if this isn't done, NVDA won't
work properly in various contexts. So just explaining how to enter screen review, numpad insert numpad 7 executed until you hear that there are no more review modes, then give the review commands to read current line, move to and read next line, etc. could
be given. How to move the mouse and click it could also be given.
then how to return to object navigation, numpad insert 1 repeated until there are no more review modes would be done when finished.
It is better not to give Window-eyes and NVDA equivalent commands in the context of screen-review. There are many equivalent commands but going into screen-review and returning to object navigation has no equivalent in Window-eyes.
this might be pointed out. As for movement commands, the Window-eyes user will recognize equivalents such as read current line without the tutorial pointing out the actual Window-eyes command.
The listener or reader will know what is being discussed when the NVDA commands are given.
Gene
----- Original Message -----
Sent: Wednesday, May 24, 2017 11:32 AM
Subject: Re: [nvda] Window-Eyes Tutorials and Transition
Howdy Mate,
That's what I was thinking also. If there are any other window eyes users out there whether they be former like myself or current who would like to help me with this endeavor, come on in, because there's loads I don't know. I'll try to have some basic
ground work for the sheet up for all of you to look at by tomorrow.
Tony
On 5/23/2017 5:09 PM, Gene wrote:
You can't compare the Window-eyes mouse pointer to object navigation. You can give commands in NVDA for read current line, previous line, next line, and similar review commands
But you have to learn object navigation on its own.
Screen review should be easy to teach since it is similar. There are different commands but it's similar in movement and concept.
Commands such as read to end can be given. As for browse mode, commands are either similar or identical in Window-eyes or NVDA. I haven't used Window-eyes to any extent for years but just listing NVDA commands
such as move by heading, h, skip blocks of links, n, move to next button, b, etc. should be sufficient. It should be explained how to stop automatic going into browse mode and how to change audio indications to words.
As I more or less said earlier, most of what most users do is use program commands, Windows commands, and quick navigation commands.
In my opinion, that is the first important point to be made.
Maybe I'll try writing something.
Gene
----- Original Message -----
Sent: Tuesday, May 23, 2017 3:42 PM
Subject: Re: [nvda] Window-Eyes Tutorials and Transition
Hi,
Give me a couple of days, Let me see what I can come up with
Tony
On 5/23/2017 2:38 PM, Brandon Cross wrote:
Yeah, agreed, I tried window eyes briefly, not enough to get a grasp on it, but if anyone did know both intimately, it would be a worthwhile venture to make a little cheat sheet, or more if needed. An article of sourts maybe.
