The cursor POR always falls in the control that has the application focus. For controls having a visible text caret, the cursor moves with the caret. It rests on the character under a block caret or to the right of a line caret. For controls supporting item selection, the cursor moves with the active selection. It rests on the first character of the active item. For all other simple controls, the cursor is fixed on the first character of the one and only item in the control.

The application dictates what controls the cursor can reach. For example, the user cannot move the cursor to a static text label deemed non-focusable by the application. The application also determines the keys available for moving the cursor. Tab for instance, switches the widget focus among the focusable controls is most applications. The ReviewPerk makes one exception to the rule of the application defining all aspects of cursor navigation. When activated, the route pointer to cursor function moves the cursor to the location of the pointer, if possible.

	Important
	When the cursor changes location, the pointer is always automatically synchronized to it.

The pointer POR may be moved to any control in an application. As a result, the pointer provides a useful way of browsing the view presented by an application without affecting it. For example, a user can read through a window by pressing the next item key. When the user activates the next item function, the ReviewPerk moves the pointer POR to that item and then BasicSpeechPerk announces it. The user may repeat the operation until reaching the end of the view. The application focus, and thus the cursor POR, remain unchanged while moving the pointer in this manner.

A practical use of the pointer is to read information that is not deemed focusable by an application. For example, a program might display a static text label with instructions. In many applications, focus cannot be given to this type of control, making the help string inaccessible to blind and visually impaired users. A user can overcome this problem by using the pointer to navigate to the static text and read it.

	Important
	When the pointer changes location, the cursor is not automatically synchronized to it.

The keyboard bindings attempt to accomplish the following:

3.3.1. Preferred Keyboard Ergonomics

The following ergonomic criteria are considered in the selection of key bindings. The most ergonomic conditions are listed first. The conditions that create an absolutely non-ergonomic conditions are listed last. Conditions beyond the top 5 most ergonomic should be seriously evaluated before use in any design.

	Note
	On some, laptops there is only one of various modifier keys so it is nearly impossible to optimize for those keyboards unless one knows where the various modifier keys are located.

1. A two-key combination where both hands remain in home row position, and the keys are pressed with opposite hands (e.g. Ctrl-letter).
2. A three-key combination involving two modifier keys that can be pressed easily with one hand and a key that can be pressed with the opposite hand in home row position. Ranked in order of preference: Alt-Ctrl-letter, Alt-Shift-letter, Alt-CapsLock-letter, Shift-CapsLock-letter, Ctrl-CapsLock-letter, and NumPadInsert-Ctrl-letter. Alternatives in this category should be ranked favoring minimization of hand movement from the home row for the hand pressing the two modifier keys. Also, some juxtaposed shift keys require more movement from the home row than other non-juxtaposed modifier key combinations depending on the keyboard layout (e.g. Shift-CapsLock requires more movement from the home row on a ThinkPad than does Alt-CapsLock).
3. A two-key combination where one hand remains on the home row while the other is used to press a key on the same half of the keyboard as that hand's home row position (e.g. Capslock-F12).
4. A three-key combination involving two shift keys that can be easily pressed with one hand and a key that is located on the same side of the keyboard as that hand's home row position (e.g. Alt-Ctrl-F12).
5. A four-key combination involving three immediately juxtaposed shift keys that can be fairly easily pressed with one hand and a fourth key that is on the same side of the keyboard as the opposite hand's home row position (e.g. Ctrl-Alt-Shift-K).
6. A two-key combination that requires one hand to move to a side of the keyboard opposite its home row position (e.g. Insert-F11).
7. A three-key combination involving two modifier keys that can easily be pressed with one hand and requires the other hand to move to a side of the keyboard opposite its home row position (e.g. Alt-CapsLock-F1).
8. A four-key combination involving three modifier keys that can be pressed with one hand with modest difficulty and requires the other hand to move to a side of the keyboard opposite its home row position (e.g. Ctrl-Shift-CapsLock-F1).
9. A three-key combination involving two modifier keys that are difficult to press with one hand (e.g. Ctrl-Insert on a laptop).
10. A four-key combination involving three shift keys that are difficult to press with one hand.
11. Any five-key combination.

The screen reader key sequences trigger functions in the ReviewPerk, BasicSpeechPerk, DeveloperPerk, and DefaultDialogPerk. Every key sequence starts with the press of one or more modifier keys followed by the press of a non-modifier. The function bound to a sequence is activated on the release of the first of any of the held keys. The use of release as the trigger is intentional: it avoids problems with accidental repeat key presses (e.g. typomatic repeat for held keys, users with poor hand control). Scan codes are used instead of keysyms to ensure the position of keys in a binding remain the same across keyboard layouts, not their mnemonic associations.

The basic screen reader functions are bound to sequences following the Alt-Shift key map defined in the AltShiftPerk. The sequences in this map are intended to avoid conflicts with standard application key sequences and keyboard accessibility features. For instance, the use of standard modifiers prevents unintended interactions with the Sticky Keys keyboard accessibility feature.

The functions in the DeveloperPerk are bound to keys prefixed with Alt-CapsLock. The use of a separate modifier distinguishes them from most of the basic user keys. The key map for the developer functions is defined in the DeveloperPerk itself.

The LSR Perk Writer's Guide advises that custom Perks use CapsLock as a modifier. This alternative helps users distinguish between standard functions and application specific functions.

	Note
	Some bindings are exceptions to these rules. First, the user function stop now is bound to Ctrl alone. Second, the user functions in BookmarkPerk use CapsLock as part of their modifier. Third, the developer function toggle mute is bound to Left Ctrl-Right Ctrl.

All of the keys available in the current context are listed in the help dialog. The listing includes keys defined in the base screen reader Perks as well as custom Perks. See Section 4.2, “Help Chooser”.

The following table lists the functions provided by the ReviewPerk and the keys to which they are bound by the AltShiftPerk. All functions operate relative to the pointer POR unless otherwise indicated.

The following table lists the functions provided by the BasicSpeechPerk, the keys to which some are bound by the AltShiftPerk, and the functions in the ReviewPerk to which others are bound. All functions operate relative to the pointer POR unless otherwise indicated.

When navigating across items, the template for output is the same as the one used for active selection events. See Section 2.4.1, “Item Activation”.

The following table lists the functions provided by the BookmarkPerk and the keys to which they are bound.

The following table lists the functions provided by the SearchPerk and the keys to which they are bound by the AltShiftPerk.

The following table lists the functions provided by the DefaultDialogPerk and the keys to which they are bound by the AltShiftPerk.

The following table lists the functions provided by the DeveloperPerk and the keys to which they are bound.

Perks for particular applications can define additional key bindings. This document only covers the commands defined by the core Perks. Additional key bindings are described in the Linux Screen Reader User's Guide.