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

Summary

Details

Icon Page properties
Content
... ... @@ -1,39 +1,101 @@
1 +(% class="box" %)
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
12 +)))
13 +
14 +
15 +== Guidance ==
16 +
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.
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 +
3 3  
21 +=== Law ===
4 4  
5 -== {{id name="l"/}}Law ==
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 +
6 6  
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.
26 +(% class="wikigeneratedid" id="H1.Usesimplelanguageforlegalterms." %)
27 +[[1. Use simple language for legal terms.>>doc:||anchor="#l1"]]
8 8  
9 -Writing in plain English can make meaning clear, so that judges don’t have to rely on sometimes contradictory interpretations.
29 +(% class="wikigeneratedid" id="H2.Explainthelawincontext." %)
30 +[[2. Explain the law in context.>>doc:||anchor="#l2"]]
10 10  
32 +[[Usability evidence: plain English in law>>doc:||anchor="#UEL"]]
11 11  
12 -=== 1. Use simple language for legal terms. ===
13 13  
35 +=== Medicine ===
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 +
40 +(% class="wikigeneratedid" id="H1.Writeclearly." %)
41 +[[1. Write clearly.>>doc:||anchor="#m1"]]
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 +
14 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.
15 15  
16 16  
17 -=== 2. Explain the law in context. ===
75 +=== {{id name="#l2"/}}2. Explain the law in context. ===
18 18  
19 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 20  
21 ->Example:
22 -> Positioned at the top of a form, not hidden away in references section.
23 23  
80 +Example:
81 +\\(% class="mark" %)Positioned at the top of a form, not hidden away in references section.
82 +
24 24  (((
25 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 26  )))
27 27  
28 ->Example:
29 ->
30 ->"**Direct sales contract — exemptions from application of the Act**"  [Subheading]
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 33  
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 +
34 34  == ==
35 35  
36 -== Usability evidence: plain English in law ==
98 +=== {{id name="#UEL"/}}Usability evidence: 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  
... ... @@ -48,22 +48,19 @@
48 48  
49 49  ----
50 50  
51 -== {{id name="m"/}}Medicine ==
113 +== {{id name="m"/}}Medicine – plain English guidelines ==
52 52  
53 -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. 
115 +=== {{id name="#m1"/}}1. Write clearly. ===
54 54  
55 -
56 -=== 1. Write clearly. ===
57 -
58 58  Users of the information might be in shock or anxious, which reduces cognition.
59 59  
60 60  
61 -=== 2. Explain medical terms. ===
120 +=== {{id name="#m2"/}} 2. Explain medical terms. ===
62 62  
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 ==
125 +=== {{id name="#UM"/}}Usability evidence: plain English in medicine ===
67 67  
68 68  [[Guide to medical information>>http://www.plainenglish.co.uk/files/medicalguide.pdf]] from Plain English Campaign.
69 69  
... ... @@ -78,25 +78,21 @@
78 78  
79 79  ----
80 80  
81 -(% class="wikigeneratedid" %)
82 82  == ==
83 83  
84 -== {{id name="mo"/}}Money ==
142 +== {{id name="mo"/}}Money – plain English guidelines ==
85 85  
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.
144 +=== {{id name="#mo1"/}}1. Use clear language. ===
87 87  
88 -
89 -=== 1. Use clear language. ===
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.
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.
92 92  \\
93 93  
94 -=== 2. Explain terminology. ===
149 +=== {{id name="#mo2"/}}2. Explain financial terminology. ===
95 95  
96 96  Avoid using financial jargon. Acronyms and pseudonyms may make sense internally, but people using your services may not understand them.
97 97  
98 98  
99 -=== 3. Give examples of conceptual arrangements. ===
154 +=== {{id name="#mo3"/}}3. Give examples of conceptual arrangements. ===
100 100  
101 101  A tracker or shared ownership mortgage is easier to understand if you give examples.
102 102  
... ... @@ -103,7 +103,7 @@
103 103  This is important for credit arrangements where there is an initial interest rate that may change.
104 104  
105 105  
106 -== Usability evidence: plain English in finance ==
161 +=== {{id name="#UEMO"/}}Usability evidence: plain English in finance ===
107 107  
108 108  [[A to Z of financial terms (PDF 87KB)>>http://www.plainenglish.co.uk/files/financialguide.pdf]] from Plain English Campaign.
109 109