Skip to Content
Last modified by Lizzie Bruce on 2020/01/11 23:49
From version Icon 1.43 Icon
edited by Lizzie Bruce
on 2019/03/09 03:18
Change comment: There is no comment for this version
To version Icon 1.40 Icon
edited by Lizzie Bruce
on 2019/03/09 02:38
Change comment: There is no comment for this version

Summary

Details

Icon Page properties
Content
... ... @@ -1,17 +1,11 @@
1 1  (% class="box" %)
2 2  (((
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
3 +Following this helps:
4 +\\
12 12  )))
13 13  
14 14  
8 +(% class="wikigeneratedid" %)
15 15  == Guidance ==
16 16  
17 17  (% class="wikigeneratedid" %)
... ... @@ -18,84 +18,46 @@
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 ===
15 +[[Law>>doc:||anchor="l"]]
22 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 -
17 +[[Medicine>>doc:||anchor="m"]]
25 25  
26 -(% class="wikigeneratedid" id="H1.Usesimplelanguageforlegalterms." %)
27 -[[1. Use simple language for legal terms.>>doc:||anchor="#l1"]]
19 +[[Money>>doc:||anchor="mo"]]
28 28  
29 -(% class="wikigeneratedid" id="H2.Explainthelawincontext." %)
30 -[[2. Explain the law in context.>>doc:||anchor="#l2"]]
21 +----
31 31  
32 -[[Usability evidence: plain English in law>>doc:||anchor="#UEL"]]
23 +== {{id name="l"/}}Law ==
33 33  
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.
34 34  
35 -=== Medicine ===
27 +Writing in plain English can make meaning clear, so that judges don’t have to rely on sometimes contradictory interpretations.
36 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 39  
40 -(% class="wikigeneratedid" id="H1.Writeclearly." %)
41 -[[1. Write clearly.>>doc:||anchor="#m1"]]
30 +=== 1. Use simple language for legal terms. ===
42 42  
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 -
72 72  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.
73 73  
74 74  
75 -=== {{id name="#l2"/}}2. Explain the law in context. ===
35 +=== 2. Explain the law in context. ===
76 76  
77 77  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.
78 78  
39 +>Example:
40 +> Positioned at the top of a form, not hidden away in references section.
79 79  
80 -Example:
81 -\\(% class="mark" %)Positioned at the top of a form, not hidden away in references section.
82 -
83 83  (((
84 84  "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)."
85 85  )))
86 86  
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]
87 87  
88 -Example:
89 -\\[Subheading]
90 -(% class="mark" %)"**Direct sales contract — exemptions from application of the Act**(%%)
91 -
92 -
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."
95 -
96 96  == ==
97 97  
98 -=== {{id name="#UEL"/}}Usability evidence: plain English in law ===
54 +== Usability evidence: plain English in law ==
99 99  
100 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".
101 101  
... ... @@ -110,19 +110,22 @@
110 110  
111 111  ----
112 112  
113 -== {{id name="m"/}}Medicine – plain English guidelines ==
69 +== {{id name="m"/}}Medicine ==
114 114  
115 -=== {{id name="#m1"/}}1. Write clearly. ===
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. 
116 116  
73 +
74 +=== 1. Write clearly. ===
75 +
117 117  Users of the information might be in shock or anxious, which reduces cognition.
118 118  
119 119  
120 -=== {{id name="#m2"/}} 2. Explain medical terms. ===
79 +=== 2. Explain medical terms. ===
121 121  
122 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.
123 123  
124 124  
125 -=== {{id name="#UM"/}}Usability evidence: plain English in medicine ===
84 +== Usability evidence: plain English in medicine ==
126 126  
127 127  [[Guide to medical information>>http://www.plainenglish.co.uk/files/medicalguide.pdf]] from Plain English Campaign.
128 128  
... ... @@ -139,19 +139,22 @@
139 139  
140 140  == ==
141 141  
142 -== {{id name="mo"/}}Money – plain English guidelines ==
101 +== {{id name="mo"/}}Money ==
143 143  
144 -=== {{id name="#mo1"/}}1. Use clear language. ===
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.
145 145  
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.
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.
147 147  \\
148 148  
149 -=== {{id name="#mo2"/}}2. Explain financial terminology. ===
111 +=== 2. Explain terminology. ===
150 150  
151 151  Avoid using financial jargon. Acronyms and pseudonyms may make sense internally, but people using your services may not understand them.
152 152  
153 153  
154 -=== {{id name="#mo3"/}}3. Give examples of conceptual arrangements. ===
116 +=== 3. Give examples of conceptual arrangements. ===
155 155  
156 156  A tracker or shared ownership mortgage is easier to understand if you give examples.
157 157  
... ... @@ -158,7 +158,7 @@
158 158  This is important for credit arrangements where there is an initial interest rate that may change.
159 159  
160 160  
161 -=== {{id name="#UEMO"/}}Usability evidence: plain English in finance ===
123 +== Usability evidence: plain English in finance ==
162 162  
163 163  [[A to Z of financial terms (PDF 87KB)>>http://www.plainenglish.co.uk/files/financialguide.pdf]] from Plain English Campaign.
164 164