y 

n/a 

n 

Required 

_ 

_ 

_ 

6-18: 

A warning dialog box allows the user to cancel the destructive action about which the dialog box is providing a warning.  

The user needs to have a way to cancel an operation that can cause destructive results. 

Required 

_ 

_ 

_ 

en: 

When your application displays a dialog box, it places the input focus at the first text field into which the user is allowed to type an entry, or at the first control within the dialog box with which the user should interact. 

Input focus should always be placed at a predictable and intuitive location. The user should not be forced to set focus at the control most likely to be used when the window is displayed. 

Recommended 

_ 

_ 

_ 

eo: 

As the user presses the Tab key within dialog boxes of your application, the input focus moves to different controls within the window in a left-right, top-down order. 

This assumes that your application is being designed for a left-to-right language environment. Alternative design approaches may be necessary for other locales.

Required 

_ 

_ 

_ 

ep: 

There is always exactly one control within any window of your application that has the input focus if the window in which it resides has the input focus. 

If any window within your application has focus, some control within that window must have focus. The user should not have to explicitly set focus to a control within the window. 

Optional 

_ 

_ 

_ 

eq: 

When a text field within your application does not have the input focus, the text cursor is not displayed within that field. 

Although use of inactive text cursors is allowed within the Motif style, it is better to hide the text cursor on focus out rather than display the inactive text cursor. This makes it easier for the user to quickly scan the screen or a window and determine which text field currently has focus. 

Optional 

_ 

_ 

_ 

er: 

Your application provides keyboard mnemonics for all buttons, menus, and menu items displayed within the application. 

Once the user becomes adept at using your application, keyboard mnemonics provide the user a quick way to access functionality. Mnemonics also facilitate access to functionality from within keyboard-centric applications or windows. The user need not frequently switch between use of the mouse or use of the keyboard. Mnemonics should be provided pervasively throughout the user interface. 

Optional 

_ 

_ 

_ 

es: 

Your application provides keyboard accelerators for those functions that are expected to be used frequently by the user. 

Keyboard accelerators provide the user who has become expert at using your application a quick way to access application functionality without having to go through menus and dialog boxes. 

Required 

_ 

_ 

_ 

et: 

Dialog boxes displayed by your application never block input to other applications within the desktop (that is, they are not system modal) unless it is absolutely essential that the user perform no other action in the desktop until the user responds to the dialog box. 

Applications must allow the user the freedom to access information and tools within the user's desktop environment. Only in the most dire circumstances should an application ever block access to other applications and services within the environment. 

Required 

_ 

_ 

_ 

eu: 

Dialog boxes displayed by your application never block access to other functionality within the application (application modal) unless it is essential that the state of the application remains unchanged until the user responds to the dialog box. 

Required 

_ 

_ 

_ 

ev: 

If your application does not use the values of global environment settings, such as multiclick timeout intervals, drag thresholds, window color settings, mouse left- or right-handedness, and so on, but instead uses its own values for these settings, then your application provides one or more Options dialog boxes that allow the user to change the values for these settings. 

In general, you should not override the value of settings treated as global environment settings. These settings are controlled by the user through the Common Desktop Environment Style Manager. If you choose to ignore these settings and specify your own settings, then your application will behave inconsistently with other applications in the Common Desktop Environment desktop. If you nevertheless choose to provide your own values, then you must provide the user a way to make your settings consistent with the rest of the desktop.