Changes for page Simple sentences

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

From version Icon 2.15 Icon
edited by Lizzie Bruce
on 2019/03/07 12:52
Change comment: There is no comment for this version
To version Icon 2.20 Icon
edited by Lizzie Bruce
on 2019/03/07 13:30
Change comment: There is no comment for this version

Summary

Details

Icon Page properties
Content
... ... @@ -7,19 +7,25 @@
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 -[[Simple sentences >> ||anchor="ssl"]]
14 +[[Simple sentences>>||anchor="ssl"]]
16 16  
17 -Specialist terms
16 +[[Specialist terms>>||anchor="st"]]
18 18  
18 +[[Medicine, money and law>>doc:.Medical.WebHome]]
19 +
19 19  (% class="wikigeneratedid" %)
20 -Words to avoid
21 +[[Words to avoid>>doc:.Words to avoid.WebHome]]
21 21  
22 22  
24 +----
25 +
26 +(% class="wikigeneratedid" %)
27 +== ==
28 +
23 23  == {{id name="pe"/}}Plain English ==
24 24  
25 25  Make content clear and understandable, to open the web up for users with different literacy levels and access challenges.
... ... @@ -75,6 +75,11 @@
75 75  [[Plain language entry>>url:https://en.m.wikipedia.org/wiki/Plain_language]], Wikipedia, last updated 2018
76 76  
77 77  
84 +----
85 +
86 +(% class="wikigeneratedid" %)
87 +== ==
88 +
78 78  == {{id name="ssl"/}}Simple sentences ==
79 79  
80 80  
... ... @@ -85,7 +85,7 @@
85 85  You can split longer sentences up into 2 or 3 or restructure the content with bullet points to make meaning clearer for users.
86 86  
87 87  
88 -== 2. Avoid complex sentence structures. ==
99 +=== 2. Avoid complex sentence structures. ===
89 89  
90 90  They are less easy to comprehend quickly. Understanding them requires more cognitive effort than simple sentences.
91 91  
... ... @@ -94,14 +94,12 @@
94 94  
95 95  * number of clauses in a sentence, the more clauses the more complex it is
96 96  * 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 +
97 97  
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
98 98  
99 -Example:
100 100  
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 -
105 105  == Usability evidence for simple sentences ==
106 106  
107 107  "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
... ... @@ -153,20 +153,68 @@
153 153  [[The Crystal Mark standard>>url:http://www.plainenglish.co.uk/services/crystal-mark/7-the-crystal-mark-standard.html]] Plain English Campaign, undated
154 154  
155 155  
156 -(% class="wikigeneratedid" %)
157 -Here's some sector specific guidance:
165 +----
158 158  
159 159  (% class="wikigeneratedid" %)
160 -Legal
168 +== ==
161 161  
162 -(% class="wikigeneratedid" %)
163 -Medical
170 +== {{id name="st"/}}Specialist terms ==
164 164  
165 165  (% class="wikigeneratedid" %)
166 -Financial
173 +Make specialist content comprehensible by non-experts.
167 167  
168 168  
169 -{{children/}}
176 +=== 1. Explain specialist terms: anybody can access your content. ===
170 170  
178 +Assuming who your audience is, and that they'll understand the technical terms you use, are common misconceptions.
171 171  
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
172 172  
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]]!