Skip to Content
Last modified by Lizzie Bruce on 2020/01/11 23:49
From version Icon 1.18 Icon
edited by Lizzie Bruce
on 2019/03/07 16:37
Change comment: (Autosaved)
To version Icon 1.56 Icon
edited by Lizzie Bruce
on 2019/04/24 10:37
Change comment: Added comment

Summary

Details

Icon Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Law, medicine and money
1 +Legal, medical and financial terms
Content
... ... @@ -1,87 +1,152 @@
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 +* **people with low literacy** – will not know meanings of complex vocabulary and terms
10 +* **cognitive impairments** – easy to understand words involve less cognitive load
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
13 +)))
4 4  
5 -Law
6 6  
7 -Medicine
16 +== Guidance ==
8 8  
9 -Money
18 +(% class="wikigeneratedid" %)
19 +The legal, financial and medical professions are known for complex terminology. This is not necessary and confuses people. 
20 +
10 10  
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. 
11 11  
12 -== Law ==
25 +(% class="wikigeneratedid" %)
26 +**Finances: **Many people do not understand financial terms. This causes problems. Complex terminology describing conceptual arrangements is not helpful.
13 13  
14 -Over the years, judges have tried to decide what the legal writers intended their writing to mean. They evolved a set of tools to do this analysis: Statutory Interpretation.
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.
15 15  
16 -Writing in plain English can make meaning clear, so that judges don’t have to rely on these sometimes contradictory interpretations.
17 17  
32 +(% class="wikigeneratedid" id="H1.Usesimplelanguageforlegalterms." %)
33 +[[1. Use simple language for legal terms.>>doc:||anchor="#l1"]]
18 18  
19 -=== 1. Explain the law in context. ===
35 +(% class="wikigeneratedid" id="H2.Explainthelawincontext." %)
36 +[[2. Explain the law in context.>>doc:||anchor="#l2"]]
20 20  
21 -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.
38 +(% class="wikigeneratedid" id="H1.Writeclearly." %)
39 +[[3. Write medical information clearly.>>doc:||anchor="#m1"]]
22 22  
41 +(% class="wikigeneratedid" id="H2.Explainmedicalterms." %)
42 +[[4. Explain medical terms.>>doc:||anchor="#m2"]]
23 23  
24 -== 2. Give simple explanations for complex terms. ==
44 +(% class="wikigeneratedid" id="H1.Useclearlanguage." %)
45 +[[5. Use clear language for financial information.>>doc:||anchor="#mo1"]]
25 25  
26 ->Example:"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)."This content is positioned at the top of a form, not hidden away in references section.
47 +(% class="wikigeneratedid" id="H2.Explainterminology." %)
48 +[[6. Explain financial terminology.>>doc:||anchor="#mo2"]]
27 27  
28 ->Example:"Direct sales contract — exemptions from application of the Act" [Subheading]"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]
50 +(% class="wikigeneratedid" id="H3.Giveexamplesofconceptualarrangements." %)
51 +[[7. Give examples of conceptual financial arrangements.>>doc:||anchor="#mo3"]]
29 29  
30 -== ==
53 +[[Usability evidence>>doc:||anchor="#UEL"]]
54 +
31 31  
32 -== Usability evidence for plain English in law ==
56 +----
33 33  
34 -[['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".
58 +=== {{id name="#l1"/}}1. Use simple language for legal terms. ===
35 35  
36 -[[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.
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.
37 37  
38 -[[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.
39 39  
40 -[[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. Just because all the legal language is there, doesn't mean you can't be sued.
63 +=== {{id name="#l2"/}}2. Explain the law in context. ===
41 41  
42 -[[Plain English Campaign>>url:http://www.plainenglish.co.uk/campaigning/past-campaigns/legal/drafting-in-plain-english.html]] The Plain English Campaign argues that 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.'
65 +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.
43 43  
44 44  
68 +Example:
69 +\\(% class="mark" %)Positioned at the top of a form, not hidden away in references section:
45 45  
46 -== Medicine ==
71 +(((
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)."
73 +)))
47 47  
48 -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. 
49 49  
76 +Example:
77 +\\[Subheading]
78 +(% class="mark" %)"**Direct sales contract — exemptions from application of the Act**(%%)
79 +
50 50  
51 -=== 1. Write clearly. ===
81 +[Body copy]
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."
52 52  
84 +
85 +=== {{id name="#m1"/}}3. Write medical information clearly. ===
86 +
53 53  Users of the information might be in shock or anxious, which reduces cognition.
54 54  
55 55  
56 -=== 2. Explain medical terms. ===
90 +=== {{id name="#m2"/}} 4. Explain medical terms. ===
57 57  
58 -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.
92 +Medical terms are unlikely to be understood by your readers. It similar to assuming they would know a word in a foreign language. Follow the word or phrase with a plain English explanation.
59 59  
60 60  
61 -== Usability evidence for plain English in medicine ==
95 +=== {{id name="#mo1"/}}5. Use clear language for financial information. ===
62 62  
63 -[[Plain English Campaign – guide to medical information>>http://www.plainenglish.co.uk/files/medicalguide.pdf]]
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 +
64 64  
65 -[[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="#mo2"/}}6. Explain financial terminology. ===
66 66  
102 +Avoid using financial jargon. Acronyms and pseudonyms may make sense internally, but people using your services may not understand them.
67 67  
68 -== Money ==
69 69  
70 -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.
105 +=== {{id name="#mo3"/}}7. Give examples of conceptual financial arrangements. ===
71 71  
107 +A tracker or shared ownership mortgage is easier to understand if you give examples.
72 72  
73 -=== 1. Use clear language. ===
109 +This is important for credit arrangements where there is an initial interest rate that may change.
74 74  
75 -=== ===
76 76  
77 -=== 2. Explain terminology. ===
112 +----
78 78  
79 -=== ===
114 +=== {{id name="#UEL"/}}Usability evidence ===
80 80  
81 -=== 3. Give examples of conceptual arrangements. ===
116 +(% class="wikigeneratedid" %)
117 +==== ====
82 82  
119 +[['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]]', Roz Strachan, Government Digital Service, 2016
83 83  
84 -== Usability evidence for plain English in finance ==
121 +[['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".
85 85  
123 +[[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.
86 86  
87 -
125 +[[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.
126 +
127 +[[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.
128 +
129 +[[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."
130 +
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 +[[A to Z of financial terms (PDF 87KB)>>http://www.plainenglish.co.uk/files/financialguide.pdf]] from Plain English Campaign.[[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.
142 +
143 +
144 +(% class="box" %)
145 +(((
146 +See also:
147 +
148 +* [[Plain English>>doc:Plain English.Plain English, simple sentences.WebHome]]
149 +* [[Simple sentences>>doc:Plain English.Simple sentences.WebHome]]
150 +* [[Specialist terms>>doc:Plain English.Specialist terms.WebHome]]
151 +* [[Words to avoid>>doc:Plain English.Words to avoid.WebHome]]
152 +)))
Icon XWiki.XWikiComments[0]
Author
... ... @@ -1,0 +1,1 @@
1 +Anonymous
Comment
... ... @@ -1,0 +1,5 @@
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,0 +1,1 @@
1 +2019-04-01 22:40:18.0
Icon XWiki.XWikiComments[1]
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.LizzieBruce
Comment
... ... @@ -1,0 +1,1 @@
1 +Thanks! Feel free to contact me for a wiki edit log in if you spot anything else. lizzie@contentdesign.london
Date
... ... @@ -1,0 +1,1 @@
1 +2019-04-24 11:37:24.801