Skip to Content
Last modified by Lizzie Bruce on 2020/01/11 23:49
From version Icon 1.28 Icon
edited by Lizzie Bruce
on 2019/03/07 17:20
Change comment: There is no comment for this version
To version Icon 1.47 Icon
edited by Lizzie Bruce
on 2019/03/15 20:21
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 health, finances and law
Content
... ... @@ -1,105 +1,157 @@
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.
1 +(% class="box" %)
2 +(((
3 +{{id name="#UM"/}}Following this helps:
4 +
3 3  
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 +)))
4 4  
5 -[[Law>>doc:||anchor="l"]]
6 6  
7 -[[Medicine>>doc:||anchor="m"]]
15 +== Guidance ==
8 8  
9 -[[Money>>doc:||anchor="mo"]]
17 +(% class="wikigeneratedid" %)
18 +The legal, financial and medical professions are known for complex terminology. This is not necessary and confuses people. 
19 +
10 10  
21 +(% class="wikigeneratedid" %)
22 +**Health:** People need to understand doctors' letters and consultant reports easily. They need to be able to comprehend online information about health. 
11 11  
12 -== {{id name="l"/}}Law ==
24 +(% class="wikigeneratedid" %)
25 +**Finances: **Many people do not understand financial terms. This causes problems. Complex terminology describing conceptual arrangements is not helpful.
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.
27 +(% class="wikigeneratedid" %)
28 +**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.
15 15  
16 -Writing in plain English can make meaning clear, so that judges don’t have to rely on sometimes contradictory interpretations.
17 17  
31 +(% class="wikigeneratedid" id="H1.Usesimplelanguageforlegalterms." %)
32 +[[1. Use simple language for legal terms.>>doc:||anchor="#l1"]]
18 18  
19 -=== 1. Use simple language for legal terms. ===
34 +(% class="wikigeneratedid" id="H2.Explainthelawincontext." %)
35 +[[2. Explain the law in context.>>doc:||anchor="#l2"]]
20 20  
21 -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.
37 +(% class="wikigeneratedid" id="H1.Writeclearly." %)
38 +[[3. Write medical information clearly.>>doc:||anchor="#m1"]]
22 22  
40 +(% class="wikigeneratedid" id="H2.Explainmedicalterms." %)
41 +[[4. Explain medical terms.>>doc:||anchor="#m2"]]
23 23  
24 -(% class="wikigeneratedid" %)
25 -=== 2. Explain the law in context. ===
43 +(% class="wikigeneratedid" id="H1.Useclearlanguage." %)
44 +[[5. Use clear language for financial information.>>doc:||anchor="#mo1"]]
26 26  
27 -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.
46 +(% class="wikigeneratedid" id="H2.Explainterminology." %)
47 +[[6. Explain financial terminology.>>doc:||anchor="#mo2"]]
28 28  
29 ->Example:
30 -> "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)."
31 -> This content is positioned at the top of a form, not hidden away in references section.
49 +(% class="wikigeneratedid" id="H3.Giveexamplesofconceptualarrangements." %)
50 +[[7. Give examples of conceptual financial arrangements.>>doc:||anchor="#mo3"]]
32 32  
33 ->Example:
34 ->
35 ->"Direct sales contract — exemptions from application of the Act" [Subheading]"
36 ->
37 ->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]
52 +[[Usability evidence>>doc:||anchor="#UEL"]]
53 +
38 38  
39 -== ==
55 +----
40 40  
41 -== Usability evidence for plain English in law ==
57 +=== {{id name="#l1"/}}1. Use simple language for legal terms. ===
42 42  
43 -[['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 +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.
44 44  
45 -[[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.
46 46  
47 -[[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 +=== {{id name="#l2"/}}2. Explain the law in context. ===
48 48  
49 -[[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.
64 +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.
50 50  
51 -[[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."
52 52  
67 +Example:
68 +\\(% class="mark" %)Positioned at the top of a form, not hidden away in references section:
53 53  
70 +(((
71 +"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)."
72 +)))
54 54  
55 -== {{id name="m"/}}Medicine ==
56 56  
57 -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. 
75 +Example:
76 +\\[Subheading]
77 +(% class="mark" %)"**Direct sales contract — exemptions from application of the Act**(%%)
78 +
58 58  
80 +[Body copy]
81 +(% 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."
59 59  
60 -=== 1. Write clearly. ===
61 61  
84 +=== {{id name="#m1"/}}3. Write medical information clearly. ===
85 +
62 62  Users of the information might be in shock or anxious, which reduces cognition.
63 63  
64 64  
65 -=== 2. Explain medical terms. ===
89 +=== {{id name="#m2"/}} 4. Explain medical terms. ===
66 66  
67 67  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.
68 68  
69 69  
70 -== Usability evidence for plain English in medicine ==
94 +=== {{id name="#mo1"/}}5. Use clear language for financial information. ===
71 71  
72 -[[Guide to medical information>>http://www.plainenglish.co.uk/files/medicalguide.pdf]] from Plain English Campaign.
96 +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.
97 +
73 73  
74 -[[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.
99 +=== {{id name="#mo2"/}}6. Explain financial terminology. ===
75 75  
101 +Avoid using financial jargon. Acronyms and pseudonyms may make sense internally, but people using your services may not understand them.
76 76  
77 -== {{id name="mo"/}}Money ==
78 78  
79 -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.
104 +=== {{id name="#mo3"/}}7. Give examples of conceptual financial arrangements. ===
80 80  
106 +A tracker or shared ownership mortgage is easier to understand if you give examples.
81 81  
82 -=== 1. Use clear language. ===
108 +This is important for credit arrangements where there is an initial interest rate that may change.
83 83  
84 -Dealing with financial issues can be stressful, which means your audience will have less cognitive capability available. Make your information easy for them to understand.
85 85  
86 -=== ===
111 +----
87 87  
88 -=== 2. Explain terminology. ===
113 +=== {{id name="#UEL"/}}Usability evidence ===
89 89  
90 -Avoid using financial jargon. Acronyms and pseudonyms may make sense internally, but people using your services may not understand them.
115 +(% class="wikigeneratedid" %)
116 +==== Legal ====
91 91  
92 -
118 +[['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".
93 93  
94 -=== 3. Give examples of conceptual arrangements. ===
120 +[[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.
95 95  
96 -A tracker or shared ownership mortgage is easier to understand if you give examples.
122 +[[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.
97 97  
98 -This is important for credit arrangements where there is an initial interest rate that may change.
124 +[[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.
99 99  
126 +[[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."
100 100  
101 -== Usability evidence for plain English in finance ==
128 +====
129 +Medical ====
102 102  
131 +[[Guide to medical information>>http://www.plainenglish.co.uk/files/medicalguide.pdf]] from Plain English Campaign.
132 +
133 +[[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.
134 +
135 +[['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
136 +
137 +[['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
138 +
139 +[[NHS content style guide beta>>https://beta.nhs.uk/service-manual/content/how-we-write]], January 2019 
140 +
141 +
142 +==== Finance ====
143 +
103 103  [[A to Z of financial terms (PDF 87KB)>>http://www.plainenglish.co.uk/files/financialguide.pdf]] from Plain English Campaign.
104 104  
105 105  [[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.
147 +
148 +
149 +(% class="box" %)
150 +(((
151 +See also:
152 +
153 +* [[Plain English>>doc:Plain English.Plain English, simple sentences.WebHome]]
154 +* [[Simple sentences>>url:https://readabilityguidelines.myxwiki.org/xwiki/bin/view/Plain%20English/Simple%20sentences/]]
155 +* [[Specialist terms>>url:https://readabilityguidelines.myxwiki.org/xwiki/bin/view/Plain%20English/Plain%20English%2C%20simple%20sentences/#st]]
156 +* [[Words to avoid>>url:https://readabilityguidelines.myxwiki.org/xwiki/bin/view/Plain%20English/Words%20to%20avoid/]]
157 +)))