[GH-ISSUE #317] [BUG] Control + Option (⌃ + ⌥) combined with anything other than Shift and/or Command is not recognized while running macOS VoiceOver #271

New issue

Closed

opened 2026-05-05 05:11:01 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 05:11:01 -06:00

Owner

Originally created by @wohfab on GitHub (Jan 3, 2025).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/317

Control + Option (⌃ + ⌥) combined with anything other than Shift and/or Command is not recognized while running macOS VoiceOver screenreader (VO), thus not shown by keycastr.

VO uses ⌃ + ⌥ as the modifier-key for all its commands, so many commands are not shown.

With VO turned off, the keys are displayed correctly.

Steps to reproduce

While using keycastr:

Start macOS VoiceOver (VO) via ⌘ + F5
Test out commands, e.g. ⌃ + ⌥ + → (used by VO to move to the next item, e.g. on a website)

System info

macOS Sequoia 15.1 (24B2083)
keycastr 0.10.2

Originally created by @wohfab on GitHub (Jan 3, 2025). Original GitHub issue: https://github.com/keycastr/keycastr/issues/317 Control + Option (`⌃ + ⌥`) combined with anything other than Shift and/or Command is not recognized _while running macOS VoiceOver screenreader (VO),_ thus not shown by keycastr. VO uses `⌃ + ⌥` as the modifier-key for all its commands, so many commands are not shown. With VO turned off, the keys are displayed correctly. ## Steps to reproduce While using keycastr: 1. Start macOS VoiceOver (VO) via `⌘ + F5` 2. Test out commands, e.g. `⌃ + ⌥ + →` (used by VO to move to the next item, e.g. on a website) ## System info - macOS Sequoia 15.1 (24B2083) - keycastr 0.10.2

gitea-mirror closed this issue

2026-05-05 05:11:03 -06:00

gitea-mirror commented

2026-05-05 05:11:07 -06:00

Author

Owner

@akitchen commented on GitHub (Jan 23, 2025):

Although it's frustrating, this is not a bug in KeyCastr itself. My best guess is that it's not receiving those events when Voiceover is enabled.

This is tracked in #100

@akitchen commented on GitHub (Jan 23, 2025): Although it's frustrating, this is not a bug in KeyCastr itself. My best guess is that it's not receiving those events when Voiceover is enabled. This is tracked in #100