A discoverable way to dismiss the keyboard

What it is

A soft keyboard has no laptop lid to close. It keeps occupying the screen until focus leaves, the system receives an explicit dismiss, or the user hits a control designated as dismiss. That exit must be discoverable: when someone needs to read covered content, tap a header button, or yield the screen to a full-screen video, they have to know how to take the keyboard down, not stumble onto empty space.

Why it happens

While focus sits in a field, the system assumes typing continues and will not dismiss itself. Typical exits are a dedicated dismiss key or chevron on the keyboard, a tap outside fields, a list scroll, a navigation away, and an application hide call. They are not equally visible. The dismiss key is missing on some platforms and some keyboard types; tapping empty space fails on a form that is almost all fields; scroll-to-dismiss fights the gesture “I want to read the hint under this field.” When the exit is undiscoverable, people misfire a system back gesture or tap Submit repeatedly—and if Submit is still covered, they type the whole thing again. Dismissal is also bound to unsaved drafts: whether blur should save decides whether “tap outside” can even be an exit.

Studying it

Give people unfamiliar with the platform the task “after typing, tap Done in the header.” Record which exit they used, attempt count, and accidental backs. Independent variables include presence of a dismiss key, amount of empty space, whether scrolling dismisses, and an explicit Done control; dependent measures include time to successful dismiss, mis-navigation, and abandonment. Internal employees treat platform habit as already-visible exits.

Where it stops holding

A single search field that submits and dismisses on Enter needs a weaker extra exit. With a hardware keyboard attached the soft keyboard may never appear. Games or immersive full screen that block system gestures must provide their own obvious close. When an IME candidate bar expands, the dismiss key moves and memory of “chevron, lower right” fails.

Applying it

• Put a persistently visible Done / Dismiss on a keyboard accessory or in the navigation bar; do not rely on tapping empty space alone.
• Decouple scrolling from dismiss so people can scroll covered content without being forced to blur; dismiss through an explicit control or the keyboard’s own key.
• Have people who do not live on that OS complete “finish typing, then tap the header.” If they first trigger Back or re-enter the field, the exit is still undiscoverable.

Related

• Same group: C6.06.1 The keyboard occludes the input area and the submit control · C6.06.2 Compressed viewports after the keyboard appears need relayout, not a simple push
• Adjacent: C6.07 Keyboard types and task fit · C6.05 Focus order
• Search: dismiss keyboard · resign first responder · keyboard accessory