13 (71)Copyright © Nokia Mobile Phones 2000. All rights reserved.4. INTERACTIONThe communicator UI is based on CBA, Menu and keyboard usage. Keep in mind that there is no generic pointingdevice in the UI, so the controls should not be ’clickable.‘ The user should be able to use the device by keyboard andthe Menu without the CBA, if he or she so wishes.ButtonFunctionalityTab Changes the focus between windowsTab -> focus to rightShift+Tab -> focus to leftEnter Default command (Button1 underlined) in CBA orCarriage Return (CR) in editorsEsc Application specificUp/Down Arrows key Application specificRight/Left Arrows key Application specificViewsTab Opens a control (e.g. choice list -> text list box)Enter (when control notopened, e.g. choice list)Opens a control (e.g. choice list -> text list box)Enter (when control opened,e.g. text list box)Optional default command = Button1 underlined (e.g.OK in text list box)Esc Cancels (clears a dialog box and any changes made)Up/Down Arrows key Changes the focus from the one control to anotherRight/Left Arrows key Focuses on the active controlDialogsTable 3: Recommendations for interaction.4.1 Enter keyIn editors, the Enter key inserts a new line. Elsewhere, Enter performs the action described by the underlined defaultcommand (Button1).4.2 Menu buttonThe Menu button activates and deactivates the Menu (see chapter 7).4.3 Esc KeyThe Esc key always allows the user to cancel the current action. This is important, because the Cancel command isoften unavailable in the CBA.When in a dialog, the dialog and any changes made can be cleared using the Esc key.4.4 Tab keyThe Tab key should move the focus between the windows, but there should always be some other way of movingbetween views, ideally using the Arrows key, e.g. the left and right keys may change the window.If the Arrows key cannot be used for navigating between windows, a command should be available in the CBA.