Avoid using accesskey for shortcuts

• An accesskey value can conflict with a system or browser keyboard shortcut, or assistive technology functionality. What may work for one combination of operating system, assistive technology, and browser may not work with other combinations.
• Certain accesskey values may not be present on certain keyboards, especially when internationalization is a concern. So adapting to specific languages could cause further problems.
• accesskey values that rely on numbers may be confusing to individuals experiencing cognitive concerns, where the number doesn't have a logical association with the functionality it triggers.
• Informing the user that accesskeys are present, so that they are aware of the functionality. If the system lacks a method of notifying the user about this feature, the user might accidentally activate accesskeys.

Success Criterion 2.1.4 Character Key Shortcuts

Other Related Success Criterion:

• Remove the use of the accesskey attribute.
• Use scripting instead of accesskey attribute to define shortcuts. The scripting must meet the WCAG 2.1.4 requirements for shortcuts.

• W3C Understanding Character Key Shortcuts
• MDN: accesskey
• WebAIM: Accesskey