Key chords is the bane of keyboarding.
There are 3 types of key shortcuts to invoke commands in software:
of these, in terms of efficiency and hand health (Repetitive Strain Injury), the single key is the best. Key sequence of single keys is second best. Key chord is the worst.
Key chord is the most hard on hand health, but is also conceptually the most convoluted.
i remember in around 1991, when i first learned about key chord on the Macintosh Classic. I thought, it's strange. You have to hold ⌘ Cmd first, then press the key c, then, release c, then, release ⌘ Cmd. It must be in that specific order.
A more natural way is either key sequence, or real chords. That is, pressing several keys together but you don't have to worry about which to hold or release first. Stenograph machines are like that.
Key chord probably started life on the mechanical typewriter, the ⇧ Shift key. The key pushes levels and shift gears, so it must be held down first, then you type other keys.
i suppose, when computer keyboard came, sans levels and gears, but habit stuck, and engineers invented the “modifier” keys, with Bucky bits, to emulate the typewriter behavior.
Now, thinking about this, i think Microsoft must be a genius, when they invented the key system on Windows, where Alt is used to invoke menu, and all command can be called by a sequence of key strokes. For example, pressing 【Alt e c】 does copy. If you press the sequence fast, menu won't show. If you press it slowly, menu shows. This is probably the best system given the PC keyboard. This system, lets you invoke any command, yet has menu counter-part, so it's easy to see a list of them and also grouped by category. (emacs supports this mechanism, and its key system is much more extensive than that.)
BAN the f�ck out of the universe.
But, there isn't enough keys on keyboard. You only have 12 function keys, plus some others such as ↖ Home, ↓. But there are 10 times more commands in software. 〔☛ Emacs Keybinding Efficiency: Page Up/Down and Pigeon Hole Principle〕 What to do?
For majority of commands, you should use a key sequence of single keys, instead. For example, 【F10 e c】. But Function keys are harder to reach. So, you could start with a easy key such as 【▤ Menu e c】. (you can make Caps Lock or ❖ Win key as your start key, whichever key on YOUR keyboard is easy to press.)
There are 26 letters in alphabet, plus 10 digits, so you have 36 key choices for the key. If each of your command has 2 keys in a key sequence (not counting the starting key), then you have 36 × 36 = 1296 possible keys for commands. Quite enough!
Still, some commands are not suitable for key sequence. For example, moving cursor by word. You want to be able to hold down a key and have the cursor keep moving. You can't do that with key sequences, because you need to release the key and press again to invoke the command again. Answer: use single-press key. Retort: But F keys are far away and all other single-press key such as {↖ Home, ↘ End, arrow} keys are already used. Answer: key chord then.
more detail at Keyboard Shortcut Design: Repeatable vs Non-Repeatable Commands and Keys
If you survey commands in a app, for example:
vast majority of commands are the non-repeating type. The repeating type are probably less than 5% of commands. Using 【Ctrl+‹letter/digit›】 key give you about 36 spots. Adding 【Alt+‹letter/digit›】, you have 72 spots. And that's more than enough for repeating commands. In practice, i estimate a programer uses less than 30 repeating commands.
Not many apps supports defining key sequences. Emacs does. For how, see: Emacs Keybinding Syntax Examples.
In {Microsoft Windows, Mac, Linux}, there's a sticky key feature. When you need to press a key chord, such as 【Ctrl+x】, you can just type them separately 【Ctrl x】. That's what the sticky key feature does.
I do not advocate the Sticky Keys feature for the handicapped. It's not the same. Sticky Keys actually make things a worse, because it's a hack over key chords. When you press a sequence of keys, it has to guess whether you mean a sequence or chord (since {Microsoft Windows, Linux, emacs} all support both). The end result is that it's confusing to use, imprecise, and slows you down.