The problem to solve
If a visitor cannot read the language an exhibit is in, the most important control on the screen is the one that changes it. If they cannot find it, the exhibit effectively does not exist for them. Language switching is a small interface element with a large effect, and it is easy to get wrong because the people designing it can read the default language and so rarely feel the problem.
The aim is simple: a visitor who needs a different language should find the option within a moment, without reading anything in the language they cannot read.
Offer the choice early and keep it visible
Two broad approaches work, and many exhibits use both.
Choose at the start. An opening screen lists the available languages. This is clear, because the choice comes before the content. It works well on attract screens and kiosks where each visitor begins fresh. The risk is that visitors who skip or tap past it find themselves in the wrong language with no obvious way back.
Persistent control. A language control stays in a consistent place on every screen, so a visitor can switch at any time. This helps when someone changes their mind, when a companion takes over, or when a visitor starts in the default language and finds it too difficult.
A sensible pattern is to ask at the start and keep a persistent control available, in the same position on every screen. Consistency matters: if the control moves, people will not find it.
Where to put it
- Choose a conventional, predictable place. A corner of the screen, often the top, is common, but the key is to be consistent across all exhibits in the venue, so visitors learn once.
- Keep it within reach. On large or tall screens, a control at the top corner can be out of reach for children and wheelchair users. Consider placing it at a comfortable height or repeating it near the bottom. See reach ranges.
- Do not hide it. Avoid burying it in a settings menu, behind an icon with no label, or at the end of a scrolling page.
- Do not let it compete. It should be easy to spot without dominating the screen.
- Mind the physical setting. If the screen is partly blocked by a hood, frame or another visitor, check that the control is not in the shadowed area. Screen enclosures sometimes hide corners.
How to label it
Labels are where many interfaces fail.
Write each language in its own language. A list reading “Español, Français, Deutsch, 中文” can be read by people who use those languages, even if the rest of the screen is incomprehensible to them. A list reading “Spanish, French, German, Chinese” in the default language helps only people who can already read it.
Use words, not flags. Flags represent countries, not languages. Many languages are spoken in several countries, and many countries have several languages. A flag can also feel exclusionary or political. Written names are clearer and more respectful.
Add a universal cue. A globe icon or a letter-based symbol can help people identify the control, but pair it with text. Icons alone are not universally understood, and an icon with no text is invisible to screen readers unless labeled correctly.
Choose which languages to list with care. Cover the languages your visitors actually use, based on visitor data and local communities, not assumptions. See multilingual visitors for broader audience thinking.
Distinguish variants where it matters. Some languages differ in written form, such as scripts or regional spellings, and visitors may care. Use the form your audience expects, and do not merge them casually.
Order the list sensibly. Alphabetical order by the language’s own name is neutral. Putting the most common languages first is also reasonable, as long as the logic is consistent.
What happens after the switch
Switching is not just changing the labels. Check each of these.
- Everything changes. Navigation, buttons, instructions, error messages, captions, audio and any pop-ups should all switch. A screen that switches half its text feels broken.
- Same position, same place. After the switch, the visitor should stay on the same screen rather than being returned to the start.
- Layout holds. Text in different languages can be much longer or shorter, and some run right-to-left or need other scripts. Design layouts and buttons with room to expand, and test with real text, not placeholders.
- Fonts support the script. Make sure the typeface includes the characters and that line spacing suits them.
- Audio and video match. Provide dubbed audio or subtitles in the chosen language, and make sure captions appear in that language. Check how exhibit translation was done and whether the quality is consistent across languages.
- Gaps are honest. If some content is not available in the chosen language, say so clearly and show what is available, rather than silently mixing languages.
- Accessibility features follow. Screen readers need the correct language tagged for the text, so they pronounce it properly.
Resets and shared screens
On a shared kiosk, many different people use the same screen in one day. Decide what happens when a visitor walks away.
- After a period of inactivity, return to the default language and the opening screen, so the next person is not confused. Use a reasonable timeout and warn before resetting if a visitor is still reading.
- Do not reset in the middle of someone’s use. Reset on a meaningful pause, not on a short one.
- Consider letting the attract mode cycle through languages, to signal that choices exist.
Resetting to the default can be a poor fit if the default is itself a barrier. Some venues use an attract screen that shows a greeting in several languages and prompts a choice before anything else.
Beyond the screen
Language access is more than a menu. Printed labels, signs, audio guides and staff all form part of the experience. A well-placed switch on a screen helps little if the room’s signs are only in one language. Where you cannot translate everything, prioritize wayfinding, safety and the main introduction.
Testing it
Language switching should be tested with people who need it. Ask speakers of the languages offered to find the control and use it, without help. Prototype testing often reveals problems quickly, such as a control that blends into the background or a label that is not recognized. Check also with users of other assistive technologies, as well as keyboard and screen reader users on web-based exhibits. Revisit the choice of languages over time as visitors change.