Full keyboard-driven interface

After reading an inspirational article. We're the first drivers from Jeff, I decided to use a keyboard and stay away from the pointer as much as possible.

But I noticed that for many applications, especially on WEB, this is not easy.

I also tried to incorporate this feature into my own pet projects and realize that it takes a huge amount of effort to create a user interface.

I used to work with a fully "keyboard-driven" windows application, and it was easy to work with as soon as you hung it. Customers, especially data entry operators, just liked it ...

I wonder if this is possible with sophisticated user interface applications, especially on the Internet? Will it be justified?

+5
source share
7 answers

This is something we should definitely strive for, absolutely - although you are right with the help of web interfaces that it can be especially difficult. All this relates to focus management and processing of keyboard events, which require additional time and effort on the part of the developer, but there are many people (and not just disabled ones) who will thank you for the care you are sure that your web projects, at least are practically affordable and suitable for use without the need for a mouse.

, , W3C Web Accessibility. .

- , , , , .

- . , , "" XHTML , .

(, , ? : , , , , , , , . , , , - .)

, , , " " , - ​​, , , , . , , - - , , , , .

+2

, . -, (, , , ..), , , .

, , / youtube , flash/ajax, . .

+5

. conkeror , emacs , Linux, Awesome, ratpoison, xmonad stumpwm.

+4

, . - " " , , , , [ , ] , ( call-, , ).

, , - ( ), , .

, , , , , .

+3

, . ( - , .) , . , : " ...", .

, , . , ( , , - .)

(call-center-type) , FoxPro, Windows. , POS- Windows.

( ), , , .

+2

:

  • -, , ( , , ).
  • -, " " , , , ( , . , ).

Google/vim - , , , . , . , .

+2
source

One cool site that really only supports the keyboard interface , the keyboardr user interface makes keyboard navigation very easy.

+1
source

All Articles