Changes for page Simple sentences
Last modified by Lizzie Bruce on 2020/01/11 23:51
From version 
2.32 
2.32
edited by Lizzie Bruce
on 2019/03/08 20:53
on 2019/03/08 20:53
Change comment:
Updated the relative links.
To version 2.35
2.35
edited by Lizzie Bruce
on 2019/03/08 23:05
on 2019/03/08 23:05
Change comment:
There is no comment for this version
Summary
Details
-
Page properties
-
- Content
-
... ... @@ -1,117 +1,52 @@ 1 1 (% class="box" %) 2 2 ((( 3 -Writing about people 4 -))) 3 +Following this helps: 5 5 6 -(% class="box" %) 7 -((( 8 -Audience labels: using I, you, we, they 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** – it's less tiring when you can absorb what you read quickly 9 9 ))) 10 10 11 -(% class="box" %) 12 -((( 13 -== [[Plain English, specialist terms >>doc:Plain English.Plain English, simple sentences.WebHome]] == 14 -))) 13 +== 14 +Guidelines == 15 15 16 -(% class="box" %) 17 -((( 18 -Simple sentences 19 -))) 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." The United Nations recommends plain language for communications. 20 20 21 -(% class="box" %) 22 -((( 23 -Law, medicine and money 24 -))) 25 25 26 -(% class="box" %) 27 -((( 28 -Words to avoid 29 -))) 19 +(% class="wikigeneratedid" id="H1.MakeyouraveragesentenceA015wordslong." %) 20 +[[1. Make your average sentence 15 words long.>>doc:||anchor="#1"]] 30 30 31 -[[Simple sentences>>||anchor="ssl"]] 22 +(% class="wikigeneratedid" id="H2.A0Avoidcomplexsentencestructures." %) 23 +[[2. Avoid complex sentence structures.>>doc:||anchor="#2"]] 32 32 33 -[[Specialist terms>>||anchor="st"]] 34 - 35 -[[Law, medicine, money>>doc:Plain English.Medical.WebHome]] 36 - 37 37 (% class="wikigeneratedid" %) 38 -[[Words to avoid>>doc:Plain English.Words to avoid.WebHome]] 26 +[[Usability evidence>>doc:||anchor="#UESS"]] 27 + 39 39 40 - 41 41 ---- 42 42 43 -== == 31 +== == 44 44 45 -== {{id name=" pe"/}}PlainEnglish==33 +=== {{id name="#1"/}}1. Make your average sentence 15 words long. === 46 46 47 - Makecontentclear andunderstandable, to open thewebup foruserswith differentliteracy levelsandaccesschallenges.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. 48 48 49 - WCAGstatesthat"usingthe clearestandsimplest language appropriate ishighly desirable."37 +Oxford Guide to plain English, GOV.UK and linguists agree: 50 50 51 -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 52 52 53 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 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 69 46 +(% class="mark" %)This sentence is about 15 words long and is easy to understand. 70 70 71 -=== 3. Write conversationally. ===48 +=== {{id name="#2"/}}2. Avoid complex sentence structures. === 72 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 - 106 -=== 1. Make your average sentence 15 words long. === 107 - 108 -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. 109 - 110 -Oxford Guide to plain English, GOV.UK and linguists agree 15 word sentences are fine but above 40 words is hard to understand. 111 - 112 - 113 -=== 2. Avoid complex sentence structures. === 114 - 115 115 They are less easy to comprehend quickly. Understanding them requires more cognitive effort than simple sentences. 116 116 117 117 ... ... @@ -121,12 +121,15 @@ 121 121 * distribution of associated words across the sentence – how easily can the brain 'parse a phrase': recognise, connect and comprehend words that together convey meaning 122 122 123 123 124 ->Example:"The red fox jumped over the gate." – easier to understand 125 ->"The fox, which was red, over the gate jumped." – harder to understand 59 +Example: 60 +\\(% class="mark" %)"The red fox jumped over the gate." – easier to understand 61 +"The fox, which was red, over the gate jumped." – harder to understand 126 126 127 127 128 - == Usability evidence: simple sentences ==64 +---- 129 129 66 +== {{id name="#UESS"/}}Usability evidence: simple sentences == 67 + 130 130 Oxford Guide to plain English 131 131 132 132 Jyoti Sanyal 'Indlish' ... ... @@ -176,64 +176,12 @@ 176 176 177 177 ---- 178 178 179 -== == 117 +(% class="box" %) 118 +((( 119 +See also: 180 180 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]]! 121 +* [[Plain English>>doc:Plain English.Plain English, simple sentences.WebHome]] 122 +* [[Specialist terms>>doc:Plain English.Specialist terms.WebHome]] 123 +* [[Law, medicine, money>>doc:Plain English.Medical.WebHome]] 124 +* [[Words to avoid>>doc:Plain English.Words to avoid.WebHome]] 125 +)))