Skip to Content

Changes for page Simple sentences

Last modified by Lizzie Bruce on 2020/01/11 23:51
From version Icon 2.14 Icon
edited by Lizzie Bruce
on 2019/03/07 11:55
Change comment: There is no comment for this version
To version Icon 2.19 Icon
edited by Lizzie Bruce
on 2019/03/07 13:25
Change comment: There is no comment for this version

Summary

Details

Icon Page properties
Content
... ... @@ -3,25 +3,26 @@
3 3  
4 4  * **people in a hurry** – simply written content is easier to scan and absorb instantly
5 5  * **cognitive impairments** – easy to understand words and sentences need less cognition
6 -* **visual impairments** – short and simple sentences convey meaning in a smaller field of focus
6 +* **visual impairments** – short and simple sentences convey meaning in a smaller visual field
7 7  * **motor impairments** – it's less tiring when you can understand what you read quickly
8 8  
9 9  
10 -
11 11  == Guidelines ==
12 12  
13 13  [[Plain English>>Plain English||anchor="pe"]]
14 14  
15 -[[Sentence length>> ||anchor="ssl"]]
14 +[[Simple sentences>>||anchor="ssl"]]
16 16  
17 -Sentence structure
16 +[[Specialist terms>>||anchor="st"]]
18 18  
19 -Specialist terms
18 +[[Medicine, money and law>>doc:.Medical.WebHome]]
20 20  
21 21  (% class="wikigeneratedid" %)
22 -Words to avoid
21 +[[Words to avoid>>doc:.Words to avoid.WebHome]]
23 23  
24 24  
24 +----
25 +
25 25  == {{id name="pe"/}}Plain English ==
26 26  
27 27  Make content clear and understandable, to open the web up for users with different literacy levels and access challenges.
... ... @@ -77,27 +77,142 @@
77 77  [[Plain language entry>>url:https://en.m.wikipedia.org/wiki/Plain_language]], Wikipedia, last updated 2018
78 78  
79 79  
80 -== {{id name="ssl"/}}Short sentence length ==
81 +----
81 81  
83 +== {{id name="ssl"/}}Simple sentences ==
82 82  
83 83  
84 -== Simple sentence structure ==
86 +=== 1. Make your average sentence 15 words long. ===
85 85  
88 +The maximum sentence length we would recommend for easy comprehension is 25 words.
86 86  
87 -(% class="wikigeneratedid" %)
88 -Here's some sector specific guidance:
90 +You can split longer sentences up into 2 or 3 or restructure the content with bullet points to make meaning clearer for users.
89 89  
90 -(% class="wikigeneratedid" %)
91 -Legal
92 92  
93 -(% class="wikigeneratedid" %)
94 -Medical
93 +=== 2. Avoid complex sentence structures. ===
95 95  
95 +They are less easy to comprehend quickly. Understanding them requires more cognitive effort than simple sentences.
96 +
97 +
98 +Complexity depends on:
99 +
100 +* number of clauses in a sentence, the more clauses the more complex it is
101 +* distribution of associated words across the sentence – how easily can the brain 'parse a phrase': recognise, connect and comprehend words that together convey meaning
102 +
103 +
104 +>Example:"The red fox jumped over the gate." – easier to understand 
105 +>"The fox, which was red, over the gate jumped." – harder to understand
106 +
107 +
108 +== Usability evidence for simple sentences ==
109 +
110 +"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
111 +
112 +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."
113 +
114 +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."
115 +
116 +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."
117 +
118 +[[Writing for GOV.UK>>url:https://www.gov.uk/guidance/content-design/writing-for-gov-uk]], UK Government website
119 +
120 +[['Sentence length: why 25 words is our limit'>>url:https://insidegovuk.blog.gov.uk/2014/08/04/sentence-length-why-25-words-is-our-limit/]], Inside GOV.UK, UK Government blog, 2014
121 +
122 +[['Content design'>>url:https://contentdesign.london/book/]], Sarah Richards, 2017
123 +
124 +[['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
125 +
126 +[['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
127 +
128 +[['How the brain attunes to sentence processing: Relating behavior, structure, and function'>>url:https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4819595/]], A. Fengler, L. Meyer, A. D. Friederici, National Center for Biotechnology Information
129 +
130 +[['Functional Analysis of Clause Complex in the Language of News Websites Texts: A Comparative Study of Two Articles'>>url:http://www.ijsrp.org/research-paper-0616/ijsrp-p5445.pdf]], F. M. S. Eid, International Journal of Scientific and Research Publications, Volume 6, Issue 6, June 2016
131 +
132 +[[Reading Level>>url:https://www.w3.org/TR/UNDERSTANDING-WCAG20/meaning-supplements.html]], Understanding SC 3.1.5, WCAG, 2008
133 +
134 +[['Readability Assessment of Internet-Based Consumer Health Information'>>url:http://rc.rcjournal.com/content/53/10/1310/tab-pdf]], T. M. Walsh and T. A. Volsko in Respiratory Care October 2008, 53 (10) 1310-1315
135 +
136 +[['The research basis of plain language techniques: Implications for establishing standards'>>url:https://www.researchgate.net/profile/Karen_Schriver/publication/285927928_The_research_basis_of_plain_language_techniques_Implications_for_establishing_standards/links/5664c50208ae192bbf90aa85/The-research-basis-of-plain-language-techniques-Implications-for-establishing-standards.pdf]], Karen Schriver, PhD, Dr. A. L. Cheek, M. Mercer, Center for Plain Language, November 20, 2008, Mexico City
137 +
138 +[['Readability Levels of Health-Based Websites: From Content to Comprehension'>>url:https://files.eric.ed.gov/fulltext/EJ851863.pdf]], M. Schutten, A. McFarland, PhD, International Electronic Journal of Health Education, 2009, 12:99-107
139 +
140 +[['Writing smaller'>>url:http://clarity-international.net/journals/63.pdf]], Clarity Journal no. 63, 2010
141 +
142 +[[Plain Language Commission style guide>>url:https://irp-cdn.multiscreensite.com/aaf9e928/files/uploaded/PLCstyleguide25July2012.pdf]], 2012
143 +
144 +[['Shorter Lines Facilitate Reading in Those Who Struggle'>>url:https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0071161]], Matthew H. Schneps , Jenny M. Thomson, Gerhard Sonnert, Marc Pomplun, Chen Chen, Amanda Heffner-Wong, 2013
145 +
146 +[['Towards a better measure of readability: Explanation of empirical performance results'>>url:https://www.tandfonline.com/doi/pdf/10.1080/00437956.1989.11435805]], Leslie A. Olsen & Rod Johnson, Taylor & Francis Group, 2015
147 +
148 +[['What is plain language?'>>url:https://plainlanguagenetwork.org/plain-language/what-is-plain-language/]], Plain Language Association International, 2015
149 +
150 +[[Text complexity, ATOS, and Lexile® Measures>>url:https://www.renaissance.com/products/practice/accelerated-reader-360/atos-and-text-complexity/]], Renaissance Learning, 2016
151 +
152 +[['Understanding Plain English summaries. A comparison of two approaches to improve the quality of Plain English summaries in research reports.'>>url:https://researchinvolvement.biomedcentral.com/articles/10.1186/s40900-017-0064-0]] 2017
153 +
154 +[['How to use Yoast SEO: The readability analysis?'>>url:https://yoast.com/yoast-seo-readability-analysis/]] Edwin Toonen, Yoast, 2018
155 +
156 +[[The Crystal Mark standard>>url:http://www.plainenglish.co.uk/services/crystal-mark/7-the-crystal-mark-standard.html]] Plain English Campaign, undated
157 +
158 +
159 +----
160 +
161 +== {{id name="st"/}}Specialist terms: explain them ==
162 +
96 96  (% class="wikigeneratedid" %)
97 -Financial
164 +Make specialist content comprehensible by non-experts.
98 98  
99 99  
100 -{{children/}}
167 +=== 1. Remember that anybody can access your content. ===
101 101  
169 +Assuming who your audience is, and that they'll understand the technical terms you use, are common misconceptions.
102 102  
171 +
172 +=== 2. Create content that all users can understand, whatever their expertise or background. ===
173 +
174 +When you present a concept explain its parts and processes in detail.
175 +
176 +If you need to include a technical term consider explaining it. Make sure the surrounding language in plain language.
177 +
178 +
179 +=== 3. Help users understand specialist terms. ===
180 +
181 +You could:
182 +
183 +* link to an existing definition – this could be an external site
184 +* add a explanatory definition after using the term
103 103  
186 +
187 +>Example:
188 +>
189 +>"It is a Palladian style stone building, and contains a number of splendid paintings and much fine wood-carving." – original sentence.
190 +>
191 +>"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.
192 +> "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.
193 +
194 +
195 +== Usability evidence for explaining specialist terms ==
196 +
197 +[['Writing Digital Copy for Domain Experts'>>url:https://www.nngroup.com/articles/writing-domain-experts/]], Nielson Norman Group, 2017
198 +
199 +[['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
200 +
201 +[['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
202 +
203 +[['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
204 +
205 +[['Advantages and disadvantages with Simplified Technical English'>>url:https://liu.diva-portal.org/smash/get/diva2:16816/FULLTEXT01]], Msc thesis paper, Karin Disborg, 2007
206 +
207 +[['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
208 +
209 +[['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
210 +
211 +(% class="wikigeneratedid" %)
212 +We generated the [[before sentence about an architecture term>>url:http://sentence.yourdictionary.com/palladian]] from yourdictionary.com and applied our recommendations.
213 +
214 +
215 +(% class="wikigeneratedid" %)
216 +Here's some sector specific guidance for [[medicine, money and law>>doc:.Medical.WebHome]].
217 +
218 +
219 +And here's our list of jargon [[words to avoid>>doc:.Words to avoid.WebHome]]!