Changes for page Legal, medical and financial terms

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,7 +1,14 @@
1	1	(% class="wikigeneratedid" %)
2		-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.
	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.
3	3
4	4
	5	+[[Law>>doc:||anchor="l"]]
	6	+
	7	+[[Medicine>>doc:||anchor="m"]]
	8	+
	9	+[[Money>>doc:||anchor="mo"]]
	10	+
	11	+
5	5	== {{id name="l"/}}Law ==
6	6
7	7	Judges need to decide what legal writers intended their writing to mean. They have evolved a set of tools for this analysis: Statutory Interpretation.
...	...	@@ -8,32 +8,26 @@
8	8
9	9	Writing in plain English can make meaning clear, so that judges don’t have to rely on sometimes contradictory interpretations.
10	10
	18	+If information on your website is unclear your organisation could be taken to court and lose, even if the content was approved by a legal department.
11	11
12		-=== 1. Use simple language for legal terms. ===
13	13
14		-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.
	21	+=== 1. Explain the law simply, in context. ===
15	15
	23	+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.
16	16
17		-=== 2. Explain the law in context. ===
18		-
19		-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.
20		-
21	21	>Example:
22		-> Positioned at the top of a form, not hidden away in references section.
	26	+> "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)."
	27	+> This content is positioned at the top of a form, not hidden away in references section.
23	23
24		-(((
25		-"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)."
26		-)))
27		-
28	28	>Example:
29	29	>
30		->"**Direct sales contract — exemptions from application of the Act**"  [Subheading]
	31	+>"Direct sales contract — exemptions from application of the Act" [Subheading]"
31	31	>
32		->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]
	33	+>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]
33	33
34	34	== ==
35	35
36		-== Usability evidence: plain English in law ==
	37	+== Usability evidence for plain English in law ==
37	37
38	38	[['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".
39	39
...	...	@@ -46,7 +46,6 @@
46	46	[[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."
47	47
48	48
49		-----
50	50
51	51	== {{id name="m"/}}Medicine ==
52	52
...	...	@@ -63,24 +63,13 @@
63	63	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.
64	64
65	65
66		-== Usability evidence: plain English in medicine ==
	66	+== Usability evidence for plain English in medicine ==
67	67
68		-[[Guide to medical information>>http://www.plainenglish.co.uk/files/medicalguide.pdf]] from Plain English Campaign.
	68	+[[Plain English Campaign – guide to medical information>>http://www.plainenglish.co.uk/files/medicalguide.pdf]]
69	69
70		-[[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.
	70	+[[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]]
71	71
72		-[['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
73	73
74		-[['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
75		-
76		-[[NHS content style guide beta>>https://beta.nhs.uk/service-manual/content/how-we-write]], January 2019
77		-
78		-
79		-----
80		-
81		-(% class="wikigeneratedid" %)
82		-== ==
83		-
84	84	== {{id name="mo"/}}Money ==
85	85
86	86	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.
...	...	@@ -88,23 +88,16 @@
88	88
89	89	=== 1. Use clear language. ===
90	90
91		-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.
92		-\\
	80	+=== ===
93	93
94	94	=== 2. Explain terminology. ===
95	95
96		-Avoid using financial jargon. Acronyms and pseudonyms may make sense internally, but people using your services may not understand them.
	84	+=== ===
97	97
98		-
99	99	=== 3. Give examples of conceptual arrangements. ===
100	100
101		-A tracker or shared ownership mortgage is easier to understand if you give examples.
102	102
103		-This is important for credit arrangements where there is an initial interest rate that may change.
	89	+== Usability evidence for plain English in finance ==
104	104
105	105
106		-== Usability evidence: plain English in finance ==
107		-
108		-[[A to Z of financial terms (PDF 87KB)>>http://www.plainenglish.co.uk/files/financialguide.pdf]] from Plain English Campaign.
109		-
110		-[[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.
	92	+