Changes for page Simple sentences
Last modified by Lizzie Bruce on 2020/01/11 23:51
From version 2.17
edited by Lizzie Bruce
on 2019/03/07 13:14
on 2019/03/07 13:14
Change comment:
There is no comment for this version
To version 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
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -14,15 +14,12 @@ 14 14 15 15 [[Simple sentences >> ||anchor="ssl"]] 16 16 17 - [[Specialist terms>>Specialist terms||anchor="st"]]17 +Specialist terms 18 18 19 19 (% class="wikigeneratedid" %) 20 20 Words to avoid 21 21 22 -(% class="wikigeneratedid" %) 23 -Medicine, money and law 24 24 25 - 26 26 == {{id name="pe"/}}Plain English == 27 27 28 28 Make content clear and understandable, to open the web up for users with different literacy levels and access challenges. ... ... @@ -97,12 +97,14 @@ 97 97 98 98 * number of clauses in a sentence, the more clauses the more complex it is 99 99 * distribution of associated words across the sentence – how easily can the brain 'parse a phrase': recognise, connect and comprehend words that together convey meaning 100 - 101 101 102 ->Example:"The red fox jumped over the gate." – easier to understand 103 ->"The fox, which was red, over the gate jumped." – harder to understand 104 104 99 +Example: 105 105 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 + 106 106 == Usability evidence for simple sentences == 107 107 108 108 "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 ... ... @@ -154,63 +154,20 @@ 154 154 [[The Crystal Mark standard>>url:http://www.plainenglish.co.uk/services/crystal-mark/7-the-crystal-mark-standard.html]] Plain English Campaign, undated 155 155 156 156 157 -== {{id name="st"/}}Specialist terms: explain them == 156 +(% class="wikigeneratedid" %) 157 +Here's some sector specific guidance: 158 158 159 159 (% class="wikigeneratedid" %) 160 - Makespecialist content comprehensible by non-experts.160 +Legal 161 161 162 - 163 -=== 1. Remember that anybody can access your content. === 164 - 165 -Assuming who your audience is, and that they'll understand the technical terms you use, are common misconceptions. 166 - 167 - 168 -=== 2. Create content that all users can understand, whatever their expertise or background. === 169 - 170 -When you present a concept explain its parts and processes in detail. 171 - 172 -If you need to include a technical term consider explaining it. Make sure the surrounding language in plain language. 173 - 174 - 175 -=== 3. Help users understand specialist terms. === 176 - 177 -You could: 178 - 179 -* link to an existing definition – this could be an external site 180 -* add a explanatory definition after using the term 181 - 182 - 183 ->Example: 184 -> 185 ->"It is a Palladian style stone building, and contains a number of splendid paintings and much fine wood-carving." – original sentence. 186 -> 187 ->"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. 188 -> "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. 189 - 190 - 191 -== Usability evidence for explaining specialist terms == 192 - 193 -[['Writing Digital Copy for Domain Experts'>>url:https://www.nngroup.com/articles/writing-domain-experts/]], Nielson Norman Group, 2017 194 - 195 -[['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 196 - 197 -[['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 198 - 199 -[['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 200 - 201 -[['Advantages and disadvantages with Simplified Technical English'>>url:https://liu.diva-portal.org/smash/get/diva2:16816/FULLTEXT01]], Msc thesis paper, Karin Disborg, 2007 202 - 203 -[['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 204 - 205 -[['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 206 - 207 207 (% class="wikigeneratedid" %) 208 - Wegeneratedthe [[before sentence about an architecture term>>url:http://sentence.yourdictionary.com/palladian]] from yourdictionary.com and applied our recommendations.163 +Medical 209 209 210 - 211 211 (% class="wikigeneratedid" %) 212 - Here's some sector specific guidance for medicine, moneyandlaw.166 +Financial 213 213 168 + 214 214 {{children/}} 215 215 171 + 216 216