Re: The top three big problems

  • From: "Marlon Brandão de Sousa" <splyt.lists@xxxxxxxxx>
  • To: programmingblind@xxxxxxxxxxxxx
  • Date: Sat, 13 Oct 2007 19:56:03 -0300

The key for doing this follows:
Make navegation for blinds as randomic as it is for sighted people.
This can be achieved by setting keystrokes which will simulate quick
visual navegation. It would also be good if all those keystrokes were
put in a menu. People will use more one or another feature deppending
on what they're trying to do. The only way of letting them know what
tools are available to use is putting all of them in menus, properly
grouped and defined (with its corresponding keystrokes being
anounced). Then the more used features keystrokes will be memorized
with the use.
As for debugging I still do think a command line aproach is good, I
can't imagine other possible solutions for now.

When you say "I wrote a program that crashed Windows," people just
stare at you blankly and say "Hey, I got those with the system, for
Linus Torvalds
View the list's information and change your settings at 

Other related posts: