Changes for page Simple sentences

Summary

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

Details

Page properties

Content

...	...	@@ -14,7 +14,7 @@
14	14
15	15	[[Simple sentences >> ||anchor="ssl"]]
16	16
17		-Specialist terms
	17	+[[Specialist terms>>Specialist terms||anchor="st"]]
18	18
19	19	(% class="wikigeneratedid" %)
20	20	Words to avoid
...	...	@@ -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
	97	+
97	97
	99	+>Example:"The red fox jumped over the gate." – easier to understand
	100	+>"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,7 +153,61 @@
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
	154	+== {{id name="st"/}}Specialist terms: explain them ==
	155	+
156	156	(% class="wikigeneratedid" %)
	157	+Make specialist content comprehensible by non-experts.
	158	+
	159	+
	160	+=== 1. Remember that anybody can access your content. ===
	161	+
	162	+Assuming who your audience is, and that they'll understand the technical terms you use, are common misconceptions.
	163	+
	164	+
	165	+=== 2. Create content that all users can understand, whatever their expertise or background. ===
	166	+
	167	+When you present a concept explain its parts and processes in detail.
	168	+
	169	+If you need to include a technical term consider explaining it. Make sure the surrounding language in plain language.
	170	+
	171	+
	172	+=== 3. Help users understand specialist terms. ===
	173	+
	174	+You could:
	175	+
	176	+* link to an existing definition – this could be an external site
	177	+* add a explanatory definition after using the term
	178	+
	179	+
	180	+>Example:
	181	+>
	182	+>"It is a Palladian style stone building, and contains a number of splendid paintings and much fine wood-carving." – original sentence.
	183	+>
	184	+>"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.
	185	+> "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.
	186	+
	187	+
	188	+== Usability evidence for explaining specialist terms ==
	189	+
	190	+[['Writing Digital Copy for Domain Experts'>>url:https://www.nngroup.com/articles/writing-domain-experts/]], Nielson Norman Group, 2017
	191	+
	192	+[['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
	193	+
	194	+[['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
	195	+
	196	+[['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
	197	+
	198	+[['Advantages and disadvantages with Simplified Technical English'>>url:https://liu.diva-portal.org/smash/get/diva2:16816/FULLTEXT01]], Msc thesis paper, Karin Disborg, 2007
	199	+
	200	+[['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
	201	+
	202	+[['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
	203	+
	204	+(% class="wikigeneratedid" %)
	205	+We generated the [[before sentence about an architecture term>>url:http://sentence.yourdictionary.com/palladian]] from yourdictionary.com and applied our recommendations.
	206	+
	207	+
	208	+(% class="wikigeneratedid" %)
157	157	Here's some sector specific guidance:
158	158
159	159	(% class="wikigeneratedid" %)