Skip to Content
Last modified by Lizzie Bruce on 2020/01/11 23:49
From version Icon 3.1 Icon
edited by Lizzie Bruce
on 2019/04/24 15:03
Change comment: Added more evidence, added subheadings for Health, Legal, Finance specific studies/articles
To version Icon 1.45 Icon
edited by Lizzie Bruce
on 2019/03/09 03:21
Change comment: There is no comment for this version

Summary

Details

Icon Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Legal, medical and financial terms
1 +Law, medicine and money
Content
... ... @@ -4,12 +4,11 @@
4 4  
5 5  
6 6  * **people in a hurry** – simply written content is quicker to scan
7 -* **people who are stressed** – if you're anxious it's difficult to understand complex text
8 -* **people who are multi-tasking** – when distracted complex text is harder to comprehend
9 -* **people with low literacy** – will not know meanings of complex vocabulary and terms
10 -* **cognitive impairments** – easy to understand words involve less cognitive load
7 +* **people who are stressed** – if you're anxious it's harder to comprehend things
8 +* **people who are multi-tasking** – when distracted you cannot concentrate on complex text
9 +* **cognitive impairments** – easy to understand words carry less cognitive load
11 11  * **visual impairments** – short, simple sentences convey meaning in a smaller visual field
12 -* **motor impairments** – it takes less physical effort to navigate shorter content
11 +* **motor impairments** – it's less tiring when you can understand what you read quickly
13 13  )))
14 14  
15 15  
... ... @@ -16,19 +16,14 @@
16 16  == Guidance ==
17 17  
18 18  (% class="wikigeneratedid" %)
19 -The legal, financial and medical professions are known for complex terminology. This is not necessary and confuses people. 
18 +The [[legal>>doc:||anchor="l"]], [[medical>>doc:||anchor="m"]] and [[financial>>doc:||anchor="mo"]] professions are known for using complex terminology. But it's not necessary and confuses people who use their services. 
20 20  
21 21  
22 -(% class="wikigeneratedid" %)
23 -**Health:** People need to understand doctors' letters and consultant reports easily. They need to be able to comprehend online information about health. 
21 +=== Law ===
24 24  
25 -(% class="wikigeneratedid" %)
26 -**Finances: **Many people do not understand financial terms. This causes problems. Complex terminology describing conceptual arrangements is not helpful.
23 +Judges need to decide what legal writers intended by their writing. They evolved a set of tools for this analysis: Statutory Interpretation. Using plain English can make meaning clear, so that judges avoid relying on sometimes contradictory interpretations.
24 +
27 27  
28 -(% class="wikigeneratedid" %)
29 -**Law: **Judges created a set of tools to decide what legal writers intended: Statutory Interpretation. But analyses can contradict each other. Plain English makes meaning clearer from the start.
30 -
31 -
32 32  (% class="wikigeneratedid" id="H1.Usesimplelanguageforlegalterms." %)
33 33  [[1. Use simple language for legal terms.>>doc:||anchor="#l1"]]
34 34  
... ... @@ -35,26 +35,44 @@
35 35  (% class="wikigeneratedid" id="H2.Explainthelawincontext." %)
36 36  [[2. Explain the law in context.>>doc:||anchor="#l2"]]
37 37  
32 +[[Usability evidence: plain English in law>>doc:||anchor="#UEL"]]
33 +
34 +
35 +=== Medicine ===
36 +
37 +People need doctors' letters and consultant reports to be easy to understand. And they need online information about health conditions to be comprehensible.  
38 +
39 +
38 38  (% class="wikigeneratedid" id="H1.Writeclearly." %)
39 -[[3. Write medical information clearly.>>doc:||anchor="#m1"]]
41 +[[1. Write clearly.>>doc:||anchor="#m1"]]
40 40  
41 41  (% class="wikigeneratedid" id="H2.Explainmedicalterms." %)
42 -[[4. Explain medical terms.>>doc:||anchor="#m2"]]
44 +[[2. Explain medical terms.>>doc:||anchor="#m2"]]
43 43  
46 +[[Usability evidence: plain English in medicine>>doc:||anchor="#UM"]]
47 +
48 +
49 +=== Money ===
50 +
51 +Many people do not understand financial terms. This causes problems. Complex terminology describing conceptual arrangements about a non-tangible resource does not help anyone. 
52 +
53 +
44 44  (% class="wikigeneratedid" id="H1.Useclearlanguage." %)
45 -[[5. Use clear language for financial information.>>doc:||anchor="#mo1"]]
55 +[[1. Use clear language.>>doc:||anchor="#mo1"]]
46 46  
47 47  (% class="wikigeneratedid" id="H2.Explainterminology." %)
48 -[[6. Explain financial terminology.>>doc:||anchor="#mo2"]]
58 +[[2. Explain terminology.>>doc:||anchor="#mo2"]]
49 49  
50 50  (% class="wikigeneratedid" id="H3.Giveexamplesofconceptualarrangements." %)
51 -[[7. Give examples of conceptual financial arrangements.>>doc:||anchor="#mo3"]]
61 +[[3. Give examples of conceptual arrangements.>>doc:||anchor="#mo3"]]
52 52  
53 -[[Usability evidence>>doc:||anchor="#UEL"]]
54 -
63 +[[Usability evidence: plain English in finance>>doc:||anchor="#UEMO"]]
55 55  
65 +
56 56  ----
57 57  
68 +== {{id name="l"/}}Law – plain English guidelines ==
69 +
58 58  === {{id name="#l1"/}}1. Use simple language for legal terms. ===
59 59  
60 60  If information on your website is unclear your organisation could be taken to court and lose, even if content is approved by your legal department.
... ... @@ -66,7 +66,7 @@
66 66  
67 67  
68 68  Example:
69 -\\(% class="mark" %)Positioned at the top of a form, not hidden away in references section:
81 +\\(% class="mark" %)Positioned at the top of a form, not hidden away in references section.
70 70  
71 71  (((
72 72  "We collect personal information on this form under section 26 the Freedom of Information and Protection of Privacy Act, because it concerns our programs and activities (c), and it is necessary for planning and evaluating our programs and activities(e)."
... ... @@ -82,48 +82,35 @@
82 82  (% class="mark" %)5 (1) This section describes direct sellers that are, and circumstances in which direct sellers are, exempt from the application of sections 19 to 22 (required contents, direct sales contracts, direct sales contract — cancellation, credit agreement respecting direct sales contract) of the Act."
83 83  
84 84  
85 -=== {{id name="#m1"/}}3. Write medical information clearly. ===
97 +=== {{id name="#UEL"/}}Usability evidence: plain English in law ===
86 86  
87 -Users of the information might be in shock or anxious, which reduces cognition.
99 +[['Joseph Kimble—No, the law does not (normally) require legalese'>>url:http://www.ivacheung.com/2015/07/joseph-kimble-no-the-law-does-not-normally-require-legalese-editing-goes-global-2015/]] Editing Goes Global, 2015. Professor Joseph Kimble discusses the "psuedo-precision of legalese".
88 88  
101 +[[Plain language: the underlying research>>url:https://www.victorialawfoundation.org.au/sites/default/files/resources/Schriver_Karen%20Clarity2012.pdf]], Karen Schriver slide presentation, pages 29 to 35.
89 89  
90 -=== {{id name="#m2"/}} 4. Explain medical terms. ===
103 +[[The public speaks: an empirical study of legal communication>>url:http://works.bepress.com/cgi/viewcontent.cgi?article=1000&context=christopher_trudeau]], study by Christopher Trudeau (@proftrudeau on Twitter) containing case studies from solicitors about using legal language.
91 91  
92 -Medical terms are unlikely to be understood by your readers. It's similar to assuming they would know a word in a foreign language. Follow the word or phrase with a plain English explanation.
105 +[[Richmond vs HRA>>url:http://www.alltrials.net/news/judgment-in-richmond-v-hra-judicial-review/]] A pharmaceutical company called Richmond took the Health Regulatory Authority to court because the website was confusing. A high court judge deemed the site 'unlawful' and ruled against the government. The site was cleared through a legal department. This set a precedent in the UK. You could still be sued even with all the legal language is there, if the information is not clear.
93 93  
107 +[[Plain English Campaign>>url:http://www.plainenglish.co.uk/campaigning/past-campaigns/legal/drafting-in-plain-english.html]] believes legalese is unnecessary and does not do what it was intended to. "The argument that clarity should be sacrificed for a document to be comprehensive does not stand up."
94 94  
95 -=== {{id name="#mo1"/}}5. Use clear language for financial information. ===
96 96  
97 -Dealing with financial issues can be stressful, which means your audience will have less cognitive capability available. Write information so that it is easy for them to understand.
98 -
110 +----
99 99  
100 -=== {{id name="#mo2"/}}6. Explain financial terminology. ===
112 +== {{id name="m"/}}Medicine – plain English guidelines ==
101 101  
102 -Avoid using financial jargon. Acronyms and pseudonyms may make sense internally, but people using your services may not understand them.
114 +=== {{id name="#m1"/}}1. Write clearly. ===
103 103  
116 +Users of the information might be in shock or anxious, which reduces cognition.
104 104  
105 -=== {{id name="#mo3"/}}7. Give examples of conceptual financial arrangements. ===
106 106  
107 -A tracker or shared ownership mortgage is easier to understand if you give examples.
119 +=== {{id name="#m2"/}} 2. Explain medical terms. ===
108 108  
109 -This is important for credit arrangements where there is an initial interest rate that may change.
121 +Medical terms are likely not to be understood by your readers. It is likely assuming they would know a word in a foreign language. Follow the word or phrase with a plain English explanation.
110 110  
111 111  
112 -----
124 +=== {{id name="#UM"/}}Usability evidence: plain English in medicine ===
113 113  
114 -== {{id name="#UEL"/}}Usability evidence ==
115 -
116 -
117 -[['Writing content for everyone'>>path:/xwiki/bin/get/Plain%20English/Plain%20English%2C%20simple%20sentences/?sheet=CKEditor.ResourceDispatcher&outputSyntax=plain&language=en&type=doc&reference=https%3A%2F%2Fgds.blog.gov.uk%2F2016%2F02%2F23%2Fwriting-content-for-everyone%2F]], R. Strachan, UK Government Digital Service blog, 2016
118 -
119 -=== Health specific ===
120 -
121 -(% class="wikigeneratedid" id="H" %)
122 -[['Department of Health Stakeholder Report: 2012'>>https://www.gov.uk/government/publications/department-of-health-stakeholder-report-2012]], research by Ipsos MORI, 2012
123 -
124 -(% class="wikigeneratedid" %)
125 -[['Connecting with audiences. An evidence-based language sourcebook'>>http://www.linguisticlandscapes.co.uk/pdf/DH%20Language%20Guidelines%20230710%20FINAL_for%20website_240114.pdf]], Department of Health and Linguistic Landscapes, 2010, 2014
126 -
127 127  [[Guide to medical information>>http://www.plainenglish.co.uk/files/medicalguide.pdf]] from Plain English Campaign.
128 128  
129 129  [[Guidance on writing letters to outpatients>>http://www.aomrc.org.uk/wp-content/uploads/2018/09/Please_write_to_me_Guidance_010918.pdf]] from Academy of Medical Royal Colleges.
... ... @@ -130,30 +130,36 @@
130 130  
131 131  [['Clarity is king – the evidence that reveals the desperate need to re-think the way we write'>>https://gds.blog.gov.uk/2014/02/17/guest-post-clarity-is-king-the-evidence-that-reveals-the-desperate-need-to-re-think-the-way-we-write/]] GDS blog, Mark Morris, 2014
132 132  
132 +[['Connecting with audiences: An evidence-based language sourcebook for the Department of Health'>>http://www.linguisticlandscapes.co.uk/pdf/DH%20Language%20Guidelines%20230710%20FINAL_for%20website_240114.pdf]] Linguistic Landscapes, July 2010
133 +
133 133  [[NHS content style guide beta>>https://beta.nhs.uk/service-manual/content/how-we-write]], January 2019
134 134  
135 135  
136 -=== Legal specific ===
137 +----
137 137  
138 -[['Joseph Kimble—No, the law does not (normally) require legalese'>>url:http://www.ivacheung.com/2015/07/joseph-kimble-no-the-law-does-not-normally-require-legalese-editing-goes-global-2015/]] Editing Goes Global, 2015. Professor Joseph Kimble discusses the "psuedo-precision of legalese".
139 +== ==
139 139  
140 -[[Plain language: the underlying research>>url:https://www.victorialawfoundation.org.au/sites/default/files/resources/Schriver_Karen%20Clarity2012.pdf]], Karen Schriver slide presentation, pages 29 to 35.
141 +== {{id name="mo"/}}Money – plain English guidelines ==
141 141  
142 -[['The public speaks: an empirical study of legal communication'>>https://works.bepress.com/christopher_trudeau/4/]], Christopher Trudeau, study includes solicitor case studies, 2017
143 +=== {{id name="#mo1"/}}1. Use clear language. ===
143 143  
144 -[['Legislative language and judicial politics: The effects of changing parliamentary language on UK immigration disputes'>>https://journals.sagepub.com/doi/10.1177/1369148117705272]], Matthew Williams, 2017. Locked
145 +Dealing with financial issues can be stressful, which means your audience will have less cognitive capability available. Write information so that it is easy for them to understand.
146 +\\
145 145  
146 -[['How Parliament’s failure to clearly articulate immigration policy forces judges to take control'>>https://blogs.lse.ac.uk/politicsandpolicy/parliamentary-language-and-immigration/]], Matthew Williams 'Legislative language and judicial politics' 2017 summarised in London School of Economics blog post
148 +=== {{id name="#mo2"/}}2. Explain financial terminology. ===
147 147  
148 -[['I fought the law and the users won: delivering online voter registration'>>https://gds.blog.gov.uk/2014/06/20/i-fought-the-law-and-the-users-won-delivering-online-voter-registration/]], Peter Herlihy, UK Government Digital Service blog, 2014
150 +Avoid using financial jargon. Acronyms and pseudonyms may make sense internally, but people using your services may not understand them.
149 149  
150 -[[Richmond vs HRA>>url:http://www.alltrials.net/news/judgment-in-richmond-v-hra-judicial-review/]] Richmond pharmaceutical company took the Health Regulatory Authority to court because the website was confusing. A high court judge decided the site was 'unlawful' and ruled against the government. The site was cleared through a legal department. This set a precedent in the UK. You can still be sued even with all the legal language there, if the information is not clear.
151 151  
152 -[[Plain English Campaign>>url:http://www.plainenglish.co.uk/campaigning/past-campaigns/legal/drafting-in-plain-english.html]] believes legalese is unnecessary and does not do what it was intended to. "The argument that clarity should be sacrificed for a document to be comprehensive does not stand up."
153 -
153 +=== {{id name="#mo3"/}}3. Give examples of conceptual arrangements. ===
154 154  
155 -=== Finance specific ===
155 +A tracker or shared ownership mortgage is easier to understand if you give examples.
156 156  
157 +This is important for credit arrangements where there is an initial interest rate that may change.
158 +
159 +
160 +=== {{id name="#UEMO"/}}Usability evidence: plain English in finance ===
161 +
157 157  [[A to Z of financial terms (PDF 87KB)>>http://www.plainenglish.co.uk/files/financialguide.pdf]] from Plain English Campaign.
158 158  
159 159  [[Plain English guide to financial term (PDF 686KB)>>https://www.nala.ie/resources/plain-english-guide-financial-terms]] from National Adult Literacy Agency, Ireland, January 2009.
... ... @@ -164,7 +164,7 @@
164 164  See also:
165 165  
166 166  * [[Plain English>>doc:Plain English.Plain English, simple sentences.WebHome]]
167 -* [[Simple sentences>>doc:Plain English.Simple sentences.WebHome]]
168 -* [[Specialist terms>>doc:Plain English.Specialist terms.WebHome]]
169 -* [[Words to avoid>>doc:Plain English.Words to avoid.WebHome]]
172 +* [[Simple sentences>>url:https://readabilityguidelines.myxwiki.org/xwiki/bin/view/Plain%20English/Simple%20sentences/]]
173 +* [[Specialist terms>>url:https://readabilityguidelines.myxwiki.org/xwiki/bin/view/Plain%20English/Plain%20English%2C%20simple%20sentences/#st]]
174 +* [[Words to avoid>>url:https://readabilityguidelines.myxwiki.org/xwiki/bin/view/Plain%20English/Words%20to%20avoid/]]
170 170  )))
Icon XWiki.XWikiComments[0]
Author
... ... @@ -1,1 +1,0 @@
1 -Anonymous
Comment
... ... @@ -1,5 +1,0 @@
1 -4. Explain medical terms.
2 -Medical terms are unlikely to be understood by your readers. It similar to assuming
3 -
4 -
5 -Should be : it is similar
Date
... ... @@ -1,1 +1,0 @@
1 -2019-04-01 22:40:18.0
Icon XWiki.XWikiComments[1]
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.LizzieBruce
Comment
... ... @@ -1,1 +1,0 @@
1 -Thanks! Feel free to contact me for a wiki edit log in if you spot anything else. lizzie@contentdesign.london
Date
... ... @@ -1,1 +1,0 @@
1 -2019-04-24 11:37:24.0