Skip to Content
Last modified by Lizzie Bruce on 2020/01/11 23:49
From version Icon 1.21 Icon
edited by Lizzie Bruce
on 2019/03/07 16:49
Change comment: There is no comment for this version
To version Icon 1.46 Icon
edited by Lizzie Bruce
on 2019/03/15 20:02
Change comment: There is no comment for this version

Summary

Details

Icon Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Law, medicine and money
1 +Plain language for law, medicine, money
Content
... ... @@ -1,92 +1,166 @@
1 +(% class="box" %)
2 +(((
3 +{{id name="#UM"/}}Following this helps:
4 +
5 +
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 +* **cognitive impairments** – easy to understand words involve less cognitive load
10 +* **visual impairments** – short, simple sentences convey meaning in a smaller visual field
11 +* **motor impairments** – it takes less physical effort to navigate shorter content
12 +)))
13 +
14 +
15 +== Guidance ==
16 +
1 1  (% class="wikigeneratedid" %)
2 -The legal, medical and financial professions are known for using complex terminology. But it's not necessary and confuses people who use their services.
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. 
19 +
3 3  
21 +(% class="wikigeneratedid" id="H1.Usesimplelanguageforlegalterms." %)
22 +[[1. Use simple language for legal terms.>>doc:||anchor="#l1"]]
4 4  
5 -[[Law>>doc:||anchor="l"]]
24 +(% class="wikigeneratedid" id="H2.Explainthelawincontext." %)
25 +[[2. Explain the law in context.>>doc:||anchor="#l2"]]
6 6  
7 -[[Medicine>>doc:||anchor="m"]]
27 +(% class="wikigeneratedid" id="H1.Writeclearly." %)
28 +[[3. Write medical information clearly.>>doc:||anchor="#m1"]]
8 8  
9 -[[Money>>doc:||anchor="mo"]]
30 +(% class="wikigeneratedid" id="H2.Explainmedicalterms." %)
31 +[[4. Explain medical terms.>>doc:||anchor="#m2"]]
10 10  
33 +(% class="wikigeneratedid" id="H1.Useclearlanguage." %)
34 +[[5. Use clear language for financial information.>>doc:||anchor="#mo1"]]
11 11  
12 -== {{id name="l"/}}Law ==
36 +(% class="wikigeneratedid" id="H2.Explainterminology." %)
37 +[[6. Explain financial terminology.>>doc:||anchor="#mo2"]]
13 13  
14 -Judges need to decide what legal writers intended their writing to mean. They have evolved a set of tools for this analysis: Statutory Interpretation.
39 +(% class="wikigeneratedid" id="H3.Giveexamplesofconceptualarrangements." %)
40 +[[7. Give examples of conceptual financial arrangements.>>doc:||anchor="#mo3"]]
15 15  
16 -Writing in plain English can make meaning clear, so that judges don’t have to rely on sometimes contradictory interpretations.
42 +[[Usability evidence>>doc:||anchor="#UEL"]]
17 17  
18 -If information on your website is unclear your organisation could be taken to court and lose, even if the content was approved by a legal department.
19 19  
45 +----
20 20  
21 -=== 1. Explain the law simply, in context. ===
47 +== {{id name="l"/}}Law ==
22 22  
23 -When you refer to a law, or part of it, explain what the law is about right there at the point of user need. Do not only refer to it in a reference section or appendix.
49 +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.
50 +
24 24  
25 ->Example:
26 -> "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)."
27 -> This content is positioned at the top of a form, not hidden away in references section.
52 +=== {{id name="#l1"/}}1. Use simple language for legal terms. ===
28 28  
29 ->Example:
30 ->
31 ->"Direct sales contract — exemptions from application of the Act" [Subheading]"
32 ->
33 ->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." [Body copy]
54 +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.
34 34  
35 -== ==
36 36  
37 -== Usability evidence for plain English in law ==
57 +=== {{id name="#l2"/}}2. Explain the law in context. ===
38 38  
39 -[['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".
59 +When you refer to a law, or part of it, explain what that law is at the point of user need. Do not only refer to it in a reference section or appendix.
40 40  
41 -[[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.
42 42  
43 -[[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.
62 +Example:
63 +\\(% class="mark" %)Positioned at the top of a form, not hidden away in references section.
44 44  
45 -[[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.
65 +(((
66 +"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)."
67 +)))
46 46  
47 -[[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."
48 48  
70 +Example:
71 +\\[Subheading]
72 +(% class="mark" %)"**Direct sales contract — exemptions from application of the Act**(%%)
73 +
49 49  
75 +[Body copy]
76 +(% 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."
50 50  
51 -== {{id name="m"/}}Medicine ==
52 52  
53 -People need letters and reports about their health from doctors and consultants to be easy to understand. And they need online information to be comprehensible. 
79 +----
54 54  
81 +== {{id name="m"/}}Medicine ==
55 55  
56 -=== 1. Write clearly. ===
83 +People need doctors' letters and consultant reports to be easy to understand. And they need online information about health conditions to be comprehensible.  
84 +
57 57  
86 +=== {{id name="#m1"/}}3. Write medical information clearly. ===
87 +
58 58  Users of the information might be in shock or anxious, which reduces cognition.
59 59  
60 60  
61 -=== 2. Explain medical terms. ===
91 +=== {{id name="#m2"/}} 4. Explain medical terms. ===
62 62  
63 63  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.
64 64  
65 65  
66 -== Usability evidence for plain English in medicine ==
96 +----
67 67  
68 -[[Plain English Campaign – guide to medical information>>http://www.plainenglish.co.uk/files/medicalguide.pdf]]
98 +== ==
69 69  
70 -[[Academy of Medical Royal Colleges – Guidance on writing letters to outpatients>>http://www.aomrc.org.uk/wp-content/uploads/2018/09/Please_write_to_me_Guidance_010918.pdf]]
100 +== {{id name="mo"/}}Money ==
71 71  
102 +Many people do not understand financial terms. This causes problems. Complex terminology describing conceptual arrangements about a non-tangible resource does not help anyone. 
103 +
72 72  
73 -== {{id name="mo"/}}Money ==
105 +=== {{id name="#mo1"/}}5. Use clear language for financial information. ===
74 74  
75 -Many people do not understand their finances and it causes them problems. Complex terminology describing concept-heavy arrangements about a non-tangible resource makes things difficult for everybody.
107 +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.
108 +\\
76 76  
110 +=== {{id name="#mo2"/}}6. Explain financial terminology. ===
77 77  
78 -=== 1. Use clear language. ===
112 +Avoid using financial jargon. Acronyms and pseudonyms may make sense internally, but people using your services may not understand them.
79 79  
80 -=== ===
81 81  
82 -=== 2. Explain terminology. ===
115 +=== {{id name="#mo3"/}}7. Give examples of conceptual financial arrangements. ===
83 83  
84 -=== ===
117 +A tracker or shared ownership mortgage is easier to understand if you give examples.
85 85  
86 -=== 3. Give examples of conceptual arrangements. ===
119 +This is important for credit arrangements where there is an initial interest rate that may change.
87 87  
88 88  
89 -== Usability evidence for plain English in finance ==
122 +=== {{id name="#UEL"/}}Usability evidence ===
90 90  
124 +(% class="wikigeneratedid" %)
125 +==== Legal ====
91 91  
92 -
127 +[['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".
128 +
129 +[[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.
130 +
131 +[[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.
132 +
133 +[[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.
134 +
135 +[[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."
136 +
137 +====
138 +\\Medical ====
139 +
140 +[[Guide to medical information>>http://www.plainenglish.co.uk/files/medicalguide.pdf]] from Plain English Campaign.
141 +
142 +[[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.
143 +
144 +[['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
145 +
146 +[['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
147 +
148 +[[NHS content style guide beta>>https://beta.nhs.uk/service-manual/content/how-we-write]], January 2019
149 +
150 +
151 +==== Finance ====
152 +
153 +[[A to Z of financial terms (PDF 87KB)>>http://www.plainenglish.co.uk/files/financialguide.pdf]] from Plain English Campaign.
154 +
155 +[[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.
156 +
157 +
158 +(% class="box" %)
159 +(((
160 +See also:
161 +
162 +* [[Plain English>>doc:Plain English.Plain English, simple sentences.WebHome]]
163 +* [[Simple sentences>>url:https://readabilityguidelines.myxwiki.org/xwiki/bin/view/Plain%20English/Simple%20sentences/]]
164 +* [[Specialist terms>>url:https://readabilityguidelines.myxwiki.org/xwiki/bin/view/Plain%20English/Plain%20English%2C%20simple%20sentences/#st]]
165 +* [[Words to avoid>>url:https://readabilityguidelines.myxwiki.org/xwiki/bin/view/Plain%20English/Words%20to%20avoid/]]
166 +)))