Find Help for Every Part of SimplifyAccess

Changing Language and Accessing Translated Content

Distinguish the widget interface language from prepared website translations and understand why coverage can differ.

Search titles, topics, and tags. Articles matching more keywords appear first.

Step-by-step instructions Platform and visitor tools Practical accessibility workflows
Published
Author
SimplifyAccess Team
Updated

The language used by widget buttons and the language of the website content are separate matters. Changing one does not guarantee that every part of the other will change.

SimplifyAccess provides interface-language selection and a separate capability for applying available prepared translations to page content.

Change the widget interface language

  1. Open the widget.
  2. Select the language button in the header, shown as a language symbol or flag.
  3. Choose an offered language.
  4. Read the widget's translated labels and messages.

The selection is stored in the current browser. Another browser or device may use a different selection.

If the language button is absent, the website owner may not have enabled Language Selection.

Understand page translations

When the translation capability is enabled, the widget can request a prepared page translation for a supported target language. It can use a stored language preference or a compatible browser preference.

The available translation must belong to the current page. Only matching supported text is replaced, so some parts of a page can remain in the original language.

Selecting a menu language does not instantly create translations for all website content, and the range of interface languages is broader than the translation capability's current target-language handling.

Example

A visitor selects French and sees French widget controls. If a prepared French translation is available and the translation capability is enabled, matching page passages can also appear in French.

If the original page stays unchanged, the interface-language selection may still have worked correctly. The page may not have a usable translation for that language.

Other language-dependent tools

Read Aloud voices, dictionary definitions, speech commands, and prepared simplified text each have their own language requirements. An interface translation does not prove that all of these tools support the same language or have corresponding content.

For example, a dictionary's configured language can differ from the selected widget language.

If the result is incomplete

Allow the page to finish loading. Check whether the unchanged text is ordinary page text, an image, or content inside an embedded service. Website changes can also prevent prepared text from matching its original passage.

For an explicit original-language version, use the website's own language navigation where available. The current widget's language control should not be treated as a universal restore-original-translation button.

For website owners

Test interface language and content translation separately. Confirm that prepared translations exist and remain aligned with the current source text.

See Looking Up Words with the Dictionary and Why a Widget Feature Is Missing or Has No Content for related availability questions.

Continue in SimplifyAccess

Ready to Put This Guide Into Practice?

Create a SimplifyAccess account to manage connected websites, review accessibility findings, work with accessible-content workflows, configure visitor tools, and create reports from one platform.

Already have an account? Log in to continue with the website, setting, audit, content workflow, or report covered in this guide.

Available features, processing options, and editing capabilities depend on the connected website and selected plan.