Why a Morse keyer app asks for Accessibility on a Mac

27 October 2026 · 6 min read

A Morse keyer app asks for Accessibility because macOS lets no app type into another app until you say so, and Accessibility permission is how you say so. In System Settings, Privacy & Security, Accessibility, macOS sums up the list as “Allow the applications below to control your computer.” A keyer that types what you key into your email or your notes needs exactly that; anything it does inside its own window needs no permission at all.

That is a broad permission, so it is fair to ask what it covers, why a Morse program needs it, and how to take it back.

What Accessibility permission allows

Accessibility was built for assistive technology: software that reads the screen aloud, or lets someone work a Mac with a switch or by voice. To do that, such software has to reach into other apps. With Accessibility permission, an app can:

send keystrokes and clicks to whatever app is in front, as if they came from your keyboard and mouse;
read what is on screen in other apps, such as which button is under the pointer or which text field has the cursor;
watch keyboard input while you work in other apps.

Many ordinary utilities ask for it for the same reasons: window managers, text expanders, automation tools and clipboard tools among them. macOS will not let an app grant itself this. An app can only ask, and you decide in System Settings.

Why a Morse keyer needs it

Inside its own window, any app gets the keys you press, whether they come from the keyboard or from a USB Morse key that acts as a keyboard. That is how a Morse program can teach you, run drills and let you key messages without asking for anything. The trouble starts when you want to key into another app. Then the keyer has three jobs, and macOS guards all of them:

Hear your Morse key while another app is in front. Normally your key presses go only to the front app, so the keyer would never see them.
Type the characters you key into that app, as if you had typed them on the keyboard.
Notice when you type or click yourself, so that any correction it makes touches only the text it typed, never yours.

All three are things Accessibility permission allows. Without it, the keyer can still do everything in its own window, but it cannot type a single letter into another app. For how keying into other apps works in practice, see how to type Morse code into any app on a Mac.

Accessibility and Input Monitoring

There is a second, narrower permission in the same part of System Settings: Input Monitoring. macOS describes it as “Allow the applications below to monitor input from your keyboard even while using other applications.” It lets an app listen to the keyboard, but not type into other apps or read what is on screen.

Some apps that only listen ask for Input Monitoring alone. A keyer that types needs Accessibility. If it also needs Input Monitoring, a well-made one tells you so when it does, rather than asking for everything up front.

One difference worth knowing: when you switch an app’s Input Monitoring on or off, macOS warns that the change applies only once that app is quit. If a permission change seems to do nothing, quit the app and open it again.

How to give it, step by step

Let the app ask. When it needs the permission, macOS shows its own notice saying the app “would like to control this computer using accessibility features,” and points you to Privacy & Security in System Settings.
Or go there yourself. Open the Apple menu, then System Settings, Privacy & Security, Accessibility.
Switch the app on. Find it in the list and turn its switch on. macOS may ask for your password or Touch ID to confirm.
If the app is not listed, use the add button under the list and choose it from your Applications folder.

Make sure you are allowing the copy of the app you actually use. If you have moved or reinstalled it and its switch is on but nothing works, remove its entry and add the app again.

What a careful keyer does with it

A keyer has a broad permission and a narrow job. Before you allow one, it is reasonable to expect it to:

ask only when you switch on the feature that needs it, and explain why;
stop while a password field is active (macOS already shields password fields from other apps, and a careful keyer stays out of them too);
keep nothing you type, and send nothing anywhere;
be signed by a known developer and notarized by Apple, so macOS can check it before it runs.

Here is how Dot & Dash handles it. Only its Type Anywhere feature, which keys Morse into any app, needs Accessibility, and it asks the first time you switch that on, never before. It listens for your Morse key and for your own typing and clicks, so its error signal never deletes your words; it pauses while a password field is active; and it never records, keeps or sends what you type. You can switch Type Anywhere off from its menu bar item, and if keying types nothing, check Accessibility, and Input Monitoring only if Dot & Dash says so.

Taking it back

You can withdraw the permission at any time, from the same place:

Open System Settings, Privacy & Security, Accessibility.
Switch the app off, or select it and use the remove button under the list.

The feature that needed the permission stops; the rest of the app carries on. For a Morse keyer, that means the lessons, drills and everything in its own window still work, but nothing is typed into other apps.

A sensible habit for any Mac: look through the Accessibility list now and then, and switch off anything you no longer use. It is one of the most powerful lists in Privacy & Security, and it is easy to forget what is on it.

Questions

Is it safe to give an app Accessibility permission?

It is safe when you trust the app, because the permission is broad. Give it to apps from a developer you know, signed and notarized, that explain why they need it, and take it back from anything you stop using.

Why does my Morse app work in its own window but not in other apps?

An app always receives the keys pressed in its own window. Keying into other apps needs Accessibility permission, so check that the app is switched on in System Settings, Privacy & Security, Accessibility.

Do I need Accessibility permission just to learn Morse on a Mac?

No. Lessons and drills happen in the app’s own window, where it gets your key presses without any permission. Only keying into other apps needs it.

What is the difference between Accessibility and Input Monitoring?

Input Monitoring lets an app listen to the keyboard while you use other apps. Accessibility goes further: it lets an app type and click in other apps and read what is on screen, which is what typing Morse into another app requires.