Language access and resident usability
Plan English, Spanish, Vietnamese and Tagalog content as complete service journeys, with translation review and resident testing.
Newton & Carter. Published November 9, 2026; updated November 9, 2026. Version 1.1.
Maintain one governed content inventory
Record the approved English source, content owner, translated versions, terminology, update triggers and review history. Include attachments, forms, search answers, notices and multimedia.
Make language choice usable
Use native language labels, UTF-8, correct page and passage language, and a persistent way to switch. Browser language can suggest an initial view while the visitor remains in control.
Review meaning and test resident tasks
Qualified language reviewers validate terminology and intent. Recruit residents for representative mobile tasks, provide interpretation and accommodations, and record misunderstood content and completion barriers before acceptance.
Inspect the four-language interface and resident acceptance plan ↗
References for the work
Use these published resources when defining the requirements for your project.
- W3C internationalization quick tips ↗
Language declaration, Unicode, visible language choice and validation guidance.
- Four-language service interface example ↗
Inspect English, Spanish, Vietnamese and Tagalog content and language controls.
Synthetic research sample / Version 1.0
Research and service-design plan
- Question
- Can a first-time resident identify and begin the correct service?
- Scenario
- Fictional service directory
Put the plan to work
Inspect the versioned source and discuss the structure of your engagement.
Inspect the related versioned sample ↗These are planning practices, not a universal scope, legal interpretation or delivery guarantee. Agree the criteria that apply to your project.
Bring your project brief ↗