Plain English
Following this helps:
- people in a hurry – simply written content is easier to scan and absorb instantly
- people who are stressed – if you're anxious you find it harder to comprehend things
- people who are multi-tasking – if you're holding a baby or dealing with customers your attention's divided
- people with low literacy – will not know meanings of complex vocabulary and terms
- cognitive impairments – words and sentences that are easy to understand carry less cognitive load
- visual impairments – short and simple sentences convey meaning in a smaller visual field
- motor impairments – clear, concise content is shorter so requires less navigation
Guidelines
Make content clear and understandable, to open the web up for users with different literacy levels and access challenges.
1. Choose easy and short words not formal, long ones.
2. Jargon and buzzwords are unlikely to be clear language.
3. Write conversationally, in first person, using the active voice.
4. Test your content with users.
1. Choose easy and short words not formal, long ones.
Write for the reading comprehension of a 9 year old. This helps your content reach the most users. It also makes your content easier to scan read.
Web Content Accessibility Guidelines (WCAG) say: "using the clearest and simplest language appropriate is highly desirable." The United Nations recommends plain language for communications.
Examples:
"buy" not "purchase"
"help" not "assist"
"about" not "approximately"
2. Jargon and buzzwords are unlikely to be clear language.
Often, these words are too general and vague and can lead to misinterpretation or empty, meaningless text. Avoid them. Instead, think about what the term actually means and describe that. Be open and specific.
Example:
"Let's touch base in 10 and do some blue sky thinking." This uses jargon.
"Let's meet in 10 minutes to think of some ideas." Conveys same meaning using clear language.
3. Write conversationally, in first person, using the active voice.
Picture your audience and write as if you were talking directly to them, with the authority of someone who can help and inform.
4. Test your content with users.
What is clear to you may not be for someone else.
Usability evidence: plain English
Guideline 3.1 Readable: Make text content readable and understandable., Web Content Accessibility Guidelines (WCAG) 2.0, 2008
'Convention on the Rights of Persons with Disabilities', page 4 Article 2, Definitions, The United Nations Convention on the Rights of Persons with Disabilities, 2018
'Plain Language Is for Everyone, Even Experts', H. Loranger, Nielsen Norman Group, 2017
'The Public Speaks: An Empirical Study of Legal Communication', C. R. Trudeau in 14 Scribes J. Leg. Writing 121. 2012
‘Guidelines for authoring comprehensible web pages and evaluating their success’, Spyridakis, J. H., Technical Communication, pp. 368 to 73, checklist pp. 376 to 8. 2000
'Brevity. Note by the Prime Minister', W. Churchill, 1940 and 1951
‘Reading and navigational strategies of web users with lower literacy skills’, Summers, K and M. Summers, 2005
'Writing content for everyone', Roz Strachan, Government Digital Service, 2016
'Strengthening plain language', International Plain Language Federation. Undated.
Plain Language Commission style guide, Plain Language Commission, 2011
'The principles of readability', Impact Information, William H. DuBay, 2004
Plain language entry, Wikipedia, last updated 2018
‘Technical language, advice understandability, and perceptions of expertise and trustworthiness: the case of the financial planner’, Joiner, T.A., Australian Journal of Management, 27, 1, pp. 25 to 45. 2002. Locked.
‘Comprehension of legal contracts by non-experts: effectiveness of plain language redrafting', Masson, M.E.J. and M.A. Waldron, Applied Cognitive Psychology, 8,19. 1994
‘More individual difference in language attainment: how much do adult native speakers know about passives and quantifiers’, Street, J. and E. Dabrowska, Lingua, 120, pp. 2080 to 94. 2010. Locked.
‘Problems in public documents’, Rose, A., Information Design Journal, 2/3, 4, pp. 179 to 196. 1981. Locked.
‘What makes a good document? The criteria we use’, Waller, R., Simplification Centre Technical paper no. 2, Reading: University of Reading, 2011
‘Revising functional documents: the scenario principle’, Flower, L., Hayes J. R., and Swarts, H., in P. V. Anderson, R. J. Brockman and C. R. Miller (eds) New essays in technical and scientific communication: research, theory and practice, Farmingdale, NY: Baywood Publishing Co, pp. 109 to 36. 1983. Locked.
‘Dyslexia and accessibility/usability: a research review’, McCarthy, J., 2006