Changes for page Legal, medical and financial terms

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

From 1.39 to 1.38 From 2.1 to 1.58

From version

1.58

edited by Lizzie Bruce
on 2019/04/24 11:02

Change comment: Adding evidence from AM

To version

1.39

edited by Lizzie Bruce
on 2019/03/08 17:01

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Objects (0 modified, 0 added, 2 removed)
- XWiki.XWikiComments[0]
- XWiki.XWikiComments[1]

Details

Page properties

Title

@@ -1,1 +1,1 @@
--Legal, medical and financial terms
++Law, medicine and money

Content

@@ -1,155 +18,110 @@
--(% class="box" %)
--(((
--{{id name="#UM"/}}Following this helps:
--
--
--* **people in a hurry** – simply written content is quicker to scan
--* **people who are stressed** – if you're anxious it's difficult to understand complex text
--* **people who are multi-tasking** – when distracted complex text is harder to comprehend
--* **people with low literacy** – will not know meanings of complex vocabulary and terms
--* **cognitive impairments** – easy to understand words involve less cognitive load
--* **visual impairments** – short, simple sentences convey meaning in a smaller visual field
--* **motor impairments** – it takes less physical effort to navigate shorter content
--)))
--
--
--== Guidance ==
--
  (% class="wikigeneratedid" %)
