A shared device can have separate interface, spoken-menu, audio-track and caption-language preferences. Configure them intentionally for the people using it rather than assuming one language switch controls every layer. Check available source tracks and document any profile-specific choices. Write down the preferred language for each layer and verify them independently in the intended profile. A shared interface language can coexist with another programme-audio or caption choice, while spoken-menu support depends on the screen reader's available voices and the app's labels.
Separate the four layers
Menus, screen-reader voice, programme audio and captions have different inputs. Check interface text, screen-reader speech, programme audio and captions separately rather than changing one global language repeatedly. The first concerns translated menus, the second how accessible labels are spoken, and the latter two depend on supplied media tracks. A menu translated into a language does not imply a corresponding dub or caption track exists. Confirm each available control in the actual app and device so the household can tell a missing media option from a wrongly selected preference.
Use profiles where supported
Do not assume every player synchronizes preferences. Where profiles are supported, assign preferences to the intended viewer and check whether the device or app stores them locally or synchronizes them. Some settings may remain system-wide even when track choices are profile-specific. Test switching profiles and restarting a title before relying on automatic behavior. Keep a short note of any shared setting that one viewer must change, so another person's screen-reader voice or caption choice is not accidentally overwritten during ordinary household use.
Review actual availability
A preferred language cannot add an absent track. Open a known title containing the desired audio and caption languages to test selection fairly, then inspect the exact edition when a different title behaves differently. A preference cannot create a missing translation, and a previously selected per-title track can override a broader rule in some apps. Record the available labels and active profile when reporting a mismatch. Avoid promising that every catalogue entry will use the same languages simply because the shared device's menus do.
A practical sequence
0 of 4 steps completed on this page.
An example to work through
Menus areEnglish, the screen-reader voice uses another supported language, and captions follow the current viewer preference. One viewer keeps the interface in a familiar shared language while selecting another supplied audio language and hearing-access captions. A second profile has different track preferences, but the device's spoken-menu setting remains shared, so the household documents that one system-level choice instead of assuming complete profile isolation.
Questions about this topic
Does every app support profiles?
No. Check the actual app and distinguish profile preferences from device-wide accessibility settings.
Will a language preference translate the catalogue?
Only supported interface translations apply. Interface translation does not create programme audio, subtitles or other media tracks in that language.
