Design so it arrives

A well-structured document is one that can be taken apart and used in ways you did not plan. A screen reader can jump heading to heading. A person with low vision can enlarge it without the layout collapsing. A translator can work section by section without guessing what belongs together. A colleague can skim it in ninety seconds and find the part they need. None of that depends on how it looks; it depends on whether the structure is real.

Real means using the tools rather than imitating them. A heading made by making text big and bold is not a heading; it looks like one and behaves like nothing. A list made by typing dashes is not a list. A table used to line up a page layout tells a screen reader there is data where there is none. The fix takes seconds in the software you already use, and it is the single highest-value habit in this module.

Link text works the same way. Many people navigate by pulling up a list of the links in a page, which arrives stripped of the sentences around it. A page of links all reading “click here” or “more information” is a page of doors with no signs. Write the destination into the link: “read the service authorization summary” rather than “click here to read more.”

Translation is often treated as a final step: finish the document, hand it over, wait. That sequence produces late, expensive and often inaccurate translated versions, because the source text was never written to be translated. Idioms, long stacked clauses, undefined program terms and unexplained acronyms all break in translation, and a translator with no context will produce something fluent and wrong.

Writing translation-ready English costs nothing and improves the English version too. Keep sentences short and one idea to a sentence. Define a program term at first use. Avoid idioms and sports metaphors. Avoid acronyms, or spell them out and keep a list. Leave room in the layout, because many languages run longer than English. Then plan the calendar: vital documents need time for translation and for review by people who speak the language and know the program, and that review is expert work that should be paid.

Interpreters need the same foresight. Send the agenda, slides, names and terms in advance; tell them the format and who is speaking; and build in pauses. A staff member who speaks quickly through a dense slide has not been interpreted so much as summarized.

There is a habit worth naming here. Treating everyone identically — one version, one format, one channel, because that feels fair — is the most common way a well-meaning unit excludes people. It is what minimization looks like in daily practice: the differences are real, but the design does not see them. Adapting the form of a message while keeping its substance intact is what moves the work toward acceptance and adaptation.