A multilingual service starts before translation

A public service is not multilingual simply because its buttons have been translated. People also need to understand the purpose of a service, the documents it requires, and what will happen after they submit a request. Those questions should shape the original content and workflow.

For English, Dari, and Pashto interfaces, design teams should examine reading direction, script support, terminology, and the space each language needs. Forms deserve particular attention: names, dates, contact details, and error messages must remain understandable when the surrounding interface changes direction.

A practical review follows a complete journey in each language, using ordinary tasks rather than isolated screens. Ask whether a person can find the right service, complete its steps, and understand the response. This sample editorial article proposes a design approach; it reports no commissioned research or measured outcomes.