Last modified by Lizzie Bruce on 2020/01/11 23:49

From version Icon 1.46 Icon
edited by Lizzie Bruce
on 2019/03/15 20:02
Change comment: There is no comment for this version
To version Icon 1.43 Icon
edited by Lizzie Bruce
on 2019/03/09 03:18
Change comment: There is no comment for this version

Summary

Details

Icon Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Plain language for law, medicine, money
1 +Law, medicine and money
Content
... ... @@ -4,11 +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 -* **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 ocomplex text
9 +* **cognitive impairments** – easy to understand words carry less cognitive load
10 10  * **visual impairments** – short, simple sentences convey meaning in a smaller visual field
11 -* **motor impairments** – it takes less physical effort to navigate shortecontent
11 +* **motor impairments** – it's less tiring when you can understand what you read quickly
12 12  )))
13 13  
14 14  
... ... @@ -18,6 +18,11 @@
18 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 19  
20 20  
21 +=== Law ===
22 +
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 +
25 +
21 21  (% class="wikigeneratedid" id="H1.Usesimplelanguageforlegalterms." %)
22 22  [[1. Use simple language for legal terms.>>doc:||anchor="#l1"]]
23 23  
... ... @@ -24,31 +24,44 @@
24 24  (% class="wikigeneratedid" id="H2.Explainthelawincontext." %)
25 25  [[2. Explain the law in context.>>doc:||anchor="#l2"]]
26 26  
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 +
27 27  (% class="wikigeneratedid" id="H1.Writeclearly." %)
28 -[[3. Write medical information clearly.>>doc:||anchor="#m1"]]
41 +[[1. Write clearly.>>doc:||anchor="#m1"]]
29 29  
30 30  (% class="wikigeneratedid" id="H2.Explainmedicalterms." %)
31 -[[4. Explain medical terms.>>doc:||anchor="#m2"]]
44 +[[2. Explain medical terms.>>doc:||anchor="#m2"]]
32 32  
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 +
33 33  (% class="wikigeneratedid" id="H1.Useclearlanguage." %)
34 -[[5. Use clear language for financial information.>>doc:||anchor="#mo1"]]
55 +[[1. Use clear language.>>doc:||anchor="#mo1"]]
35 35  
36 36  (% class="wikigeneratedid" id="H2.Explainterminology." %)
37 -[[6. Explain financial terminology.>>doc:||anchor="#mo2"]]
58 +[[2. Explain terminology.>>doc:||anchor="#mo2"]]
38 38  
39 39  (% class="wikigeneratedid" id="H3.Giveexamplesofconceptualarrangements." %)
40 -[[7. Give examples of conceptual financial arrangements.>>doc:||anchor="#mo3"]]
61 +[[3. Give examples of conceptual arrangements.>>doc:||anchor="#mo3"]]
41 41  
42 -[[Usability evidence>>doc:||anchor="#UEL"]]
63 +[[Usability evidence: plain English in finance>>doc:||anchor="#UEMO"]]
43 43  
44 44  
45 45  ----
46 46  
47 -== {{id name="l"/}}Law ==
68 +== {{id name="l"/}}Law plain English guidelines ==
48 48  
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 -
51 -
52 52  === {{id name="#l1"/}}1. Use simple language for legal terms. ===
53 53  
54 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.
... ... @@ -75,92 +75,73 @@
75 75  [Body copy]
76 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."
77 77  
96 +== ==
78 78  
79 -----
98 +=== {{id name="#UEL"/}}Usability evidence: plain English in law ===
80 80  
81 -== {{id name="m"/}}Medicine ==
100 +[['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".
82 82  
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 -
102 +[[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.
85 85  
86 -=== {{id name="#m1"/}}3. Write medical information clearly. ===
104 +[[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.
87 87  
88 -Users of the information might be in shock or anxious, which reduces cognition.
106 +[[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.
89 89  
108 +[[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."
90 90  
91 -=== {{id name="#m2"/}} 4. Explain medical terms. ===
92 92  
93 -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.
94 -
95 -
96 96  ----
97 97  
98 -== ==
113 +== {{id name="m"/}}Medicine – plain English guidelines ==
99 99  
100 -== {{id name="mo"/}}Money ==
115 +=== {{id name="#m1"/}}1. Write clearly. ===
101 101  
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 -
117 +Users of the information might be in shock or anxious, which reduces cognition.
104 104  
105 -=== {{id name="#mo1"/}}5. Use clear language for financial information. ===
106 106  
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 -\\
120 +=== {{id name="#m2"/}} 2. Explain medical terms. ===
109 109  
110 -=== {{id name="#mo2"/}}6. Explain financial terminology. ===
122 +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.
111 111  
112 -Avoid using financial jargon. Acronyms and pseudonyms may make sense internally, but people using your services may not understand them.
113 113  
125 +=== {{id name="#UM"/}}Usability evidence: plain English in medicine ===
114 114  
115 -=== {{id name="#mo3"/}}7. Give examples of conceptual financial arrangements. ===
127 +[[Guide to medical information>>http://www.plainenglish.co.uk/files/medicalguide.pdf]] from Plain English Campaign.
116 116  
117 -A tracker or shared ownership mortgage is easier to understand if you give examples.
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.
118 118  
119 -This is important for credit arrangements where there is an initial interest rate that may change.
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
120 120  
133 +[['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
121 121  
122 -=== {{id name="#UEL"/}}Usability evidence ===
135 +[[NHS content style guide beta>>https://beta.nhs.uk/service-manual/content/how-we-write]], January 2019
123 123  
124 -(% class="wikigeneratedid" %)
125 -==== Legal ====
126 126  
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".
138 +----
128 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.
140 +== ==
130 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.
142 +== {{id name="mo"/}}Money plain English guidelines ==
132 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.
144 +=== {{id name="#mo1"/}}1. Use clear language. ===
134 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."
146 +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.
147 +\\
136 136  
137 -====
138 -\\Medical ====
149 +=== {{id name="#mo2"/}}2. Explain financial terminology. ===
139 139  
140 -[[Guide to medical information>>http://www.plainenglish.co.uk/files/medicalguide.pdf]] from Plain English Campaign.
151 +Avoid using financial jargon. Acronyms and pseudonyms may make sense internally, but people using your services may not understand them.
141 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 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
154 +=== {{id name="#mo3"/}}3. Give examples of conceptual arrangements. ===
145 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
156 +A tracker or shared ownership mortgage is easier to understand if you give examples.
147 147  
148 -[[NHS content style guide beta>>https://beta.nhs.uk/service-manual/content/how-we-write]], January 2019
158 +This is important for credit arrangements where there is an initial interest rate that may change.
149 149  
150 150  
151 -==== Finance ====
161 +=== {{id name="#UEMO"/}}Usability evidence: plain English in finance ===
152 152  
153 153  [[A to Z of financial terms (PDF 87KB)>>http://www.plainenglish.co.uk/files/financialguide.pdf]] from Plain English Campaign.
154 154  
155 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 -)))