Changes for page Legal, medical and financial terms
Last modified by Lizzie Bruce on 2020/01/11 23:49
From version 1.40
edited by Lizzie Bruce
on 2019/03/09 02:38
on 2019/03/09 02:38
Change comment:
There is no comment for this version
To version 1.46
edited by Lizzie Bruce
on 2019/03/15 20:02
on 2019/03/15 20:02
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - Law, medicineandmoney1 +Plain language for law, medicine, money - Content
-
... ... @@ -1,11 +1,17 @@ 1 1 (% class="box" %) 2 2 ((( 3 -Following this helps: 4 -\\ 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 5 5 ))) 6 6 7 7 8 -(% class="wikigeneratedid" %) 9 9 == Guidance == 10 10 11 11 (% class="wikigeneratedid" %) ... ... @@ -12,116 +12,149 @@ 12 12 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. 13 13 14 14 15 -[[Law>>doc:||anchor="l"]] 21 +(% class="wikigeneratedid" id="H1.Usesimplelanguageforlegalterms." %) 22 +[[1. Use simple language for legal terms.>>doc:||anchor="#l1"]] 16 16 17 -[[Medicine>>doc:||anchor="m"]] 24 +(% class="wikigeneratedid" id="H2.Explainthelawincontext." %) 25 +[[2. Explain the law in context.>>doc:||anchor="#l2"]] 18 18 19 -[[Money>>doc:||anchor="mo"]] 27 +(% class="wikigeneratedid" id="H1.Writeclearly." %) 28 +[[3. Write medical information clearly.>>doc:||anchor="#m1"]] 20 20 21 ----- 30 +(% class="wikigeneratedid" id="H2.Explainmedicalterms." %) 31 +[[4. Explain medical terms.>>doc:||anchor="#m2"]] 22 22 23 -== {{id name="l"/}}Law == 33 +(% class="wikigeneratedid" id="H1.Useclearlanguage." %) 34 +[[5. Use clear language for financial information.>>doc:||anchor="#mo1"]] 24 24 25 -Judges need to decide what legal writers intended their writing to mean. They have evolved a set of tools for this analysis: Statutory Interpretation. 36 +(% class="wikigeneratedid" id="H2.Explainterminology." %) 37 +[[6. Explain financial terminology.>>doc:||anchor="#mo2"]] 26 26 27 -Writing in plain English can make meaning clear, so that judges don’t have to rely on sometimes contradictory interpretations. 39 +(% class="wikigeneratedid" id="H3.Giveexamplesofconceptualarrangements." %) 40 +[[7. Give examples of conceptual financial arrangements.>>doc:||anchor="#mo3"]] 28 28 42 +[[Usability evidence>>doc:||anchor="#UEL"]] 29 29 30 -=== 1. Use simple language for legal terms. === 31 31 45 +---- 46 + 47 +== {{id name="l"/}}Law == 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 +=== {{id name="#l1"/}}1. Use simple language for legal terms. === 53 + 32 32 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. 33 33 34 34 35 -=== 2. Explain the law in context. === 57 +=== {{id name="#l2"/}}2. Explain the law in context. === 36 36 37 37 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. 38 38 39 ->Example: 40 -> Positioned at the top of a form, not hidden away in references section. 41 41 62 +Example: 63 +\\(% class="mark" %)Positioned at the top of a form, not hidden away in references section. 64 + 42 42 ((( 43 43 "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)." 44 44 ))) 45 45 46 ->Example: 47 -> 48 ->"**Direct sales contract — exemptions from application of the Act**" [Subheading] 49 -> 50 ->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] 51 51 52 -== == 70 +Example: 71 +\\[Subheading] 72 +(% class="mark" %)"**Direct sales contract — exemptions from application of the Act**(%%) 73 + 53 53 54 -== Usability evidence: plain English in law == 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." 55 55 56 -[['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". 57 57 58 - [[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.79 +---- 59 59 60 - [[Thepublic speaks: an empirical studyof legal communication>>url:http://works.bepress.com/cgi/viewcontent.cgi?article=1000&context=christopher_trudeau]], study by Christopher Trudeau (@proftrudeau on Twitter)containing casestudies from solicitors about using legal language.81 +== {{id name="m"/}}Medicine == 61 61 62 -[[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. 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 + 63 63 64 - [[PlainEnglishCampaign>>url:http://www.plainenglish.co.uk/campaigning/past-campaigns/legal/drafting-in-plain-english.html]] believes legaleseis unnecessary and does not do whatitwas intendedto. "The argument thatclarity shouldbe sacrificed fora documentto be comprehensive doesnotstand up."86 +=== {{id name="#m1"/}}3. Write medical information clearly. === 65 65 88 +Users of the information might be in shock or anxious, which reduces cognition. 66 66 67 ----- 68 68 69 -== {{id name="m"/}} Medicine ==91 +=== {{id name="#m2"/}} 4. Explain medical terms. === 70 70 71 - People needetters andreports abouttheir healthfrom doctors and consultantsto be easyto understand.Andtheyneedonlineinformationtobecomprehensible.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. 72 72 73 73 74 - === 1. Write clearly. ===96 +---- 75 75 76 - Usersoftheinformation might be in shock or anxious, which reduces cognition.98 +== == 77 77 100 +== {{id name="mo"/}}Money == 78 78 79 -=== 2. Explain medical terms. === 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 + 80 80 81 - Medicalterms are likely not to be understoodby your readers.It is likelyassuming they would know a wordin a foreignlanguage.Follow the wordor phrase withaplainEnglish explanation.105 +=== {{id name="#mo1"/}}5. Use clear language for financial information. === 82 82 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 +\\ 83 83 84 -== Usability evidence:plainEnglishin medicine==110 +=== {{id name="#mo2"/}}6. Explain financial terminology. === 85 85 86 - [[Guidetomedicalinformation>>http://www.plainenglish.co.uk/files/medicalguide.pdf]] from PlainEnglishCampaign.112 +Avoid using financial jargon. Acronyms and pseudonyms may make sense internally, but people using your services may not understand them. 87 87 88 -[[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. 89 89 90 - [['Clarityisking – theevidencethat reveals thedesperateneed tore-think theway 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,2014115 +=== {{id name="#mo3"/}}7. Give examples of conceptual financial arrangements. === 91 91 92 - [['Connectingwithaudiences:Anevidence-basedlanguagesourcebookforhe DepartmentofHealth'>>http://www.linguisticlandscapes.co.uk/pdf/DH%20Language%20Guidelines%20230710%20FINAL_for%20website_240114.pdf]] LinguisticLandscapes, July 2010117 +A tracker or shared ownership mortgage is easier to understand if you give examples. 93 93 94 - [[NHScontentstyle guidebeta>>https://beta.nhs.uk/service-manual/content/how-we-write]],January2019119 +This is important for credit arrangements where there is an initial interest rate that may change. 95 95 96 96 97 - ----122 +=== {{id name="#UEL"/}}Usability evidence === 98 98 99 -== == 124 +(% class="wikigeneratedid" %) 125 +==== Legal ==== 100 100 101 - =={{id name="mo"/}}Money==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". 102 102 103 - Manypeopledo not understandtheirfinancesanditcausesthem problems. Complexterminology describing concept-heavy arrangementsabout aon-tangible resourcemakesthingsdifficultforeverybody.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. 104 104 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. 105 105 106 - ===1.Use clear language.===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. 107 107 108 -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. 109 -\\ 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." 110 110 111 -=== 2. Explain terminology. === 137 +==== 138 +\\Medical ==== 112 112 113 - Avoidusingfinancialjargon. Acronymsand pseudonyms may make sense internally, buteople usingyour servicesy notunderstandthem.140 +[[Guide to medical information>>http://www.plainenglish.co.uk/files/medicalguide.pdf]] from Plain English Campaign. 114 114 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. 115 115 116 - ===3.Give examplesofconceptualgements.===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 117 117 118 - Atrackerorsharedownershipmortgageis easierrstandyou giveexamples.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 119 119 120 - Thisis importantfor creditarrangements wherethereisaninitialinterestatethat maychange.148 +[[NHS content style guide beta>>https://beta.nhs.uk/service-manual/content/how-we-write]], January 2019 121 121 122 122 123 -== Usability evidence: plainEnglish in finance ==151 +==== Finance ==== 124 124 125 125 [[A to Z of financial terms (PDF 87KB)>>http://www.plainenglish.co.uk/files/financialguide.pdf]] from Plain English Campaign. 126 126 127 127 [[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 +)))