> For the complete documentation index, see [llms.txt](https://specs.govstack.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://specs.govstack.global/service-patterns/3-service-design-good-practice-guidelines/3.2-accessibility-and-inclusion/3.2.2.2-support-multiple-languages.md). # 3.2.2.2 Support multiple languages ### **Identify the languages users speak** Analyse user demographics data to determine the languages spoken by your users. This data can be obtained through user surveys, usage data analysis, or from market research. You may also find legislation for languages the government must support. Read more about [using data to make decisions](/service-patterns/3-service-design-good-practice-guidelines/3.1-user-centred-design/3.1.3.2-monitor-performance.md). ### **Make a plan for multilingual support** Consider the feasibility and utility of providing multilingual support. This includes the translation of key content, interface elements, instructions, and forms into the most commonly spoken languages of your user base. Automated translation services can be a cost-effective starting point, but human review is essential to ensure cultural appropriateness and accuracy. ### **Use simple language** Even in the primary language of the service, avoid using complex jargon and technical terms. Use plain, simple language that can be easily understood by a broad audience. This will also facilitate more accurate translations. ### **Language Detection and Preferences** Implement language detection based on the user's browser or system settings and offer the option for users to manually set their language preferences. Use the `Accept-Language` HTTP header to detect the language preferences set by the user in their browser or device settings. This can give you a default language to serve to the user initially. Store the user's language preference (in cookies or user profiles) so that you can load the website or app in their preferred language in subsequent visits or sessions. ### **Clear Language switching options** Options to switch languages are clearly visible and easily accessible across all pages of the service. Users should not have to search or dig deep into settings to find this option. See the design pattern for [switching languages](/service-patterns/3-service-design-good-practice-guidelines/3.2-accessibility-and-inclusion/3.2.2.2-support-multiple-languages.md). ### **Support for right-to-left (RTL) languages** If you're offering support for languages that are read right-to-left (like Arabic or Hebrew), make sure your user interface can handle that transition seamlessly. This is not just about text direction; UI elements and navigation should also mirror to offer a consistent RTL experience. Read more about [using frontend frameworks](/service-patterns/3-service-design-good-practice-guidelines/3.3-consistency/3.3.2.3-use-a-frontend-framework.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://specs.govstack.global/service-patterns/3-service-design-good-practice-guidelines/3.2-accessibility-and-inclusion/3.2.2.2-support-multiple-languages.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.