RE: The top three big problems
- From: "Chris Hofstader" <chris.hofstader@xxxxxxxxxxx>
- To: <programmingblind@xxxxxxxxxxxxx>
- Date: Sun, 14 Oct 2007 08:04:42 -0400
If the features one executes also have menu items to perform the same task
and the menu item includes the keystroke (for example, if one goes to
File/New Tab Control in Internet Explorer, a screen reader will read the
text but also say "CTRL+T) and, after a few times of using it, people tend
to remember the keystrokes associated with features they use often but can
still use the menus for things they cannot remember.
Also, using keystroke assignments that are, first and fore mostly fairly
standard (for example, in virtually all Windows programs, CTRL+C is Copy,
CTRL+V is Paste and CTRL+X is cut) and, because VisualStudio is the closest
thing to a standard editor used by us blinks, I would recommend using as
many VS key bindings as possible to make the transition from one to the
other as easy as possible.
Finally, for as long as I can remember (more than 20 years), emacs has had
an "apropos" mode. In emacs the keystroke to get into it is Meta-X followed
by typing apropos (not my favorite part of the interface) but, once in the
mode, a user can type the beginning of a command they are pretty certain
exists but can't remember its name and emacs will provide a set of
suggestions based upon context and such and the key bound to the feature.
The user can hit ENTER on the command and, if they do it often enough, they
will remember the keystroke. GG and I had planned on adding this to JAWS
years back but it never made the short list of features and has probably
been forgotten since.
Hope this is helpful,
cdh
-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Andreas Stefik
Sent: Saturday, October 13, 2007 5:11 PM
To: programmingblind@xxxxxxxxxxxxx
Subject: Re: The top three big problems
Do you folks have any ideas as to what would make it easier to
remember all the keystrokes? This type of stuff would be really easy
to add in to my compiler, so suggestions are very welcome!
Andy
On 10/13/07, Andy B <a_borka@xxxxxxxxxxxxx> wrote:
> Good memory I guess... I am in VS2005 almost 50% of the day so have some
> experience with it. Did I remember something wrong?
>
>
>
> -----Original Message-----
> From: programmingblind-bounce@xxxxxxxxxxxxx
> [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Dale Leavens
> Sent: Saturday, October 13, 2007 4:27 PM
> To: programmingblind@xxxxxxxxxxxxx
> Subject: Re: The top three big problems
>
>
> I want to know how you can possibly remember all those key strokes and the
> sequence.
>
>
> Dale Leavens, Cochrane Ontario Canada
> DLeavens@xxxxxxx
> Skype DaleLeavens
> Come and meet Aurora, Nakita and Nanook at our polar bear habitat.
>
>
> ----- Original Message -----
> From: "Andy B" <a_borka@xxxxxxxxxxxxx>
> To: <programmingblind@xxxxxxxxxxxxx>
> Sent: Saturday, October 13, 2007 2:04 PM
> Subject: RE: The top three big problems
>
>
> The below is easily possible in vs2005 at least. If you go into the
> settings, under bu8ild options somewhere (I forgot exactly since I haven't
> been there in a long time), there is a choice to allow the compiler to
show
> the error list/window upon build/compile failure. When you are in this
list,
> hitting enter on a error message actually instantly jumps you to the code
> line where the error is and highlights it in a certain color. I know the
> color doesn't help a total blind person, but at least jaws jumps to the
> exact line being complained about. All you have to do now is hide the
error
> window (alt shift h), fix the line of code and then press f5/control f5/f6
> to rebuild again...
>
>
>
>
> 2. The usability.
>
> A programming environment should be made thinking to the blind
programmers
> needs also, and a blind programmer should be able to configure the
> environment as he wants.
>
> For example, what does a sighted programmer after he runs a program in
> Eclipse or VS.net and it gives an error?
> I think that he looks too se what was the error.
> So, for the sighted programmer is easy to take a look in the wanted pane,
> but a blind programmer should be able to configure the application so
after
> it runs the program and gives the error, the focus to be automaticly
placed
> in the errors pane. And he should be able to move the focus to the code
pane
>
> immediately.
>
> __________
> View the list's information and change your settings at
> //www.freelists.org/list/programmingblind
>
>
> __________
> View the list's information and change your settings at
> //www.freelists.org/list/programmingblind
>
> __________
> View the list's information and change your settings at
> //www.freelists.org/list/programmingblind
>
>
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
__________ NOD32 2590 (20071012) Information __________
This message was checked by NOD32 antivirus system.
http://www.eset.com
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
Other related posts:
