>In my eyes every software that is not usable without a mouse is a bad thing. At least proper use of menu shortcut, a meaningfull tab order and CTRL C|V|X should be provided. Enter should read data entry form, esc should close it. It's much faster to run with tab from field to field then to use a mouse.
>
>But I'm on a minority.
>AFAIK only 3% of all users realy use keyboard and keyboard shortcuts for navigation.
>
>(There is an other 3% that uses fruits as computer, on those the whole idea of keyboard navigation is uncommon)
>
>My advise is (descending order of priority)
>-provide taborder. It hurts not to much, you can use those mouse interface. (could be frustrating if you miss click)
>-provide menu shortcuts
>-provide default / cancel buttons
>-provide button shortcuts
>-provide label shortcuts
>
>I do not provide button and label shortcuts for each and every form, only for forms that have heavy use (and not to many shortcuts).
>
>The backdraw is that you can not use keyboard with toolbars. You need to double all toolbars with menus.


Share this views 100% (aldough that is as they say 'old fashion')

When I wrote my accs.app and deployed it here, I was training users by literally hiding mouse behind monitor.
They were confused at first but then would pick up easily '4-5 keyb.keys for everything' style of interface and now they are flying arround the system.
You should see speed operators are keying inn entries. But that is backward, outdated, networked VFP application!

Then I go to pay my ADSL bill and see latest & greatest technology in action.

Shiny web based billing application;
Klunk mouse, klunk keyboard, klunk mouse , klunk keyboard, klunk combo to open, klunk listbox...
Try... Catch...And finally .... Print button! {g}

But of course I missed point in new age computerisation - It does not matter how long it takes for an entry to complete
what is important is that IT manager can easily deploy application!

Cheers :)
Sergio