Why Mac window managers need the Accessibility permission

Updated · by , maker of Ribbon

macOS only lets an app move or resize another app's windows through the Accessibility interface, so every window manager, snapping tool and window switcher asks for it. It's a powerful permission: beyond moving windows, it lets an app read and operate other apps' interfaces. Grant it only to apps you trust, from developers you can identify, and know how to take it back.

What the permission is for

Accessibility exists so assistive software, like screen readers and switch control, can see and operate everything on screen. Window managers use the same interface because it's the only public way to:

There's no narrower "manage windows only" permission on macOS. That's why a simple snapping tool asks for the same permission as a screen reader.

What it could do

The interface that moves windows can also read the text of buttons, menus and many text fields in other apps, and press buttons or choose menu items. A window manager has no reason to do that, but the permission doesn't stop it. So:

How to grant it

  1. Open System Settings → Privacy & Security → Accessibility.
  2. Turn on the switch next to the app. If it isn't listed, click + and choose it from Applications.
  3. You may need to quit and reopen the app.

Most apps open this pane for you on first launch.

How to revoke it

Turn off the app's switch in the same list, or select it and click − to remove it entirely. The app loses access immediately.

Why it stops working

Other permissions you may be asked for

PermissionWho asks and why
Screen RecordingWindow switchers that show thumbnails, such as AltTab
Input MonitoringTools that watch keys or gestures system-wide, such as keyboard remappers
AutomationApps that control other apps with AppleScript

A window manager that only moves windows needs Accessibility and nothing else.

Accessibility vs turning off SIP

System Integrity Protection (SIP) protects macOS system files and processes. A few power tools ask you to partly disable it, from Recovery mode, so they can inject code into the Dock to do things the Accessibility interface can't, such as creating Spaces or moving windows between them instantly. yabai is the best-known example; its basic tiling works with SIP on. See yabai without SIP.

Turning off SIP is a much bigger decision than granting Accessibility: it lowers protection for the whole system. Most window managers don't need it.

What Ribbon asks for

Ribbon needs the Accessibility permission only. No SIP changes, no kernel extensions, no account and no telemetry; the app contacts the network only to validate its licence and check for updates. The details are in the privacy policy and the setup guide. You can see what the app does before installing anything in the live demo, and pricing is $9.99 once.

FAQ

Is it safe to give a window manager Accessibility access?

It's safe with an app you trust. The permission is broad, so choose apps from identifiable developers, and remove access from apps you stop using.

Why does my window manager say it has no permission when the switch is on?

Usually the app was moved or updated. Remove it from the Accessibility list with the minus button, add it again, and reopen the app.

Do Mac window managers need SIP disabled?

Almost none do. Some advanced yabai features need SIP partly disabled; its basic tiling, and most other window managers, work with SIP on.

Keep reading