iPhone keyboard covering the text field you are typing in
The keyboard rising over the exact box you are typing into is almost always the page or app failing to make room for it, not the keyboard doing anything wrong. How to tell the two apart, and what actually helps.
You tap a text box near the bottom of the screen — a comment field, a login box, a chat widget pinned to the bottom of a page — and the keyboard rises up and sits directly on top of it. You can still type, but you cannot see what you are typing, or even see the box at all. It feels like the keyboard is in the wrong place. Almost always, it is the page or app underneath it that has not moved out of the way.
iOS never resizes anything for you
When the keyboard appears, iOS does exactly one thing on its own: it tells the app or webpage how big the keyboard is and where it now sits, through a standard notification every app can listen for. That is the entire contract. iOS does not scroll the page, shrink the content, or push the text field up — it hands over the measurement and leaves the rest to whatever you are typing into. A well-built app or page listens for that notification and adjusts its own layout, sliding the relevant content up so the field you tapped stays visible above the keyboard. One that does not listen, or gets the calculation wrong, leaves the field exactly where it was — which the keyboard then simply covers, because nothing told it to be anywhere else.
Why this shows up on websites far more than in apps
A native app built with Apple’s own tools tends to get this right by default, because the standard building blocks already include keyboard-avoidance behaviour. A webpage loaded inside Safari, or inside the in-app browser many apps use for links, is a different story. Mobile Safari resizes the visible portion of the page when the keyboard appears rather than the page itself, and a page built with an element pinned to the bottom of the screen — a common pattern for chat widgets, comment boxes, and sticky footers — can end up positioned relative to the full page height rather than the shrunken visible area. The keyboard then rises to meet a field that never actually moved, and the result is the field sliding out of view behind it.
Chat widgets and comment boxes are the classic case
This is why the complaint so often centres on exactly those two things. A support chat bubble, a comment box under an article, a message composer inside a web app — all three are commonly built as a small panel fixed to the bottom edge, which is precisely the layout pattern most likely to misjudge where the keyboard actually ends. A plain search bar or a form field higher up the page rarely has the same problem, because there is enough page above it to scroll.
Telling the two apart
- Happens on one specific website or one specific app, fine everywhere else → that page or app is not handling the keyboard correctly. This is by far the most common case.
- Happens in Notes, Messages, and Mail too, on every keyboard you have → worth a closer look at the device itself rather than any one app, though this is uncommon.
- Only happens with a chat widget, comment box, or something pinned near the bottom of a webpage → the classic fixed-position case described above.
- Only happens right after rotating the phone, then clears once you tap out and back into the field → the page recalculated late rather than never; tapping the field again after rotation usually settles it.
What actually helps
- Try scrolling the page or screen by hand once the keyboard is up. Many pages that fail to reposition automatically will still scroll manually, and a small nudge is often enough to bring the field back above the keyboard.
- Tap out of the field and back in. Some pages recalculate their layout only when a field gains focus, so a second tap after the keyboard is already showing can fix what the first tap missed.
- On a website in Safari, try “Request Desktop Website” from the address bar menu. Desktop layouts do not rely on the mobile-specific fixed-position pattern described above nearly as often, so the field sometimes stays put where the mobile version did not.
- If it is a form you can also reach in a different app — a bank’s own app instead of its mobile site, for instance — that native version is more likely to handle the keyboard correctly in the first place.
- There is nothing to fix in Settings. This is not a configuration issue, so there is no toggle in Settings → General → Keyboard that changes it.
Does switching to a different keyboard fix it?
No, and it will not make it worse either. Every keyboard on iOS — Apple’s own or a third-party one — reports its size and position to the app through that same standard notification. The app or page decides what to do with that information, and the keyboard has no way to reach past that boundary and reposition the page itself. Switching keyboards changes what the keyboard looks and sounds like; it does not change whose job it is to make room for it.
Where Kibo fits
Kibo is a system keyboard like any other from iOS’s point of view, so it reports its frame through the same mechanism Apple’s keyboard uses, and an app or page that already handles keyboard avoidance correctly handles Kibo the same way it handles the standard keyboard. A theme, a key sound or a backlight effect does not change that reporting or add any special behaviour on top of it — Kibo cannot fix a page that ignores the keyboard, and using it does not create the problem either. It is free to download and works with Full Access left off.
Frequently asked questions
Why does the keyboard cover the exact box I am typing into?
iOS only tells the app or webpage how big the keyboard is; it is up to that app or page to move its own content out of the way. When it does not — often because of a chat widget or comment box fixed near the bottom of the screen — the keyboard ends up sitting on top of a field that never moved.
Will switching to a different keyboard app fix this?
No. Every keyboard, Apple’s own included, reports its size to the app the same way, and has no ability to move the app’s content itself. The fix, if there is one, lives in the app or webpage, not in which keyboard you have added.
Is there a Settings toggle that stops the keyboard from covering text fields?
No. This is not a configuration option because it is not a keyboard problem — it is a case of a specific app or page not repositioning its own content when the keyboard appears.
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.