# Kiosk UI Design: Touch Screens for Public Spaces

> Kiosk interfaces are used standing, in a hurry, by strangers who have never seen them. Design large touch targets, one task per screen, an attract loop that invites people in, a timeout that resets after inactivity, and an accessible path for wheelchair users and people with low vision. Make it work offline and recover gracefully when something fails.

Updated November 2026. Source: https://www.exodeui.com/learn/kiosk-ui-design/

## Key takeaways

- Assume no onboarding and little patience
- Large targets, one action per screen, reachable controls
- Attract loop when idle, timeout and reset after use
- Work offline and recover from hardware failures

## Who uses a kiosk

Kiosk users have no onboarding, no account and often little patience. They may be carrying bags, wearing gloves or reading in a second language. Every screen should make the next step obvious within a couple of seconds.

## Touch and layout

Use targets well above the WCAG minimum of 24 by 24 CSS pixels; on large public screens, much bigger targets with generous spacing reduce mistakes. Keep important controls in the lower and middle parts of the screen, where people of different heights can reach them. In the United States, the Access Board's ICT and accessibility standards cover reach ranges and operable parts for self-service machines.

- One primary action per screen
- Large type and high contrast for viewing at arm's length
- Clear back and start-over buttons on every screen
- No hover, no long-press, no small swipes

## Attract loops and timeouts

An idle kiosk needs an attract loop: a short animation that shows what the kiosk does and invites a touch. Once someone starts, add an inactivity timeout that warns them, then resets to the start so the next person does not see the previous user's data.

## Robustness

Kiosks run for months. Plan for lost connections, a frozen payment terminal and a full receipt printer. Cache content locally, show plain-language error states with a way to restart, and avoid animations that leak memory over long sessions.

## Building this in ExodeUI

In ExodeUI, which we make, an attract loop is simply the idle state of a component, and a touch input moves it into the interactive flow. Your kiosk app resets the input after the timeout. Keep the actual task screens in plain, native UI.

## Frequently asked questions

### How big should kiosk buttons be?

Much larger than desktop or phone buttons, with generous spacing. Test with real users at the actual screen size and mounting height.

### What is an attract loop?

A short animation shown when the kiosk is idle, which explains what it does and invites people to touch.

### How long should a kiosk timeout be?

Long enough to read and decide, usually tens of seconds, with a warning before resetting.

### Are kiosks covered by accessibility law?

Often, depending on the country and sector. In the US, see the Access Board's ICT standards; check local rules.

## Related

- [Accessible focus states](https://www.exodeui.com/learn/accessible-focus-states/)
- [Canvas hit testing](https://www.exodeui.com/learn/canvas-hit-testing/)
- [Error messages UX](https://www.exodeui.com/learn/error-messages-ux/)
- [Best interactive animation tools](https://www.exodeui.com/best-interactive-animation-tools/)
