- From: Charles McCathieNevile <charles@w3.org>
- Date: Wed, 28 Apr 1999 11:54:01 -0400 (EDT)
- To: Irene.Vatton@inrialpes.fr
- cc: Amaya List <www-amaya@w3.org>
On Wed, 28 Apr 1999 Irene.Vatton@inrialpes.fr wrote: It will be the case in the next release 2.0. ALT will be mandatory for AREAs. Cool > Also, it would be nice to have a default configuration which provides > keyboard shortcuts for most functions and a way of doing everything including > changing the active sub-window and selecting text via the keyboard The problem is to find out the right list of shortcuts. That could be experimented out of the team. We're ready to publish a list of files amaya.keyboard or amaya.kb. By the way, we plan the replace in the Windows versions the ESC key by the F2 key to select enclosing elements. What do you think? I don't use windows enough to know for certain, but it seems like a good idea. (It is easy enough to reconfigure it anyway). It would be nice to have the option of selecting the 'windows' interface or the 'unix' interface keyboard file, for people who are swapping across platforms. > > All the menu functions are accessible from the keyboard via the F10 (linux) > or ALT (windows) keys, and in Linux using fvwm2 I can move the mouse cursor > around using ctrl-shift and the arrow keys, but haven't found a way to make > clicks from the keyboard. For a blind user, moving the mouse around to find > things is difficult anyway - if it were more like the dialog boxes, where I > can use TAB, arrow keys and SPACE to do everything it would be better. We're looking at this problem, but we're not sure to fix it for the end of this week. Irene. Charles --Charles McCathieNevile mailto:charles@w3.org phone: +1 617 258 0992 http://www.w3.org/People/Charles W3C Web Accessibility Initiative http://www.w3.org/WAI MIT/LCS - 545 Technology sq., Cambridge MA, 02139, USA
Received on Wednesday, 28 April 1999 11:54:09 UTC