Does AssistiveTouch work with a third-party keyboard on iPhone?
AssistiveTouch is a floating button that sits above whatever is on screen, keyboard included, and it never looks inside the keyboard the way VoiceOver or Switch Control do. Here is why that makes it work the same with any keyboard, the one way it can visually get in the way, and where it hands off to Apple’s keyboard regardless.
AssistiveTouch turns a chunk of the phone into a single on-screen button, which raises an obvious question the moment you have also added a keyboard that is not Apple’s: does the button that stands in for Home, for a pinch, for a shake, know what to do around a keyboard it did not draw? The short answer is that it does not need to. AssistiveTouch was built to sit above every app on the phone, not inside any particular one, and a keyboard extension is just one more thing on screen underneath it.
What AssistiveTouch actually replaces
Turn it on in Settings → Accessibility → Touch → AssistiveTouch and a small circle appears, floating on top of everything else, that opens a menu standing in for the gestures and hardware controls a finger or a button would otherwise handle: Home, Notification Center, Control Center, a pinch, a multi-finger swipe, a shake, the volume rocker, Siri. It exists for anyone who finds a physical button hard to press reliably, or a multi-finger gesture hard to perform, and it works by replacing those actions with taps on one button instead.
It floats above the keyboard, not inside it
The distinction that matters here is where AssistiveTouch actually operates. It is a system-level overlay, drawn by iOS on top of whatever app and whatever keyboard happen to be on screen at the time, the same layer a screenshot or a Control Center swipe comes from. It has no idea which keyboard is active and no reason to need one — the menu it opens does not contain keyboard-specific actions, and dismissing it hands control straight back to whatever was underneath, keyboard included. Apple’s keyboard and a third-party one look identical to it, because neither is the thing it is built to interact with.
Why this is a different case from VoiceOver or Switch Control
It is worth contrasting this with the other iOS accessibility features that do reach into a keyboard. VoiceOver reads out each key by pulling its label from the accessibility tree the keyboard drew, and Switch Control scans through the same labelled elements one at a time. Both of those depend on the keyboard exposing its keys correctly, which is why a badly built custom keyboard can, in principle, cause them trouble. AssistiveTouch does none of that. Its button is a fixed target you tap directly, wherever it happens to be sitting, and it never reads or scans anything the keyboard drew. There is nothing for a keyboard to expose correctly or badly, so there is also nothing that could make one keyboard work better with it than another.
The one place it can visually get in the way
Because the button floats above everything, it can end up sitting over the top row of a keyboard if you have dragged it down toward the bottom edge of the screen, which is a real annoyance but not a functional one: tapping a key underneath it still reaches that key, and only a tap landing exactly on the button itself opens the AssistiveTouch menu instead. Dragging the button up out of the keyboard’s way, or turning on “Idle Opacity” in its settings so it fades to translucent when you are not actively using it, both deal with the overlap without touching anything the keyboard itself controls.
Full Access has nothing to do with it
AssistiveTouch lives in Settings → Accessibility; Full Access lives in Settings → General → Keyboard → Keyboards, next to a specific keyboard’s name. They are unrelated switches governing unrelated things, and turning one on changes nothing about the other. A keyboard that works fully with Full Access off keeps working exactly the same way with AssistiveTouch on, because AssistiveTouch was never a permission the keyboard needed to be granted — it operates entirely outside the keyboard extension’s own sandbox.
What still forces Apple’s keyboard, AssistiveTouch or not
A secure text field — a password box, a card number entry — switches to iOS’s own keyboard the moment it gets focus, and that happens at the same system level regardless of whether AssistiveTouch is running. Its menu can trigger Siri or open Control Center, but nothing in it is capable of overriding that swap, and no keyboard, Apple’s or otherwise, has a way to opt out of it either.
Where Kibo fits
Kibo draws its keys the ordinary way and has no setting for AssistiveTouch because none is needed — the floating button sits above Kibo exactly the way it sits above any other keyboard, unaffected by which theme, sound or lighting effect happens to be active underneath it. Full Access stays a separate matter entirely: Kibo reads it only for the Copy word, Copy line and Paste buttons on its own toolbar, and everything else, AssistiveTouch included, works the same with that switch left off. Kibo is free to download.
Frequently asked questions
Does AssistiveTouch work with a third-party keyboard on iPhone?
Yes. AssistiveTouch is a system-level overlay that floats above every app and keyboard on the phone. It does not read or interact with a keyboard’s keys the way VoiceOver or Switch Control do, so it behaves identically whether Apple’s keyboard or a third-party one is active.
Can the AssistiveTouch button block a keyboard key?
It can sit visually on top of one if you have dragged it down near the keyboard, but a tap on the key underneath still reaches that key. Only a tap landing exactly on the button itself opens the AssistiveTouch menu. Dragging the button elsewhere, or turning on Idle Opacity, clears it out of the way.
Does turning on AssistiveTouch require Full Access for a keyboard?
No. AssistiveTouch is an Accessibility setting and Full Access is a per-keyboard permission in a completely different Settings menu. Neither one affects the other.
Try it on your own keyboard
Kibo is a free custom keyboard for iPhone with real mechanical key sounds, a wardrobe of themes and RGB backlight effects. No account, no ads, and it works with Full Access left off.