Helping residents find municipal website information in their preferred language

Municipal website language options should be visible in a consistent place and named in ways residents can recognize. Test the whole service path after changing languages, including forms and linked documents. A translated menu is only useful if residents can understand the information and next steps behind it.

Choose languages based on the community's documented needs. Keep a route to language assistance available when automated translation cannot reliably communicate an important detail.

Where should the language choice appear?

Place it consistently across pages, including pages reached directly from search. Label languages by their own names where appropriate so residents do not need to understand an English menu first.

Tualatin's resident feedback (opens in a new tab) requested a more prominent language option. Visibility matters because a feature people cannot find provides little practical assistance.

Check the selector on a phone and with keyboard navigation. Make sure residents can return to the original language and understand which language is currently selected.

What are the limits of automated translation?

Automated translation can change meaning or leave some content untranslated. Boston's translation disclaimer (opens in a new tab) describes accuracy differences and limitations involving files, images and other media.

Review important service instructions with qualified language support when accuracy matters. A disclaimer does not make an incorrect deadline or confusing application requirement useful to a resident.

Keep source text clear and avoid unexplained abbreviations. Short, specific instructions are easier to review in any language than dense administrative phrasing. Confirm the translated result rather than assuming clear source text guarantees accuracy.

Does the language choice carry through the service?

Follow a common task after switching languages. Open the service page, read the requirements and continue into the form or payment system. Check what happens when that next step is hosted by a different provider.

List any gaps. A translated page can lead to an English-only PDF or an external screen with a separate language setting. Explain available assistance at the point where a resident may need it.

Muniway's Translation tool provides a consistent language switcher and lets staff choose the languages offered. Review the actual content and connected tools as part of the setup; the switcher itself cannot establish the accuracy of every translated item.

How should the office maintain language access?

Assign responsibility for updating reviewed translations when the source information changes. Keep related versions connected so an updated service requirement does not appear in one language while another retains the old instruction.

Use feedback from residents and language-assistance staff to identify confusing pages. Prioritize frequently used services and information where a misunderstanding could prevent someone from completing a task.

The service-page guide explains how to make the underlying instructions more complete. Pair that work with language review and accessible design. The goal is a resident who understands the service and can take the next step, with help available when translation alone is insufficient.