--The legal, financial and medical professions are known for complex terminology. This is not necessary and confuses people.
--
++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.
--(% class="wikigeneratedid" %)
--**Health:** People need to understand doctors' letters and consultant reports easily. They need to be able to comprehend online information about health.
--(% class="wikigeneratedid" %)
--**Finances: **Many people do not understand financial terms. This causes problems. Complex terminology describing conceptual arrangements is not helpful.
++== {{id name="l"/}}Law ==
--(% class="wikigeneratedid" %)
--**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.
++Judges need to decide what legal writers intended their writing to mean. They have evolved a set of tools for this analysis: Statutory Interpretation.
++Writing in plain English can make meaning clear, so that judges don’t have to rely on sometimes contradictory interpretations.
--(% class="wikigeneratedid" id="H1.Usesimplelanguageforlegalterms." %)
--[[1. Use simple language for legal terms.>>doc:||anchor="#l1"]]
--(% class="wikigeneratedid" id="H2.Explainthelawincontext." %)
--[[2. Explain the law in context.>>doc:||anchor="#l2"]]
++=== 1. Use simple language for legal terms. ===
--(% class="wikigeneratedid" id="H1.Writeclearly." %)
--[[3. Write medical information clearly.>>doc:||anchor="#m1"]]
++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.
--(% class="wikigeneratedid" id="H2.Explainmedicalterms." %)
--[[4. Explain medical terms.>>doc:||anchor="#m2"]]
--(% class="wikigeneratedid" id="H1.Useclearlanguage." %)
--[[5. Use clear language for financial information.>>doc:||anchor="#mo1"]]
++=== 2. Explain the law in context. ===
--(% class="wikigeneratedid" id="H2.Explainterminology." %)
--[[6. Explain financial terminology.>>doc:||anchor="#mo2"]]
++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.
--(% class="wikigeneratedid" id="H3.Giveexamplesofconceptualarrangements." %)
--[[7. Give examples of conceptual financial arrangements.>>doc:||anchor="#mo3"]]
++>Example:
++> Positioned at the top of a form, not hidden away in references section.
--[[Usability evidence>>doc:||anchor="#UEL"]]
--
++(((
++"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)."
++)))
------
++>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]
--=== {{id name="#l1"/}}1. Use simple language for legal terms. ===
++==   ==
--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.
++== Usability evidence: plain English in law ==
++[['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".
--=== {{id name="#l2"/}}2. Explain the law in context. ===
++[[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.
--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.
++[[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.
++[[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.
--Example:
--\\(% class="mark" %)Positioned at the top of a form, not hidden away in references section:
++[[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."
--(((
--"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)."
--)))
++----
--Example:
--\\[Subheading]
--(% class="mark" %)"**Direct sales contract — exemptions from application of the Act**(%%)
--
++== {{id name="m"/}}Medicine ==
--[Body copy]
--(% 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."
++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.
--=== {{id name="#m1"/}}3. Write medical information clearly. ===
++=== 1. Write clearly. ===
  Users of the information might be in shock or anxious, which reduces cognition.
--=== {{id name="#m2"/}} 4. Explain medical terms. ===
++=== 2. Explain medical terms. ===
--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.
++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.
--=== {{id name="#mo1"/}}5. Use clear language for financial information. ===
++== Usability evidence: plain English in medicine ==
--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.
--
++[[Guide to medical information>>http://www.plainenglish.co.uk/files/medicalguide.pdf]] from Plain English Campaign.
--=== {{id name="#mo2"/}}6. Explain financial terminology. ===
++[[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.
--Avoid using financial jargon. Acronyms and pseudonyms may make sense internally, but people using your services may not understand them.
++[['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
++[['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
--=== {{id name="#mo3"/}}7. Give examples of conceptual financial arrangements. ===
++[[NHS content style guide beta>>https://beta.nhs.uk/service-manual/content/how-we-write]], January 2019
--A tracker or shared ownership mortgage is easier to understand if you give examples.
--This is important for credit arrangements where there is an initial interest rate that may change.
--
--
  ----
--=== {{id name="#UEL"/}}Usability evidence ===
--
--(% class="wikigeneratedid" id="H" %)
--[['Department of Health Stakeholder Report: 2012'>>https://www.gov.uk/government/publications/department-of-health-stakeholder-report-2012]], research by Ipsos MORI, 2012
--
  (% class="wikigeneratedid" %)
--[['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]], DoH and Linguistic Landscapes, 2010, revised 2014
++==   ==
--[['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]]', blog post by, Roz Strachan, Government Digital Service, 2016
++== {{id name="mo"/}}Money ==
--[['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".
++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.
--[[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.
--[[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.
++=== 1. Use clear language. ===
--[[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.
++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.
++\\
--[[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."
++=== 2. Explain terminology. ===
--[[Guide to medical information>>http://www.plainenglish.co.uk/files/medicalguide.pdf]] from Plain English Campaign.
++Avoid using financial jargon. Acronyms and pseudonyms may make sense internally, but people using your services may not understand them.
--[[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.
--[['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
++=== 3. Give examples of conceptual arrangements. ===
--[['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
++A tracker or shared ownership mortgage is easier to understand if you give examples.
--[[NHS content style guide beta>>https://beta.nhs.uk/service-manual/content/how-we-write]], January 2019
++This is important for credit arrangements where there is an initial interest rate that may change.
--[[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.
++== Usability evidence: plain English in finance ==
--(% class="box" %)
--(((
--See also:
++[[A to Z of financial terms (PDF 87KB)>>http://www.plainenglish.co.uk/files/financialguide.pdf]] from Plain English Campaign.
--* [[Plain English>>doc:Plain English.Plain English, simple sentences.WebHome]]
--* [[Simple sentences>>doc:Plain English.Simple sentences.WebHome]]
--* [[Specialist terms>>doc:Plain English.Specialist terms.WebHome]]
--* [[Words to avoid>>doc:Plain English.Words to avoid.WebHome]]
--)))
++[[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.

XWiki.XWikiComments[0]

Author

...	...	@@ -1,1 +1,0 @@
1		-Anonymous

Comment

@@ -1,5 +1,0 @@
--4. Explain medical terms.
--Medical terms are unlikely to be understood by your readers. It similar to assuming
--
--
--Should be : it is similar

Date

...	...	@@ -1,1 +1,0 @@
1		-2019-04-01 22:40:18.0

XWiki.XWikiComments[1]