Wiki source code of Numbers

Version 7.1 by Lizzie Bruce on 2019/05/22 10:39
Show last authors
1 (% class="box" %)
2 (((
3 Following this helps:
4
5 * **people in a hurry** – clear, specific data and numbers are quicker to scan and comprehend.
6 * **people who are stressed** – not having to decipher fractions makes content easier to absorb.
7 * **people who are multi-tasking** – if your attention's divided clear, specific data is more helpful.
8 * **cognitive impairments** – easy to understand figures carry less cognitive load
9 * **visual impairments** – numerals are easy to spot in a smaller visual focus field
10 )))
11
12 ==
13 Guidance ==
14
15 [[1. Use numerals instead of words for numbers.>>doc:||anchor="#1"]]
16
17 [[2. Choose clear typography.>>doc:||anchor="#2"]]
18
19 [[3. Be specific with data.>>doc:||anchor="#3"]]
20
21 [[4. Use percentages.>>doc:||anchor="#4"]]
22
23 [[5. Use "to" for number ranges, not a hyphen.>>doc:||anchor="#5"]]
24
25 [[6. Use years and months not just months.>>doc:||anchor="#6"]]
26
27 [[7. Use a space before KB and MB.>>doc:||anchor="#7"]]
28
29 [[Usability evidence>>doc:||anchor="UEN"]]
30
31
32 ----
33
34 === {{id name="#1"/}}1. Use numerals instead of words for numbers. ===
35
36 They are easier to scan read. It's more consistent to always use numerals rather than have a variety of rules for different sentence structures.
37
38
39 Example:
40
41 "You’ll be shown (% class="mark" %)14 clips(%%) that feature everyday road scenes.
42
43 There will be:
44
45 (% class="mark" %)1 developing hazard in 13 clips(%%)
46 (% class="mark" %)2 developing hazards in the other clip(%%)"
47
48
49 === {{id name="#2"/}}2. Choose clear typography. ===
50
51 "1" and "I" can look the same depending on the typeface, as can "0 and "O", so choose a typeface where these characters look sufficiently different and unique. Test with users if you're not sure.
52
53 (% class="wikigeneratedid" id="H2.Avoidusing0and1iftheycouldcauseconfusionwithletters22O22and22I22or22l22." %)
54 Avoid using 0 and 1 if they could cause confusion with letters. Make sure passcodes do not include characters that can cause letter confusion.
55
56
57 === {{id name="#3"/}}3. Be specific with data. ===
58
59 Be specific and consider the context. 20% of 10 people is very different to 20% of 100.
60
61
62 Example:
63 \\(% class="mark" %)"20 people"(%%) not "20% of the survey group"
64
65
66 Keep data as accurate as possible, 2 decimal places is recommended.
67
68 Example:
69 \\(% class="mark" %)4.03 MB
70
71 === ===
72
73 === {{id name="#4"/}}4. Use percentages. ===
74
75 Use a % sign for percentages: 50%
76
77
78 === {{id name="#5"/}}5. Use "to" for number ranges, not a hyphen. ===
79
80 Use ‘500 to 900’ and not ‘500-900’.
81
82 Addresses: use ‘to’ in address ranges: 49 to 53 Cherry Street.
83
84 === ===
85
86 === {{id name="#6"/}}6. Use years and months not just months. ===
87
88 For most audiences, writing the year followed by the month is most comprehensible.
89
90
91 Example:
92
93 (% class="mark" %)"1 year 6 months"(%%) not "18 months", "a year and a half" or "1.5 years".
94
95 Below 1 year, use months: 
96 \\(% class="mark" %)"6 months old"
97
98 ===
99 {{id name="#7"/}}7. Use a space before KB and MB ===
100
101 Use KB with a space before for anything under 1 MB. Use MB with a space before for anything over 1 MB.
102
103
104 Examples:
105
106 (% class="mark" %)569 KB(%%) not 0.55 MB
107 (% class="mark" %)4 MB(%%) not 4096 KB
108
109
110 ----
111
112 == {{id name="#UEN"/}}Usability evidence ==
113
114 [['The innate mind: Structure and Contents Part III > Number and natural language'>>url:https://philpapers.org/rec/LAUNAN]], 2005
115
116 [['Formatting the value of a quantity'>>url:https://www.bipm.org/en/publications/si-brochure/section5-3-3.html]], 2006
117
118 [['Show numbers as numerals when writing for online readers'>>url:https://www.nngroup.com/articles/web-writing-show-numbers-as-numerals/]], J. Nielson, 2007
119
120 [['Knowledge of number and knowledge of language: Number as a test case for the role of language in cognition'>>url:https://philpapers.org/rec/DECKON]],** **De Cruz, H. and Pica, P., 2008. Locked
121
122 [['Low levels of numeracy are a long-term problem for the UK'>>http://www.nationalnumeracy.org.uk/news/16/index.html]], National Numeracy update, National Numeracy YouGov Survey 2014, data sources: [[Skills for Life 2011>>url:https://www.nationalnumeracy.org.uk/research-skills-life-survey-2011]], [[PIAAC 2014>>url:https://www.nationalnumeracy.org.uk/research-programme-international-student-assessment-2014]],
123
124 [[GOV.UK Content principles>>url:https://www.gov.uk/government/publications/govuk-content-principles-conventions-and-research-background/govuk-content-principles-conventions-and-research-background]], UK Government, 2016
125
126 [[GOV.UK Style guide A to Z>>url:https://www.gov.uk/guidance/style-guide/a-to-z-of-gov-uk-style]], UK Government, 2016
127
128 [['Numeracy and decision making’>>https://journals.sagepub.com/doi/abs/10.1111/j.1467-9280.2006.01720.x]], Peters, E., D. Västfjäll, et al., Psychological Science, 17(5), pp. 407 to 413. 2006. Locked.
129
130 [['Less is more in presenting quality information to consumers'>>http://library.mpib-berlin.mpg.de/ft/gg/GG_30_Chance_2005.pdf]], Peters, E., N. Dieckmann, et al, Medical Care Research and Review, 64 (2), pp.169 to 190. 2007
131
132 [['‘‘A 30% chance of rain tomorrow’’: How does the public understand probabilistic weather forecasts?'>>http://library.mpib-berlin.mpg.de/ft/gg/GG_30_Chance_2005.pdf]], Gigerenzer, G., Hertwig, R., van den Broek, E., Fasolo, B., & Katsikopoulos, K.V., Risk Analysis, 25, 623 to 629, 2006
133
134 [[‘The Effect of Type Size and Case Alternation on Word Identification’>>url:https://www.jstor.org/stable/1421250?seq=1#page_scan_tab_contents]], Smith, Lott and Cronnell, 1969. Semi-locked: free to access online with MyJSTOR account.
135
136 [[‘Case alternation impairs word identification’>>url:https://www.researchgate.net/publication/271957284_Case_alternation_impairs_word_identification]] Coltheart, M. and Freeman, R. 2013
137
138 [['Can you tell your 1 from your l? Why letter legibility is key in type design'>>https://www.designweek.co.uk/issues/7-13-december-2015/can-you-tell-your-1-from-your-l-why-letter-legibility-is-key-in-type-design/]], Design Week analysis of [[Thomas Bohm’s>>https://www.userdesignillustrationandtypesetting.com]] report on typographical usability. 
139
140
141 (% class="box" %)
142 (((
143 See also:
144
145 * [[Hyphens and dashes>>doc:Punctuation and abbreviating.Hyphens and en dashes.WebHome]]
146 * [[Plain English>>doc:Plain English.Plain English, simple sentences.WebHome]]
147 )))