Changes for page Simple sentences

Summary

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

Details

Page properties

Content

...	...	@@ -7,22 +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	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.
...	...	@@ -78,8 +78,6 @@
78	78	[[Plain language entry>>url:https://en.m.wikipedia.org/wiki/Plain_language]], Wikipedia, last updated 2018
79	79
80	80
81		-----
82		-
83	83	== {{id name="ssl"/}}Simple sentences ==
84	84
85	85
...	...	@@ -90,7 +90,7 @@
90	90	You can split longer sentences up into 2 or 3 or restructure the content with bullet points to make meaning clearer for users.
91	91
92	92
93		-=== 2. Avoid complex sentence structures. ===
	88	+== 2. Avoid complex sentence structures. ==
94	94
95	95	They are less easy to comprehend quickly. Understanding them requires more cognitive effort than simple sentences.
96	96
...	...	@@ -99,12 +99,14 @@
99	99
100	100	* number of clauses in a sentence, the more clauses the more complex it is
101	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	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	106
	99	+Example:
107	107
	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	+
108	108	== Usability evidence for simple sentences ==
109	109
110	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
...	...	@@ -156,64 +156,20 @@
156	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	157
158	158
159		-----
	156	+(% class="wikigeneratedid" %)
	157	+Here's some sector specific guidance:
160	160
161		-== {{id name="st"/}}Specialist terms: explain them ==
	159	+(% class="wikigeneratedid" %)
	160	+Legal
162	162
163	163	(% class="wikigeneratedid" %)
164		-Make specialist content comprehensible by non-experts.
	163	+Medical
165	165
	165	+(% class="wikigeneratedid" %)
	166	+Financial
166	166
167		-=== 1. Remember that anybody can access your content. ===
168	168
169		-Assuming who your audience is, and that they'll understand the technical terms you use, are common misconceptions.
	169	+{{children/}}
170	170
171	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
185	185
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]]!