Write for Accessibility and Translation

Content that works for screen readers and translators is almost always clearer for everyone else, too.

Accessibility

Meaningful link text: "See Export options", never "click here".
Alt text for images that explains their purpose; mark purely decorative images as decorative.
Proper heading levels (H1 → H2 → H3) so assistive technology can navigate.
Don't rely on color alone: "the red button" fails for color-blind readers — name it.
Avoid directional language: "the button on the left" breaks on mobile and in screen readers.
Captions and transcripts for every video and audio clip.

Translation-ready writing

Short, complete sentences with a clear subject and verb.
No idioms or wordplay: "a piece of cake" or "out of the box" may not translate.
Consistent terminology — every synonym multiplies translation work.
No text in images; keep labels in the text so translators can reach them.
Leave room for expansion: German or French text can be around 30% longer than English.

Try it: find the problem

"For more details, click here."

✅ Screen-reader users often navigate by links; "here" says nothing. Write: "For details, see Export options."

"Setting up SSO is a piece of cake — just hit the green button."

✅ An idiom (hard to translate), a vague verb, and color as the only identifier. Write: "To set up SSO, select Enable SSO."

"The fields marked in red are required."

✅ Color alone carries the meaning. Add a text marker: "Required fields are marked with an asterisk (*)."

Quick checklist

Every link describes where it goes. Every image has meaningful alt text. Headings follow a logical order. No idioms, no color-only or position-only instructions.

➡ Next: Review, measure, and maintain