• Button Access Keys
• Accelerator Keys

Fusion Standard Button Access Keys

Button mnemonic access keys use the combination of Shift+Alt+<character> in Firefox and Alt+<character> in Internet Explorer. These mnemonic button access keys are added using the textAndAccessKey property for commandButtons and should be used consistently throughout Fusion application buttons. If these Fusion Standard Button actions are used within a commandMenuItem of inline selector buttons, add the access key using the textAndAccessKey property of commandMenuItem.

• Apply – l
  
• Back – B
  
• Cancel – C
  
• Continue – u
  
• Done – o
• Finish – i
  
• Next – x
  
• No – N
  
• OK – K
  
• Save and Close - S
  
• Search – r
  
• Submit – m
  
• Yes – Y

Please see the Keyboard Shortcuts Excel document for a list of keyboard letters already being used as access keys by either Oracle Applications or by the browser in Internet Explorer.

Apps-UX recommends that keyboard shortcuts are not used for Table Action butcons, such as Create, Edit, and Delete. Although these are common butcons, they are not HTML text buttons and would break the consistency of using inline access keys with the textAndAccessKey property.

Custom Access Keys

Apps-UX recommends that product teams should avoid creating custom access keys and only use them sparingly when necessary for needed product functionality. Custom access keys should be created only when absolutely necessary using the number 0-9 with the accessKey property.

The product team is responsible that their access key is used consistently and does not conflict with other access keys in their product. (Using the numbers 0-9 as custom button access keys saves internationalization from having to translate custom development access keys into respective languages.)

Product teams should avoid creating custom access keys. Access keys have the potential to introduce conflicts. Teams creating custom access keys are responsible for managing any conflicts with the browsers, other assistive technology programs that use access keys, and any access key conflicts with different product areas that appear together within the UI Shell.

Internationalization

Apps-UX recommends that each language translates the Fusion Standard Button Access Keys list into inline access keys using the textAndAccessKey property for each language. Translators of the list need to ensure that the translated button access keys do not conflict with browser access keys and assistive technology access keys in that particular language.

Custom development coded access keys do not need to be translated if development has followed the standard of using numeric (0-9) custom button access key combinations only.

Accelerators are keyboard shortcuts that initiate actions immediately when activated.

Accelerators can be added in Fusion Applications to menu items within a menu.

The accelerator attribute for commandMenuItem allows developers to specify a key combination that will activate a menu command. There is no other public method of coding accelerators outside of this attribute.

Default accelerators for RCUX components are described within individual UI specifications. Custom accelerators are only supported in Menus.

Refer to the Keyboard Shortcuts Usage Guideline in the RCUX Guidelines at:
Keyboard Shortcuts Usage Guideline

Flexfield Accelerator

Flexfields in Fusion Applications uses the accelerator Ctrl-Alt-K.

Custom Accelerators

If custom accelerators are needed, Apps-UX recommends that Ctrl-Alt key combinations are used for accelerators whenever possible. Ctrl-Alt accelerators tend to conflict less with accelerators of other applications, such as assistive technology. (Ctrl-Shift may be used infrequently for accelerators that deal with the movement or positioning of items.) Appropriate uses of Ctrl-Alt key combinations include accelerators for menu items.

Product teams need to ensure that Custom Accelerators do not conflict with other accelerators and custom accelerators in their product.

Refer to the worksheet on Ctrl-Alt accelerators in the Keyboard Shortcuts Excel document

Guidelines for Creating Custom Keyboard Shortcuts

Product teams are responsible for creating any custom keyboard shortcuts they deem necessary for their product and ensuring that these custom keyboard shortcuts are used consistently throughout the application.

Below is an outline of a process the product team may want to go through for Custom Keyboard Shortcuts:

1. Determine which functions are most critical for users to have keyboard shortcuts and make a prioritized list.
   • These may include frequently and repetitively used functions in the application.
• As a general rule of thumb, less than 25% of the available functions should have a keyboard shortcut.
• Keyboard shortcuts are not required for accessibility. As long as all parts and functions of the application are keyboard-navigable, the keyboard shortcut provides an additional way to access the area or function quickly.
2. Check RCUX and product-specific documentation to determine what standard keyboard shortcuts already exist.
• Refer to the RCUX Keyboard Shortcuts UI Specification
• See product-specific documentation, such as the Apps-UX Fusion Standard Button Access Keys to see what keyboard shortcuts already exist.
• Refer to any documentation your product team has on custom keyboard shortcuts and standards.
3. Define which custom keyboard shortcuts are needed.
• Use custom keyboard shortcuts sparingly.
• Use the numbers 0-9 for custom button access keys using the accessKey attribute, and use these consistently throughout the product.
• Use Ctrl-Alt key combinations for custom menu accelerators, and use these consistently throughout the product.
• Product team to keep track of used keyboard shortcut combinations.