Changes for page Simple sentences

Last modified by Lizzie Bruce on 2020/01/11 23:51

From 2.15 to 2.16 From 3.1 to 3.2

From version

2.16

edited by Lizzie Bruce
on 2019/03/07 13:11

Change comment: There is no comment for this version

To version

3.1

edited by Cass Bonner
on 2019/04/11 14:30

Change comment: Added to book title

Raw
Rendered

Summary

Page properties (4 modified, 0 added, 0 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--Clear language
++Simple sentences

Parent

@@ -1,1 +1,1 @@
--Main.WebHome
++Plain English.WebHome

Author

@@ -1,1 +1,1 @@
--xwiki:XWiki.LizzieBruce
++XWiki.CassBonner

Content

@@ -1,92 +1,53 @@
--(% class="wikigeneratedid" %)
--This helps:
++(% class="box" %)
++(((
++Following this helps:
--* **people in a hurry** – simply written content is easier to scan and absorb instantly
--* **cognitive impairments** – easy to understand words and sentences need less cognition
--* **visual impairments** – short and simple sentences convey meaning in a smaller visual field
--* **motor impairments** – it's less tiring when you can understand what you read quickly
++* **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 distracted it's hard to comprehend convoluted structures
++* **cognitive impairments** – shorter, non-complex sentences carry less cognitive load
++* **visual impairments** – short, simple sentences convey meaning in a smaller visual field
++* **motor impairments** – clear, concise content is shorted so requires less navigation
++)))
++==
++Guidelines ==
++Short, simple sentences are better on the web than long, protracted prose with complex syntax. WCAG says: "using the clearest and simplest language appropriate is highly desirable."
--== Guidelines ==
--[[Plain English>>Plain English||anchor="pe"]]
++(% class="wikigeneratedid" id="H1.MakeyouraveragesentenceA015wordslong." %)
++[[1. Make your average sentence 15 words long.>>doc:||anchor="#1"]]
--[[Simple sentences >>    ||anchor="ssl"]]
++(% class="wikigeneratedid" id="H2.A0Avoidcomplexsentencestructures." %)
++[[2. Avoid complex sentence structures.>>doc:||anchor="#2"]]
--[[Specialist terms>>Specialist terms||anchor="st"]]
--
  (% class="wikigeneratedid" %)
--Words to avoid
++[[Usability evidence>>doc:||anchor="#UESS"]]
++
++----
--== {{id name="pe"/}}Plain English ==
++==   ==
--Make content clear and understandable, to open the web up for users with different literacy levels and access challenges.
++=== {{id name="#1"/}}1. Make your average sentence 15 words long. ===
--WCAG states that "using the clearest and simplest language appropriate is highly desirable."
++The maximum sentence length for a good level of comprehension is 25 words. Split long sentences up into 2 or 3, or use bullet points.
--The United Nations recommends plain language for communications.
--
++Oxford Guide to plain English, GOV.UK and linguists agree:
--=== 1. Choose easy and short words not formal, long ones. ===
--
--Use ‘buy’ instead of ‘purchase’, ‘help’ instead of ‘assist’, and ‘about’ instead of ‘approximately’.
--
--Write for the reading comprehension of a 9 year old. This helps you reach the most users and makes your content easy to scan.
++* 15 word sentences are more likely to be comprehensible
++* 25 words is a good maximum sentence length limit
++* above 40 words sentences are hard to comprehend easily
--=== 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.
++(% class="mark" %)This sentence is about 15 words long and is easy to understand. (%%)
++
--=== 3. Write conversationally. ===
++=== {{id name="#2"/}}2. Avoid complex sentence structures. ===
--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 'plain' for one person may not be for someone else.
--
--
--== Usability evidence for plain English ==
--
--[[Guideline 3.1 Readable: Make text content readable and understandable.>>url:https://www.w3.org/TR/UNDERSTANDING-WCAG20/meaning-supplements.html]], Web Content Accessibility Guidelines (WCAG) 2.0, 2008.
--
--[['Convention on the Rights of Persons with Disabilities'>>url:http://templatelab.com/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'>>url:https://www.nngroup.com/articles/plain-language-experts/]], H. Loranger, Nielsen Norman Group, 2017
--
--[['The Public Speaks: An Empirical Study of Legal Communication'>>url:https://papers.ssrn.com/sol3/papers.cfm?abstract_id=1843415]], C. R. Trudeau in 14 Scribes J. Leg. Writing 121 2012
--
--[['Strengthening plain language'>>url:http://www.iplfederation.org/]], International Plain Language Federation. Undated.
--
--[[Plain Language Commission style guide>>url:https://www.clearest.co.uk/plain-language-commission-style-guide]], Plain Language Commission, 2011
--
--[['The principles of readability'>>url:http://www.impact-information.com/impactinfo/readability02.pdf]], Impact Information, William H. DuBay, 2004
--
--[[Plain language entry>>url:https://en.m.wikipedia.org/wiki/Plain_language]], Wikipedia, last updated 2018
--
--
--== {{id name="ssl"/}}Simple sentences ==
--
--
--=== 1. Make your average sentence 15 words long. ===
--
--The maximum sentence length we would recommend for easy comprehension is 25 words.
--
--You can split longer sentences up into 2 or 3 or restructure the content with bullet points to make meaning clearer for users.
--
--
--== 2. Avoid complex sentence structures. ==
--
  They are less easy to comprehend quickly. Understanding them requires more cognitive effort than simple sentences.
@@ -96,19 +96,20 @@
  * distribution of associated words across the sentence – how easily can the brain 'parse a phrase': recognise, connect and comprehend words that together convey meaning
-->Example:"The red fox jumped over the gate." – easier to understand
-->"The fox, which was red, over the gate jumped." – harder to understand
++Example:
++\\(% class="mark" %)"The red fox jumped over the gate." – easier to understand
++"The fox, which was red, over the gate jumped." – harder to understand
--== Usability evidence for simple sentences ==
++----
--"People with some learning disabilities read letter for letter – they do not bounce around like other users. They also cannot fully understand a sentence if it’s too long. People with moderate learning disabilities can understand sentences of 5 to 8 words without difficulty. By using common words we can help all users understand sentences of around 25 words." GOV.UK
++== {{id name="#UESS"/}}Usability evidence: simple sentences ==
--The Oxford Guide to Plain English recommends 15–20 words per sentence. It also says: "…if you regularly exceed 40 words, you’ll certainly weary and deter your readers."
++[[Oxford Guide to plain English>>https://global.oup.com/academic/product/oxford-guide-to-plain-english-9780199669172?cc=gb&lang=en&]] , Oxford University Press, 2013
--Jyoti Sanyal, author of 'Indlish' said: "Based on several studies, press associations in the USA have laid down a readability table. Their survey shows readers find sentences of 8 words or less very easy to read; 11 words, easy; 14 words fairly easy; 17 words standard; 21 words fairly difficult; 25 words difficult and 29 words or more, very difficult."
++Jyoti Sanyal 'Indlish: The book for every English-speaking Indian'
--Author Ann Wylie said: "When the average sentence length in a piece was fewer than 8 words long, readers understood 100% of the story. At 14 words, they could comprehend more than 90% of the information. But move up to 43-word sentences and comprehension dropped below 10 percent."
++[[Author Ann Wylie>>https://www.wyliecomm.com/]], Reach more readers website
  [[Writing for GOV.UK>>url:https://www.gov.uk/guidance/content-design/writing-for-gov-uk]], UK Government website
@@ -116,7 +116,7 @@
  [['Content design'>>url:https://contentdesign.london/book/]], Sarah Richards, 2017
--[['The role of word difficulty and sentence length in text comprehension'>>url:https://apps.dtic.mil/dtic/tr/fulltext/u2/a114935.pdf]], T. M. Duffy and P. K. U'Ren, 1982
++[['The role of word difficulty and sentence length in text comprehension'>>https://eric.ed.gov/?id=ED215330]], T. M. Duffy and P. K. U'Ren, 1982
  [['The Influence of Semantics and Syntax on What Readers Remember'>>url:https://www.hcde.washington.edu/files/people/docs/Isakson_Spyridakis_Sem_Syn.pdf]], C. S. Isakson and J. H. Spyridakis, 1999
@@ -151,74 +151,14 @@
  [[The Crystal Mark standard>>url:http://www.plainenglish.co.uk/services/crystal-mark/7-the-crystal-mark-standard.html]] Plain English Campaign, undated
--== {{id name="st"/}}Specialist terms: explain them ==
++----
--(% class="wikigeneratedid" %)
--Make specialist content comprehensible by non-experts.
++(% class="box" %)
++(((
++See also:
--
--=== 1. Remember that anybody can access your content. ===
--
--Assuming who your audience is, and that they'll understand the technical terms you use, are common misconceptions.
--
--
--=== 2. Create content that all users can understand, whatever their expertise or background. ===
--
--When you present a concept explain its parts and processes in detail.
--
--If you need to include a technical term consider explaining it. Make sure the surrounding language in plain language.
--
--
--=== 3. Help users understand specialist terms. ===
--
--You could:
--
--* link to an existing definition – this could be an external site
--* add a explanatory definition after using the term
--
--
-->Example:
-->
-->"It is a Palladian style stone building, and contains a number of splendid paintings and much fine wood-carving." – original sentence.
-->
-->"It is a [[Palladian style>>url:http://www.vam.ac.uk/content/articles/s/style-guide-palladianism/]] stone building, and contains a number of splendid paintings and much fine wood-carving." – with link to a definition.
--> "It is a Palladian style stone building and contains a number of splendid paintings and much fine wood-carving. Palladian style architecture features include columns, symmetry and decorative arches." – with explanatory definition.
--
--
--== Usability evidence for explaining specialist terms ==
--
--[['Writing Digital Copy for Domain Experts'>>url:https://www.nngroup.com/articles/writing-domain-experts/]], Nielson Norman Group, 2017
--
--[['Writing Digital Copy for Specialists vs. General Audiences'>>url:https://www.nngroup.com/videos/writing-digital-copy-specialists/?lm=how-users-read-on-the-web&pt=article]], Nielson Norman Group, undated
--
--[['Plain Language For Everyone, Even Experts'>>url:https://www.nngroup.com/videos/plain-language-for-experts/?lm=how-users-read-on-the-web&pt=article]] Nielson Norman Group, undated
--
--[['TechWhirl Fast 5: Understanding Plain Language and Simplified Technical English'>>url:https://techwhirl.com/techwhirl-fast-5-understanding-plain-language-simplified-technical-english/]], Connie Giordano, TechWhirl, 2017
--
--[['Advantages and disadvantages with Simplified Technical English'>>url:https://liu.diva-portal.org/smash/get/diva2:16816/FULLTEXT01]], Msc thesis paper, Karin Disborg, 2007
--
--[['Technical Writing Need Not Be Abstruse—Use Plain Language for Maximum Impact'>>url:https://digital.gov/2015/10/23/technical-writing-need-not-be-abstruse-use-plain-language-for-maximum-impact/#]], Colleen Blessing, 2015
--
--[['The Facets of the General Public as Audience'>>url:https://www.dropbox.com/s/2u2cybl7c57u0tr/AudienceIssues.pdf?dl=0]] Cheryl Stephens and Mariah Stufflebeam, 2017
--
--(% class="wikigeneratedid" %)
--We generated the [[before sentence about an architecture term>>url:http://sentence.yourdictionary.com/palladian]] from yourdictionary.com and applied our recommendations.
--
--
--(% class="wikigeneratedid" %)
--Here's some sector specific guidance:
--
--(% class="wikigeneratedid" %)
--Legal
--
--(% class="wikigeneratedid" %)
--Medical
--
--(% class="wikigeneratedid" %)
--Financial
--
--
--{{children/}}
--
--
--
++* [[Plain English>>doc:Plain English.Plain English, simple sentences.WebHome]]
++* [[Specialist terms>>doc:Plain English.Specialist terms.WebHome]]
++* [[Law, medicine, money>>doc:Plain English.Medical.WebHome]]
++* [[Words to avoid>>doc:Plain English.Words to avoid.WebHome]]
++)))

Changes for page Simple sentences

Summary

Details

Navigation