Changes for page Simple sentences

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-Clear language
	1	+Simple sentences

Parent

...	...	@@ -1,1 +1,1 @@
1		-Main.WebHome
	1	+Plain English.WebHome

Content

...	...	@@ -1,104 +1,53 @@
1		-(% class="wikigeneratedid" %)
2		-This helps:
	1	+(% class="box" %)
	2	+(((
	3	+Following this helps:
3	3
4		-* **people in a hurry** – simply written content is easier to scan and absorb instantly
5		-* **people who are stressed** – if you're anxious you find it harder to comprehend things
6		-* **people who are multi-tasking** – if you're holding a baby or a running business your attention's divided
7		-* **cognitive impairments** – easy to understand words and sentences carry less cognitive load
8		-* **visual impairments** – short and simple sentences convey meaning in a smaller visual field
9		-* **motor impairments** – it's less tiring when you can understand what you read quickly
10		-
	5	+* **people in a hurry** – simply written content is easier to scan and absorb instantly
	6	+* **people who are stressed** – if you're anxious you find it harder to comprehend things
	7	+* **people who are multi-tasking** – if you're distracted it's hard to comprehend convoluted structures
	8	+* **cognitive impairments** – shorter, non-complex sentences carry less cognitive load
	9	+* **visual impairments** – short, simple sentences convey meaning in a smaller visual field
	10	+* **motor impairments** – clear, concise content is shorted so requires less navigation
	11	+)))
11	11
12		-== ==
	13	+==
	14	+Guidelines ==
13	13
14		-== Guidelines ==
	16	+Short, simple sentences are better on the web than long, protracted prose with complex syntax. WCAG says: "using the clearest and simplest language appropriate is highly desirable."
15	15
16		-[[Plain English>>Plain English||anchor="pe"]]
17	17
18		-[[Simple sentences>>||anchor="ssl"]]
	19	+(% class="wikigeneratedid" id="H1.MakeyouraveragesentenceA015wordslong." %)
	20	+[[1. Make your average sentence 15 words long.>>doc:||anchor="#1"]]
19	19
20		-[[Specialist terms>>||anchor="st"]]
	22	+(% class="wikigeneratedid" id="H2.A0Avoidcomplexsentencestructures." %)
	23	+[[2. Avoid complex sentence structures.>>doc:||anchor="#2"]]
21	21
22		-[[Law, medicine, money>>doc:.Medical.WebHome]]
23		-
24	24	(% class="wikigeneratedid" %)
25		-[[Words to avoid>>doc:.Words to avoid.WebHome]]
	26	+[[Usability evidence>>doc:||anchor="#UESS"]]
	27	+
26	26
27		-
28	28	----
29	29
30		-== ==
	31	+== ==
31	31
32		-== {{id name="pe"/}}Plain English ==
	33	+=== {{id name="#1"/}}1. Make your average sentence 15 words long. ===
33	33
34		-Make content clear and understandable, to open the web up for users with different literacy levels and access challenges.
	35	+The maximum sentence length for a good level of comprehension is 25 words. Split long sentences up into 2 or 3, or use bullet points.
35	35
36		-WCAG states that "using the clearest and simplest language appropriate is highly desirable."
	37	+Oxford Guide to plain English, GOV.UK and linguists agree:
37	37
38		-The United Nations recommends plain language for communications.
	39	+* 15 word sentences are more likely to be comprehensible
	40	+* 25 words is a good maximum sentence length limit
	41	+* above 40 words sentences are hard to comprehend easily
39	39
40	40
41		-=== 1. Choose easy and short words not formal, long ones. ===
	44	+Example:
42	42
43		-Use ‘buy’ instead of ‘purchase’, ‘help’ instead of ‘assist’, and ‘about’ instead of ‘approximately’.
44		-
45		-Write for the reading comprehension of a 9 year old. This helps you reach the most users and makes your content easy to scan.
	46	+(% class="mark" %)This sentence is about 15 words long and is easy to understand. (%%)
46	46
47	47
48		-=== 2. Jargon and buzzwords are unlikely to be clear language. ===
	49	+=== {{id name="#2"/}}2. Avoid complex sentence structures. ===
