Changes for page Simple sentences

Summary

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

Details

Page properties

Content

...	...	@@ -1,25 +1,108 @@
1	1	(% class="box" %)
2	2	(((
3		-Following this helps:
	3	+Writing about people
	4	+)))
4	4
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 holding a baby or a running business your attention's divided
8		-* **cognitive impairments** – easy to understand words and sentences carry less cognitive load
9		-* **visual impairments** – short and simple sentences convey meaning in a smaller visual field
10		-* **motor impairments** – it's less tiring when you can understand what you read quickly
	6	+(% class="box" %)
	7	+(((
	8	+Audience labels: using I, you, we, they
11	11	)))
12	12
13		-==
14		-Guidelines ==
	11	+(% class="box" %)
	12	+(((
	13	+== [[Plain English, specialist terms >>doc:Plain English.Plain English, simple sentences.WebHome]] ==
	14	+)))
15	15
16		-* [[Simple sentences>>url:https://readabilityguidelines.myxwiki.org/xwiki/bin/view/Plain%20English/Plain%20English%2C%20simple%20sentences/#ssl]]
	16	+(% class="box" %)
	17	+(((
	18	+Simple sentences
	19	+)))
17	17
	21	+(% class="box" %)
	22	+(((
	23	+Law, medicine and money
	24	+)))
	25	+
	26	+(% class="box" %)
	27	+(((
	28	+Words to avoid
	29	+)))
	30	+
	31	+[[Simple sentences>>||anchor="ssl"]]
	32	+
	33	+[[Specialist terms>>||anchor="st"]]
	34	+
	35	+[[Law, medicine, money>>doc:Plain English.Medical.WebHome]]
	36	+
	37	+(% class="wikigeneratedid" %)
	38	+[[Words to avoid>>doc:Plain English.Words to avoid.WebHome]]
	39	+
	40	+
18	18	----
19	19
20		-==
21		-Simple sentences ==
	43	+== ==
22	22
	45	+== {{id name="pe"/}}Plain English ==
	46	+
	47	+Make content clear and understandable, to open the web up for users with different literacy levels and access challenges.
	48	+
	49	+WCAG states that "using the clearest and simplest language appropriate is highly desirable."
	50	+
	51	+The United Nations recommends plain language for communications.
	52	+
	53	+
	54	+=== 1. Choose easy and short words not formal, long ones. ===
	55	+
	56	+Use ‘buy’ instead of ‘purchase’, ‘help’ instead of ‘assist’, and ‘about’ instead of ‘approximately’.
	57	+
	58	+Write for the reading comprehension of a 9 year old. This helps you reach the most users and makes your content easy to scan.
	59	+
	60	+
	61	+=== 2. Jargon and buzzwords are unlikely to be clear language. ===
	62	+
	63	+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.
	64	+
	65	+
	66	+Example:
	67	+"Let's touch base in 10 and do some blue sky thinking." This uses jargon.
	68	+"Let's meet in 10 minutes to think of some ideas." Conveys same meaning using clear language.
	69	+
	70	+
	71	+=== 3. Write conversationally. ===
	72	+
	73	+Picture your audience and write as if you were talking directly to them, with the authority of someone who can help and inform.
	74	+
	75	+
	76	+=== 4. Test your content with users ===
	77	+
	78	+What is 'plain' for one person may not be for someone else.
	79	+
	80	+
	81	+== Usability evidence: plain English ==
	82	+
	83	+[[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.
	84	+
	85	+[['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.
	86	+
	87	+[['Plain Language Is for Everyone, Even Experts'>>url:https://www.nngroup.com/articles/plain-language-experts/]], H. Loranger, Nielsen Norman Group, 2017
	88	+
	89	+[['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
	90	+
	91	+[['Strengthening plain language'>>url:http://www.iplfederation.org/]], International Plain Language Federation. Undated.
	92	+
	93	+[[Plain Language Commission style guide>>url:https://www.clearest.co.uk/plain-language-commission-style-guide]], Plain Language Commission, 2011
	94	+
	95	+[['The principles of readability'>>url:http://www.impact-information.com/impactinfo/readability02.pdf]], Impact Information, William H. DuBay, 2004
	96	+
	97	+[[Plain language entry>>url:https://en.m.wikipedia.org/wiki/Plain_language]], Wikipedia, last updated 2018
	98	+
	99	+
	100	+----
	101	+
	102	+== ==
	103	+
	104	+== {{id name="ssl"/}}Simple sentences ==
	105	+
23	23	=== 1. Make your average sentence 15 words long. ===
24	24
25	25	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.
...	...	@@ -93,9 +93,64 @@
93	93
94	94	----
95	95
96		-See also:
	179	+== ==
97	97
98		-* Plain English
99		-* [[Specialist terms>>url:https://readabilityguidelines.myxwiki.org/xwiki/bin/view/Plain%20English/Plain%20English%2C%20simple%20sentences/#st]]
100		-* [[Law, medicine, money>>url:https://readabilityguidelines.myxwiki.org/xwiki/bin/view/Plain%20English/Medical/]]
101		-* [[Words to avoid>>url:https://readabilityguidelines.myxwiki.org/xwiki/bin/view/Plain%20English/Words%20to%20avoid/]]
	181	+== {{id name="st"/}}Specialist terms ==
	182	+
	183	+(% class="wikigeneratedid" %)
	184	+Make specialist content comprehensible by non-experts.
	185	+
	186	+
	187	+=== 1. Explain specialist terms: anybody can access your content. ===
	188	+
	189	+Assuming who your audience is, and that they'll understand the technical terms you use, are common misconceptions.
	190	+
	191	+
	192	+=== 2. Create content that all users can understand, whatever their expertise or background. ===
	193	+
	194	+When you present a concept explain its parts and processes in detail.
	195	+
	196	+If you need to include a technical term consider explaining it. Make sure the surrounding language in plain language.
	197	+
	198	+
	199	+=== 3. Help users understand specialist terms. ===
	200	+
	201	+You could:
	202	+
	203	+* link to an existing definition – this could be an external site
	204	+* add a explanatory definition after using the term
	205	+
	206	+
	207	+>Example:
	208	+>
	209	+>"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]]).
	210	+>
	211	+>"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.
	212	+>
	213	+> "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.
	214	+
	215	+
	216	+== Usability evidence: specialist terms ==
	217	+
	218	+[['Writing Digital Copy for Domain Experts'>>url:https://www.nngroup.com/articles/writing-domain-experts/]], Nielson Norman Group, 2017
	219	+
	220	+[['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
	221	+
	222	+[['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
	223	+
	224	+[['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
	225	+
	226	+[['Advantages and disadvantages with Simplified Technical English'>>url:https://liu.diva-portal.org/smash/get/diva2:16816/FULLTEXT01]], Msc thesis paper, Karin Disborg, 2007
	227	+
	228	+[['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
	229	+
	230	+[['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
	231	+
	232	+
	233	+----
	234	+
	235	+(% class="wikigeneratedid" %)
	236	+Here's some sector specific guidance for [[medicine, money and law>>doc:Plain English.Medical.WebHome]].
	237	+
	238	+
	239	+And here's our list of jargon [[words to avoid>>doc:Plain English.Words to avoid.WebHome]]!