View Page - Team Home Page : Character key shortcuts exist and cannot be modified or turned off

Issue Summary

Single character key shortcuts exist and do not have at least one of these required options: the ability to turn off single character key shortcuts, the ability to remap to a non-singular key shortcut, OR are only active when the appropriate user interface component has focus.

Steps to Reproduce

1. Navigate to the desired confluence page.
2. In the header section, navigate to the confluence help link and activate the keyboard shortcut link option.
3. A modal will appear containing the keyboard shortcuts, uncheck the "Enable shortcuts" checkbox in the modal and close the modal.
4. In the main content area of the viewed page, try interacting with the page with single character keyboard shortcuts such as "C", "F", "M", etc.

Actual Results

On the Confluence page, when the user has the settings disabled for keyboard shortcuts and tries to interact with the page, the shortcut actions are still being performed. For eg. when the user activated the "C" key, the create page shortcut functionality is available, or "M" to add a comment to the page, which should not happen since the shortcuts are disabled. This will affect the users with mobility impairment or cognitive disability, as a key could be pressed unwillingly by mistake and unwanted actions could take place.

Expected Results

The single-character keyboard shortcuts should not function when the "Enable shortcut" checkbox in unchecked from the Keyboard shortcuts modal dialog.

The following could be implemented to ensure more accessible keyboard shortcut techniques:

• Turn off: A mechanism is available to turn the shortcut off;
• Remap: A mechanism is available to remap the shortcut to use one or more non-printable keyboard characters (e.g. Ctrl, Alt, etc);
• Active only on focus: The keyboard shortcut for a user interface component is only active when that component has focus.

Screen Recording

Screen Recording 2022-07-08 at 6.55.39 PM.mov

Workaround

Currently, there is no known workaround for this behaviour. A workaround will be added here when available.

Bug Ref: 725273