Changes for page Legal, medical and financial terms

Summary

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

Details

Page properties

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 harder to comprehend things
	8	+* **people who are multi-tasking** – when distracted you cannot concentrate on complex text
	9	+* **cognitive impairments** – easy to understand words carry less cognitive load
	10	+* **visual impairments** – short, simple sentences convey meaning in a smaller visual field
	11	+* **motor impairments** – it's less tiring when you can understand what you read quickly
5	5	)))
6	6
7	7
8		-(% class="wikigeneratedid" %)
9	9	== Guidance ==
10	10
11	11	(% class="wikigeneratedid" %)
...	...	@@ -12,47 +12,84 @@
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	+=== Law ===
16	16
17		-[[Medicine>>doc:||anchor="m"]]
	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	+
18	18
19		-[[Money>>doc:||anchor="mo"]]
	26	+(% class="wikigeneratedid" id="H1.Usesimplelanguageforlegalterms." %)
	27	+[[1. Use simple language for legal terms.>>doc:||anchor="#l1"]]
20	20
21		-----
	29	+(% class="wikigeneratedid" id="H2.Explainthelawincontext." %)
	30	+[[2. Explain the law in context.>>doc:||anchor="#l2"]]
22	22
23		-== {{id name="l"/}}Law ==
	32	+[[Usability evidence: plain English in law>>doc:||anchor="#UEL"]]
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.
26	26
27		-Writing in plain English can make meaning clear, so that judges don’t have to rely on sometimes contradictory interpretations.
	35	+=== Medicine ===
28	28
	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	+
29	29
30		-=== 1. Use simple language for legal terms. ===
	40	+(% class="wikigeneratedid" id="H1.Writeclearly." %)
	41	+[[1. Write clearly.>>doc:||anchor="#m1"]]
31	31
	43	+(% class="wikigeneratedid" id="H2.Explainmedicalterms." %)
	44	+[[2. Explain medical terms.>>doc:||anchor="#m2"]]
	45	+
	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	+
	54	+(% class="wikigeneratedid" id="H1.Useclearlanguage." %)
	55	+[[1. Use clear language.>>doc:||anchor="#mo1"]]
	56	+
	57	+(% class="wikigeneratedid" id="H2.Explainterminology." %)
	58	+[[2. Explain terminology.>>doc:||anchor="#mo2"]]
	59	+
	60	+(% class="wikigeneratedid" id="H3.Giveexamplesofconceptualarrangements." %)
	61	+[[3. Give examples of conceptual arrangements.>>doc:||anchor="#mo3"]]
	62	+
	63	+[[Usability evidence: plain English in finance>>doc:||anchor="#UEMO"]]
	64	+
	65	+
	66	+----
	67	+
	68	+== {{id name="l"/}}Law – plain English guidelines ==
	69	+
	70	+=== {{id name="#l1"/}}1. Use simple language for legal terms. ===
	71	+
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. ===
	75	+=== {{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
	80	+Example:
	81	+\\(% class="mark" %)Positioned at the top of a form, not hidden away in references section.
	82	+
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		-== ==
	88	+Example:
	89	+\\[Subheading]
	90	+(% class="mark" %)"**Direct sales contract — exemptions from application of the Act**(%%)
	91	+
53	53
54		-== Usability evidence: plain English in law ==
	93	+[Body copy]
	94	+(% 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
	96	+
	97	+=== {{id name="#UEL"/}}Usability evidence: plain English in law ===
	98	+
56	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	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.
...	...	@@ -66,22 +66,19 @@
66	66
67	67	----
68	68
69		-== {{id name="m"/}}Medicine ==
	112	+== {{id name="m"/}}Medicine – plain English guidelines ==
70	70
71		-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.
	114	+=== {{id name="#m1"/}}1. Write clearly. ===
72	72
73		-
74		-=== 1. Write clearly. ===
75		-
76	76	Users of the information might be in shock or anxious, which reduces cognition.
77	77
78	78
79		-=== 2. Explain medical terms. ===
	119	+=== {{id name="#m2"/}} 2. Explain medical terms. ===
80	80
81	81	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.
82	82
83	83
84		-== Usability evidence: plain English in medicine ==
	124	+=== {{id name="#UM"/}}Usability evidence: plain English in medicine ===
85	85
86	86	[[Guide to medical information>>http://www.plainenglish.co.uk/files/medicalguide.pdf]] from Plain English Campaign.
87	87
...	...	@@ -98,22 +98,19 @@
98	98
99	99	== ==
100	100
101		-== {{id name="mo"/}}Money ==
	141	+== {{id name="mo"/}}Money – plain English guidelines ==
102	102
103		-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.
	143	+=== {{id name="#mo1"/}}1. Use clear language. ===
104	104
105		-
106		-=== 1. Use clear language. ===
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.
	145	+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.
109	109	\\
110	110
111		-=== 2. Explain terminology. ===
	148	+=== {{id name="#mo2"/}}2. Explain financial terminology. ===
112	112
113	113	Avoid using financial jargon. Acronyms and pseudonyms may make sense internally, but people using your services may not understand them.
114	114
115	115
116		-=== 3. Give examples of conceptual arrangements. ===
	153	+=== {{id name="#mo3"/}}3. Give examples of conceptual arrangements. ===
117	117
118	118	A tracker or shared ownership mortgage is easier to understand if you give examples.
119	119
...	...	@@ -120,8 +120,19 @@
120	120	This is important for credit arrangements where there is an initial interest rate that may change.
121	121
122	122
123		-== Usability evidence: plain English in finance ==
	160	+=== {{id name="#UEMO"/}}Usability evidence: plain English in 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.
	165	+
	166	+
	167	+(% class="box" %)
	168	+(((
	169	+See also:
	170	+
	171	+* [[Plain English>>doc:Plain English.Plain English, simple sentences.WebHome]]
	172	+* [[Simple sentences>>url:https://readabilityguidelines.myxwiki.org/xwiki/bin/view/Plain%20English/Simple%20sentences/]]
	173	+* [[Specialist terms>>url:https://readabilityguidelines.myxwiki.org/xwiki/bin/view/Plain%20English/Plain%20English%2C%20simple%20sentences/#st]]
	174	+* [[Words to avoid>>url:https://readabilityguidelines.myxwiki.org/xwiki/bin/view/Plain%20English/Words%20to%20avoid/]]
	175	+)))