Changes for page Simple sentences
Last modified by Lizzie Bruce on 2020/01/11 23:51
From version 
2.20 
2.20
edited by Lizzie Bruce
on 2019/03/07 13:30
on 2019/03/07 13:30
Change comment:
There is no comment for this version
To version 2.15
2.15
edited by Lizzie Bruce
on 2019/03/07 12:52
on 2019/03/07 12:52
Change comment:
There is no comment for this version
Summary
Details
-
Page properties
-
- Content
-
... ... @@ -7,25 +7,19 @@ 7 7 * **motor impairments** – it's less tiring when you can understand what you read quickly 8 8 9 9 10 + 10 10 == Guidelines == 11 11 12 12 [[Plain English>>Plain English||anchor="pe"]] 13 13 14 -[[Simple sentences>>||anchor="ssl"]] 15 +[[Simple sentences >> ||anchor="ssl"]] 15 15 16 - [[Specialist terms>>||anchor="st"]]17 +Specialist terms 17 17 18 -[[Medicine, money and law>>doc:.Medical.WebHome]] 19 - 20 20 (% class="wikigeneratedid" %) 21 - [[Words to avoid>>doc:.Words to avoid.WebHome]]20 +Words to avoid 22 22 23 23 24 ----- 25 - 26 -(% class="wikigeneratedid" %) 27 -== == 28 - 29 29 == {{id name="pe"/}}Plain English == 30 30 31 31 Make content clear and understandable, to open the web up for users with different literacy levels and access challenges. ... ... @@ -81,11 +81,6 @@ 81 81 [[Plain language entry>>url:https://en.m.wikipedia.org/wiki/Plain_language]], Wikipedia, last updated 2018 82 82 83 83 84 ----- 85 - 86 -(% class="wikigeneratedid" %) 87 -== == 88 - 89 89 == {{id name="ssl"/}}Simple sentences == 90 90 91 91 ... ... @@ -96,7 +96,7 @@ 96 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 97 98 98 99 -== =2. Avoid complex sentence structures. ===88 +== 2. Avoid complex sentence structures. == 100 100 101 101 They are less easy to comprehend quickly. Understanding them requires more cognitive effort than simple sentences. 102 102 ... ... @@ -105,12 +105,14 @@ 105 105 106 106 * number of clauses in a sentence, the more clauses the more complex it is 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 - 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 112 112 99 +Example: 113 113 101 +"The red fox jumped over the gate." – easier to understand 102 +"The fox, which was red, over the gate jumped." – harder to understand 103 + 104 + 114 114 == Usability evidence for simple sentences == 115 115 116 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 ... ... @@ -162,68 +162,20 @@ 162 162 [[The Crystal Mark standard>>url:http://www.plainenglish.co.uk/services/crystal-mark/7-the-crystal-mark-standard.html]] Plain English Campaign, undated 163 163 164 164 165 ----- 156 +(% class="wikigeneratedid" %) 157 +Here's some sector specific guidance: 166 166 167 167 (% class="wikigeneratedid" %) 168 - == ==160 +Legal 169 169 170 -== {{id name="st"/}}Specialist terms == 162 +(% class="wikigeneratedid" %) 163 +Medical 171 171 172 172 (% class="wikigeneratedid" %) 173 - Make specialist contentcomprehensibleby non-experts.166 +Financial 174 174 175 175 176 - === 1. Explain specialist terms: anybody can access yourcontent. ===169 +{{children/}} 177 177 178 -Assuming who your audience is, and that they'll understand the technical terms you use, are common misconceptions. 179 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 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]]!