Skip to Content

Changes for page Simple sentences

Last modified by Lizzie Bruce on 2020/01/11 23:51
From version Icon 2.20 Icon
edited by Lizzie Bruce
on 2019/03/07 13:30
Change comment: There is no comment for this version
To version Icon 3.1 Icon
edited by Cass Bonner
on 2019/04/11 14:30
Change comment: Added to book title

Summary

Details

Icon Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Clear language
1 +Simple sentences
Parent
... ... @@ -1,1 +1,1 @@
1 -Main.WebHome
1 +Plain English.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.LizzieBruce
1 +XWiki.CassBonner
Content
... ... @@ -1,103 +1,53 @@
1 -(% class="wikigeneratedid" %)
2 -This helps:
1 +(% class="box" %)
2 +(((
3 +Following this helps:
3 3  
4 -* **people in a hurry** – simply written content is easier to scan and absorb instantly
5 -* **cognitive impairments** – easy to understand words and sentences need less cognition
6 -* **visual impairments** – short and simple sentences convey meaning in a smaller visual field
7 -* **motor impairments** – it's less tiring when you can understand what you read quickly
5 +* **people in a hurry** – simply written content is easier to scan and absorb instantly
6 +* **people who are stressed** – if you're anxious you find it harder to comprehend things
7 +* **people who are multi-tasking** – if you're distracted it's hard to comprehend convoluted structures
8 +* **cognitive impairments** – shorter, non-complex sentences carry less cognitive load
9 +* **visual impairments** – short, simple sentences convey meaning in a smaller visual field
10 +* **motor impairments** – clear, concise content is shorted so requires less navigation
11 +)))
8 8  
13 +==
14 +Guidelines ==
9 9  
10 -== Guidelines ==
16 +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."
11 11  
12 -[[Plain English>>Plain English||anchor="pe"]]
13 13  
14 -[[Simple sentences>>||anchor="ssl"]]
19 +(% class="wikigeneratedid" id="H1.MakeyouraveragesentenceA015wordslong." %)
20 +[[1. Make your average sentence 15 words long.>>doc:||anchor="#1"]]
15 15  
16 -[[Specialist terms>>||anchor="st"]]
22 +(% class="wikigeneratedid" id="H2.A0Avoidcomplexsentencestructures." %)
23 +[[2. Avoid complex sentence structures.>>doc:||anchor="#2"]]
17 17  
18 -[[Medicine, money and law>>doc:.Medical.WebHome]]
19 -
20 20  (% class="wikigeneratedid" %)
21 -[[Words to avoid>>doc:.Words to avoid.WebHome]]
26 +[[Usability evidence>>doc:||anchor="#UESS"]]
27 +
22 22  
23 -
24 24  ----
25 25  
26 -(% class="wikigeneratedid" %)
27 27  == ==
28 28  
29 -== {{id name="pe"/}}Plain English ==
33 +=== {{id name="#1"/}}1. Make your average sentence 15 words long. ===
30 30  
31 -Make content clear and understandable, to open the web up for users with different literacy levels and access challenges.
35 +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.
32 32  
33 -WCAG states that "using the clearest and simplest language appropriate is highly desirable."
37 +Oxford Guide to plain English, GOV.UK and linguists agree:
34 34  
35 -The United Nations recommends plain language for communications.
39 +* 15 word sentences are more likely to be comprehensible
40 +* 25 words is a good maximum sentence length limit
41 +* above 40 words sentences are hard to comprehend easily
36 36  
37 37  
38 -=== 1. Choose easy and short words not formal, long ones. ===
44 +Example:
39 39  
40 -Use ‘buy’ instead of ‘purchase’, ‘help’ instead of ‘assist’, and ‘about’ instead of ‘approximately’.
41 -
42 -Write for the reading comprehension of a 9 year old. This helps you reach the most users and makes your content easy to scan.
46 +(% class="mark" %)This sentence is about 15 words long and is easy to understand. (%%)
43 43  
44 44  
45 -=== 2. Jargon and buzzwords are unlikely to be clear language. ===
49 +=== {{id name="#2"/}}2. Avoid complex sentence structures. ===
46 46  
47 -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.
48 -
49 -
50 -Example:
51 -"Let's touch base in 10 and do some blue sky thinking." This uses jargon.
52 -"Let's meet in 10 minutes to think of some ideas." Conveys same meaning using clear language.
53 -
54 -
55 -=== 3. Write conversationally. ===
56 -
57 -Picture your audience and write as if you were talking directly to them, with the authority of someone who can help and inform.
58 -
59 -
60 -=== 4. Test your content with users ===
61 -
62 -What is 'plain' for one person may not be for someone else.
63 -
64 -
65 -== Usability evidence for plain English ==
66 -
67 -[[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.
68 -
69 -[['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.
70 -
71 -[['Plain Language Is for Everyone, Even Experts'>>url:https://www.nngroup.com/articles/plain-language-experts/]], H. Loranger, Nielsen Norman Group, 2017
72 -
73 -[['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
74 -
75 -[['Strengthening plain language'>>url:http://www.iplfederation.org/]], International Plain Language Federation. Undated.
76 -
77 -[[Plain Language Commission style guide>>url:https://www.clearest.co.uk/plain-language-commission-style-guide]], Plain Language Commission, 2011
78 -
79 -[['The principles of readability'>>url:http://www.impact-information.com/impactinfo/readability02.pdf]], Impact Information, William H. DuBay, 2004
80 -
81 -[[Plain language entry>>url:https://en.m.wikipedia.org/wiki/Plain_language]], Wikipedia, last updated 2018
82 -
83 -
84 -----
85 -
86 -(% class="wikigeneratedid" %)
87 -== ==
88 -
89 -== {{id name="ssl"/}}Simple sentences ==
90 -
91 -
92 -=== 1. Make your average sentence 15 words long. ===
93 -
94 -The maximum sentence length we would recommend for easy comprehension is 25 words.
95 -
96 -You can split longer sentences up into 2 or 3 or restructure the content with bullet points to make meaning clearer for users.
97 -
98 -
99 -=== 2. Avoid complex sentence structures. ===
100 -
101 101  They are less easy to comprehend quickly. Understanding them requires more cognitive effort than simple sentences.
102 102  
103 103  
... ... @@ -107,19 +107,20 @@
107 107  * distribution of associated words across the sentence – how easily can the brain 'parse a phrase': recognise, connect and comprehend words that together convey meaning
108 108  
109 109  
110 ->Example:"The red fox jumped over the gate." – easier to understand 
111 ->"The fox, which was red, over the gate jumped." – harder to understand
60 +Example:
61 +\\(% class="mark" %)"The red fox jumped over the gate." – easier to understand 
62 +"The fox, which was red, over the gate jumped." – harder to understand
112 112  
113 113  
114 -== Usability evidence for simple sentences ==
65 +----
115 115  
116 -"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
67 +== {{id name="#UESS"/}}Usability evidence: simple sentences ==
117 117  
118 -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."
69 +[[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
119 119  
120 -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."
71 +Jyoti Sanyal 'Indlish: The book for every English-speaking Indian'
121 121  
122 -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."
73 +[[Author Ann Wylie>>https://www.wyliecomm.com/]], Reach more readers website
123 123  
124 124  [[Writing for GOV.UK>>url:https://www.gov.uk/guidance/content-design/writing-for-gov-uk]], UK Government website
125 125  
... ... @@ -127,7 +127,7 @@
127 127  
128 128  [['Content design'>>url:https://contentdesign.london/book/]], Sarah Richards, 2017
129 129  
130 -[['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
81 +[['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
131 131  
132 132  [['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
133 133  
... ... @@ -164,66 +164,12 @@
164 164  
165 165  ----
166 166  
167 -(% class="wikigeneratedid" %)
168 -== ==
118 +(% class="box" %)
119 +(((
120 +See also:
169 169  
170 -== {{id name="st"/}}Specialist terms ==
171 -
172 -(% class="wikigeneratedid" %)
173 -Make specialist content comprehensible by non-experts.
174 -
175 -
176 -=== 1. Explain specialist terms: anybody can access your content. ===
177 -
178 -Assuming who your audience is, and that they'll understand the technical terms you use, are common misconceptions.
179 -
180 -
181 -=== 2. Create content that all users can understand, whatever their expertise or background. ===
182 -
183 -When you present a concept explain its parts and processes in detail.
184 -
185 -If you need to include a technical term consider explaining it. Make sure the surrounding language in plain language.
186 -
187 -
188 -=== 3. Help users understand specialist terms. ===
189 -
190 -You could:
191 -
192 -* link to an existing definition – this could be an external site
193 -* add a explanatory definition after using the term
194 -
195 -
196 ->Example:
197 ->
198 ->"It is a Palladian style stone building, and contains a number of splendid paintings and much fine wood-carving." – original sentence.
199 ->
200 ->"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.
201 -> "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.
202 -
203 -
204 -== Usability evidence for explaining specialist terms ==
205 -
206 -[['Writing Digital Copy for Domain Experts'>>url:https://www.nngroup.com/articles/writing-domain-experts/]], Nielson Norman Group, 2017
207 -
208 -[['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
209 -
210 -[['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
211 -
212 -[['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
213 -
214 -[['Advantages and disadvantages with Simplified Technical English'>>url:https://liu.diva-portal.org/smash/get/diva2:16816/FULLTEXT01]], Msc thesis paper, Karin Disborg, 2007
215 -
216 -[['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
217 -
218 -[['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
219 -
220 -
221 -(% class="wikigeneratedid" %)
222 -We generated the [[original sentence about a specialist architecture term>>url:http://sentence.yourdictionary.com/palladian]] from yourdictionary.com.
223 -
224 -
225 -(% class="wikigeneratedid" %)
226 -Here's some sector specific guidance for [[medicine, money and law>>doc:.Medical.WebHome]].
227 -
228 -
229 -And here's our list of jargon [[words to avoid>>doc:.Words to avoid.WebHome]]!
122 +* [[Plain English>>doc:Plain English.Plain English, simple sentences.WebHome]]
123 +* [[Specialist terms>>doc:Plain English.Specialist terms.WebHome]]
124 +* [[Law, medicine, money>>doc:Plain English.Medical.WebHome]]
125 +* [[Words to avoid>>doc:Plain English.Words to avoid.WebHome]]
126 +)))