49	49
50		-Often, these words are too general and vague and can lead to misinterpretation or empty, meaningless text. Avoid them. Instead, think about what the term actually means and describe that. Be open and specific.
51		-
52		-
53		-Example:
54		-"Let's touch base in 10 and do some blue sky thinking." This uses jargon.
55		-"Let's meet in 10 minutes to think of some ideas." Conveys same meaning using clear language.
56		-
57		-
58		-=== 3. Write conversationally. ===
59		-
60		-Picture your audience and write as if you were talking directly to them, with the authority of someone who can help and inform.
61		-
62		-
63		-=== 4. Test your content with users ===
64		-
65		-What is 'plain' for one person may not be for someone else.
66		-
67		-
68		-== Usability evidence: plain English ==
69		-
70		-[[Guideline 3.1 Readable: Make text content readable and understandable.>>url:https://www.w3.org/TR/UNDERSTANDING-WCAG20/meaning-supplements.html]], Web Content Accessibility Guidelines (WCAG) 2.0, 2008.
71		-
72		-[['Convention on the Rights of Persons with Disabilities'>>url:http://templatelab.com/convention-on-the-rights-of-persons-with-disabilities/]], page 4 Article 2, Definitions, The United Nations Convention on the Rights of Persons with Disabilities, 2018.
73		-
74		-[['Plain Language Is for Everyone, Even Experts'>>url:https://www.nngroup.com/articles/plain-language-experts/]], H. Loranger, Nielsen Norman Group, 2017
75		-
76		-[['The Public Speaks: An Empirical Study of Legal Communication'>>url:https://papers.ssrn.com/sol3/papers.cfm?abstract_id=1843415]], C. R. Trudeau in 14 Scribes J. Leg. Writing 121 2012
77		-
78		-[['Strengthening plain language'>>url:http://www.iplfederation.org/]], International Plain Language Federation. Undated.
79		-
80		-[[Plain Language Commission style guide>>url:https://www.clearest.co.uk/plain-language-commission-style-guide]], Plain Language Commission, 2011
81		-
82		-[['The principles of readability'>>url:http://www.impact-information.com/impactinfo/readability02.pdf]], Impact Information, William H. DuBay, 2004
83		-
84		-[[Plain language entry>>url:https://en.m.wikipedia.org/wiki/Plain_language]], Wikipedia, last updated 2018
85		-
86		-
87		-----
88		-
89		-== ==
90		-
91		-== {{id name="ssl"/}}Simple sentences ==
92		-
93		-=== 1. Make your average sentence 15 words long. ===
94		-
95		-The maximum sentence length for a good level of comprehension is 25 words. Split long sentences up into 2 or 3, or use bullet points.
96		-
97		-Oxford Guide to plain English, GOV.UK and linguists agree 15 word sentences are fine but above 40 words is hard to understand.
98		-
99		-
100		-=== 2. Avoid complex sentence structures. ===
101		-
102	102	They are less easy to comprehend quickly. Understanding them requires more cognitive effort than simple sentences.
103	103
104	104
...	...	@@ -108,18 +108,17 @@
108	108	* distribution of associated words across the sentence – how easily can the brain 'parse a phrase': recognise, connect and comprehend words that together convey meaning
109	109
110	110
111		->Example:"The red fox jumped over the gate." – easier to understand
112		->"The fox, which was red, over the gate jumped." – harder to understand
	60	+Example:
	61	+\\(% class="mark" %)"The red fox jumped over the gate." – easier to understand
	62	+"The fox, which was red, over the gate jumped." – harder to understand
113	113
114	114
115		-== Usability evidence: simple sentences ==
	65	+----
116	116
117		-Oxford Guide to plain English
	67	+== {{id name="#UESS"/}}Usability evidence: simple sentences ==
118	118
119		-Jyoti Sanyal 'Indlish'
	69	+[[Oxford Guide to plain English>>https://global.oup.com/academic/product/oxford-guide-to-plain-english-9780199669172?cc=gb&lang=en&]] , Oxford University Press, 2013
120	120
121		-Author Ann Wylie
122		-
123	123	[[Writing for GOV.UK>>url:https://www.gov.uk/guidance/content-design/writing-for-gov-uk]], UK Government website
124	124
125	125	[['Sentence length: why 25 words is our limit'>>url:https://insidegovuk.blog.gov.uk/2014/08/04/sentence-length-why-25-words-is-our-limit/]], Inside GOV.UK, UK Government blog, 2014
...	...	@@ -126,8 +126,12 @@
126	126
127	127	[['Content design'>>url:https://contentdesign.london/book/]], Sarah Richards, 2017
128	128
129		-[['The role of word difficulty and sentence length in text comprehension'>>url:https://apps.dtic.mil/dtic/tr/fulltext/u2/a114935.pdf]], T. M. Duffy and P. K. U'Ren, 1982
	77	+[['Short sentences boost readability. Nearly 140 years of research proves it'>>https://www.wyliecomm.com/2018/08/short-sentences-boost-readability/]] A. Wylie, a collection of studies since 1880s, 2018
130	130
	79	+[['Indlish: The book for every English-speaking Indian'>>http://www.vivagroupindia.com/frmBookDetail.aspx?BookId=5020&Status=C]], J. Sanyal, 2006. Book.
	80	+
	81	+[['The role of word difficulty and sentence length in text comprehension'>>https://eric.ed.gov/?id=ED215330]], T. M. Duffy and P. K. U'Ren, 1982
	82	+
131	131	[['The Influence of Semantics and Syntax on What Readers Remember'>>url:https://www.hcde.washington.edu/files/people/docs/Isakson_Spyridakis_Sem_Syn.pdf]], C. S. Isakson and J. H. Spyridakis, 1999
132	132
133	133	[['How the brain attunes to sentence processing: Relating behavior, structure, and function'>>url:https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4819595/]], A. Fengler, L. Meyer, A. D. Friederici, National Center for Biotechnology Information
...	...	@@ -138,7 +138,7 @@
138	138
139	139	[['Readability Assessment of Internet-Based Consumer Health Information'>>url:http://rc.rcjournal.com/content/53/10/1310/tab-pdf]], T. M. Walsh and T. A. Volsko in Respiratory Care October 2008, 53 (10) 1310-1315
140	140
141		-[['The research basis of plain language techniques: Implications for establishing standards'>>url:https://www.researchgate.net/profile/Karen_Schriver/publication/285927928_The_research_basis_of_plain_language_techniques_Implications_for_establishing_standards/links/5664c50208ae192bbf90aa85/The-research-basis-of-plain-language-techniques-Implications-for-establishing-standards.pdf]], Karen Schriver, PhD, Dr. A. L. Cheek, M. Mercer, Center for Plain Language, November 20, 2008, Mexico City
	93	+[['The research basis of plain language techniques: Implications for establishing standards'>>url:https://www.researchgate.net/profile/Karen_Schriver/publication/285927928_The_research_basis_of_plain_language_techniques_Implications_for_establishing_standards/links/5664c50208ae192bbf90aa85/The-research-basis-of-plain-language-techniques-Implications-for-establishing-standards.pdf]], K. Schriver, PhD, Dr. A. L. Cheek, M. Mercer, Center for Plain Language, November 20, 2008, Mexico City
142	142
143	143	[['Readability Levels of Health-Based Websites: From Content to Comprehension'>>url:https://files.eric.ed.gov/fulltext/EJ851863.pdf]], M. Schutten, A. McFarland, PhD, International Electronic Journal of Health Education, 2009, 12:99-107
144	144
...	...	@@ -146,81 +146,29 @@
146	146
147	147	[[Plain Language Commission style guide>>url:https://irp-cdn.multiscreensite.com/aaf9e928/files/uploaded/PLCstyleguide25July2012.pdf]], 2012
148	148
149		-[['Shorter Lines Facilitate Reading in Those Who Struggle'>>url:https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0071161]], Matthew H. Schneps , Jenny M. Thomson, Gerhard Sonnert, Marc Pomplun, Chen Chen, Amanda Heffner-Wong, 2013
	101	+[['Shorter Lines Facilitate Reading in Those Who Struggle'>>url:https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0071161]], M. H. Schneps , J. M. Thomson, G. Sonnert, M. Pomplun, C. Chen, A. Heffner-Wong, 2013
150	150
151		-[['Towards a better measure of readability: Explanation of empirical performance results'>>url:https://www.tandfonline.com/doi/pdf/10.1080/00437956.1989.11435805]], Leslie A. Olsen & Rod Johnson, Taylor & Francis Group, 2015
	103	+[['Towards a better measure of readability: Explanation of empirical performance results'>>url:https://www.tandfonline.com/doi/pdf/10.1080/00437956.1989.11435805]], L. A. Olsen, R. Johnson, Taylor and Francis Group, 2015
152	152
153	153	[['What is plain language?'>>url:https://plainlanguagenetwork.org/plain-language/what-is-plain-language/]], Plain Language Association International, 2015
154	154
155	155	[[Text complexity, ATOS, and Lexile® Measures>>url:https://www.renaissance.com/products/practice/accelerated-reader-360/atos-and-text-complexity/]], Renaissance Learning, 2016
156	156
157		-[['Understanding Plain English summaries. A comparison of two approaches to improve the quality of Plain English summaries in research reports.'>>url:https://researchinvolvement.biomedcentral.com/articles/10.1186/s40900-017-0064-0]] 2017
	109	+[['Understanding Plain English summaries. A comparison of two approaches to improve the quality of Plain English summaries in research reports.'>>url:https://researchinvolvement.biomedcentral.com/articles/10.1186/s40900-017-0064-0]] E. Kirkpatrick, W. Gaisford, E. Williams, E. Brindley, D. Tembo, D. Wright, 2017
158	158
159		-[['How to use Yoast SEO: The readability analysis?'>>url:https://yoast.com/yoast-seo-readability-analysis/]] Edwin Toonen, Yoast, 2018
	111	+[['How to use Yoast SEO: The readability analysis?'>>url:https://yoast.com/yoast-seo-readability-analysis/]] E. Toonen, Yoast, 2018
160	160
161		-[[The Crystal Mark standard>>url:http://www.plainenglish.co.uk/services/crystal-mark/7-the-crystal-mark-standard.html]] Plain English Campaign, undated
	113	+[[The Crystal Mark standard>>url:http://www.plainenglish.co.uk/services/crystal-mark/7-the-crystal-mark-standard.html]] Plain English Campaign. Undated.
162	162
163	163
164	164	----
165	165
166		-== ==
	118	+(% class="box" %)
	119	+(((
	120	+See also:
167	167
168		-== {{id name="st"/}}Specialist terms ==
169		-
170		-(% class="wikigeneratedid" %)
171		-Make specialist content comprehensible by non-experts.
172		-
173		-
174		-=== 1. Explain specialist terms: anybody can access your content. ===
175		-
176		-Assuming who your audience is, and that they'll understand the technical terms you use, are common misconceptions.
177		-
178		-
179		-=== 2. Create content that all users can understand, whatever their expertise or background. ===
180		-
181		-When you present a concept explain its parts and processes in detail.
182		-
183		-If you need to include a technical term consider explaining it. Make sure the surrounding language in plain language.
184		-
185		-
186		-=== 3. Help users understand specialist terms. ===
187		-
188		-You could:
189		-
190		-* link to an existing definition – this could be an external site
191		-* add a explanatory definition after using the term
192		-
193		-
194		->Example:
195		->
196		->"It is a Palladian style stone building, and contains a number of splendid paintings and much fine wood-carving." – original sentence (source [[yourdictionary.com>>url:http://sentence.yourdictionary.com/palladian]]).
197		->
198		->"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.
199		->
200		-> "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.
201		-
202		-
203		-== Usability evidence: specialist terms ==
204		-
205		-[['Writing Digital Copy for Domain Experts'>>url:https://www.nngroup.com/articles/writing-domain-experts/]], Nielson Norman Group, 2017
206		-
207		-[['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
208		-
209		-[['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
210		-
211		-[['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
212		-
213		-[['Advantages and disadvantages with Simplified Technical English'>>url:https://liu.diva-portal.org/smash/get/diva2:16816/FULLTEXT01]], Msc thesis paper, Karin Disborg, 2007
214		-
215		-[['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
216		-
217		-[['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
218		-
219		-
220		-----
221		-
222		-(% class="wikigeneratedid" %)
223		-Here's some sector specific guidance for [[medicine, money and law>>doc:.Medical.WebHome]].
224		-
225		-
226		-And here's our list of jargon [[words to avoid>>doc:.Words to avoid.WebHome]]!
	122	+* [[Plain English>>doc:Plain English.Plain English, simple sentences.WebHome]]
	123	+* [[Specialist terms>>doc:Plain English.Specialist terms.WebHome]]
	124	+* [[Law, medicine, money>>doc:Plain English.Medical.WebHome]]
	125	+* [[Words to avoid>>doc:Plain English.Words to avoid.WebHome]]
	126	+)))