Changes for page Simple sentences

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -7,6 +7,7 @@
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,14 +13,11 @@
13	13
14	14	[[Simple sentences >> ||anchor="ssl"]]
15	15
16		-[[Specialist terms>>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		-----
24	24
25	25	== {{id name="pe"/}}Plain English ==
26	26
...	...	@@ -76,7 +76,6 @@
76	76
77	77	[[Plain language entry>>url:https://en.m.wikipedia.org/wiki/Plain_language]], Wikipedia, last updated 2018
78	78
79		-----
80	80
81	81	== {{id name="ssl"/}}Simple sentences ==
82	82
...	...	@@ -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
...	...	@@ -153,64 +153,21 @@
153	153
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		-----
157	157
158		-== {{id name="st"/}}Specialist terms: explain them ==
	156	+(% class="wikigeneratedid" %)
	157	+Here's some sector specific guidance:
159	159
160	160	(% class="wikigeneratedid" %)
161		-Make specialist content comprehensible by non-experts.
	160	+Legal
162	162
	162	+(% class="wikigeneratedid" %)
	163	+Medical
163	163
164		-=== 1. Remember that anybody can access your content. ===
	165	+(% class="wikigeneratedid" %)
	166	+Financial
165	165
166		-Assuming who your audience is, and that they'll understand the technical terms you use, are common misconceptions.
167	167
	169	+{{children/}}
168	168
169		-=== 2. Create content that all users can understand, whatever their expertise or background. ===
170	170
171		-When you present a concept explain its parts and processes in detail.
172		-
173		-If you need to include a technical term consider explaining it. Make sure the surrounding language in plain language.
174		-
175		-
176		-=== 3. Help users understand specialist terms. ===
177		-
178		-You could:
179		-
180		-* link to an existing definition – this could be an external site
181		-* add a explanatory definition after using the term
182	182
183		-
184		->Example:
185		->
186		->"It is a Palladian style stone building, and contains a number of splendid paintings and much fine wood-carving." – original sentence.
187		->
188		->"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.
189		-> "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.
190		-
191		-
192		-== Usability evidence for explaining specialist terms ==
193		-
194		-[['Writing Digital Copy for Domain Experts'>>url:https://www.nngroup.com/articles/writing-domain-experts/]], Nielson Norman Group, 2017
195		-
196		-[['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
197		-
198		-[['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
199		-
200		-[['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
201		-
202		-[['Advantages and disadvantages with Simplified Technical English'>>url:https://liu.diva-portal.org/smash/get/diva2:16816/FULLTEXT01]], Msc thesis paper, Karin Disborg, 2007
203		-
204		-[['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
205		-
206		-[['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
207		-
208		-(% class="wikigeneratedid" %)
209		-We generated the [[before sentence about an architecture term>>url:http://sentence.yourdictionary.com/palladian]] from yourdictionary.com and applied our recommendations.
210		-
211		-
212		-(% class="wikigeneratedid" %)
213		-Here's some sector specific guidance for [[medicine, money and law>>doc:.Medical.WebHome]].
214		-
215		-
216		-And here's our list of jargon [[words to avoid>>doc:.Words to avoid.WebHome]]!