Published on 31 March 2022 by Andrew Owen (3 minutes)
At the end of last week, I attended a conference in Budapest. I had the opportunity to give a short talk on API First, and I’ll expand on that in a future article. But one of the biggest takeaways for me was that, as an industry, we still have a long way to go in making documentation globally accessible.
If at any point this article starts to sound like an advert for the Microsoft Writing Style Guide, it’s with good reason. For most of my nearly 15 year tech-writing career, the third edition of the “Microsoft Manual of Style for Technical Publications” was the main style reference at every company I worked at. It includes an entire chapter on writing global content. I’m not sure how many people read it.
The printed book has now been replaced by a website, and updates are more frequent (there was nearly a decade between the publication of the third and fourth editions). If you write for a technical audience, I’d recommend reading the guide in its entirety.
However, if you’re short on time these are the sections that I think are most important for writers who want to promote diversity, equity and inclusion:
To apply those lessons in my own writing, I assume my audience has English as a second language and uses a screen reader to access the text. And I have a short set of principles, in no particular order, that I try to adhere to:
It’s worth remembering that modern computing owes its foundations to diverse people including Alan Turing, Hedy Lamar, Mark Dean and Sophie Wilson.
Image: Original by Etienne Girardet.