Wiki source code of Numbers

Version 12.2 by XWikiGuest on 2019/11/01 08:01

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 [[8. Spell out month in dates, write day as a numeral without "st", "nd" or "th".>>doc:||anchor="#8"]]
30
31 [[Usability evidence>>doc:||anchor="UEN"]]
32
33
34 ----
35
36 === {{id name="#1"/}}1. Use numerals instead of words for numbers. ===
37
38 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.
39
40
41 Example:
42
43 "You’ll be shown (% class="mark" %)14 clips(%%) that feature everyday road scenes.
44
45 There will be:
46
47 (% class="mark" %)1 developing hazard in 13 clips(%%)
48 (% class="mark" %)2 developing hazards in the other clip(%%)"
49
50
51 === {{id name="#2"/}}2. Choose clear typography. ===
52
53 "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.
54
55 (% class="wikigeneratedid" id="H2.Avoidusing0and1iftheycouldcauseconfusionwithletters22O22and22I22or22l22." %)
56 Avoid using 0 and 1 if they could cause confusion with letters. Make sure passcodes do not include characters that can cause letter confusion.
57
58
59 === {{id name="#3"/}}3. Be specific with data. ===
60
61 Be specific and consider the context. 20% of 10 people is very different to 20% of 100.
62
63
64 Example:
65 \\(% class="mark" %)"20 people"(%%) not "20% of the survey group"
66
67
68 Keep data as accurate as possible, 2 decimal places is recommended.
69
70 Example:
71 \\(% class="mark" %)4.03 MB
72
73 === ===
74
75 === {{id name="#4"/}}4. Use percentages. ===
76
77 Use a % sign for percentages: 50%
78
79
80 === {{id name="#5"/}}5. Use "to" for number ranges, not a hyphen. ===
81
82 Use ‘500 to 900’ and not ‘500-900’.
83
84 Addresses: use ‘to’ in address ranges: 49 to 53 Cherry Street.
85
86 === ===
87
88 === {{id name="#6"/}}6. Use years and months not just months. ===
89
90 For most audiences, writing the year followed by the month is most comprehensible.
91
92
93 Example:
94
95 (% class="mark" %)"1 year 6 months"(%%) not "18 months", "a year and a half" or "1.5 years".
96
97 Below 1 year, use months: 
98 \\(% class="mark" %)"6 months old"
99
100 ===
101 {{id name="#7"/}}7. Use a space before KB and MB ===
102
103 Use KB with a space before for anything under 1 MB. Use MB with a space before for anything over 1 MB.
104
105
106 Examples:
107
108 (% class="mark" %)569 KB(%%) not 0.55 MB
109 (% class="mark" %)4 MB(%%) not 4096 KB
110
111
112 === {{id name="#8"/}}8. Write dates without "st", "nd", "th", known as cardinals. ===
113
114 Do not use a comma to separate the year. Write the year in full. Spell out the month.
115
116
117 Example for UK:
118
119 (% class="mark" %)18 July 2019
120
121
122 Example for US:
123
124 (% class="mark" %)July 18 2019
125
126
127 ----
128
129 == {{id name="#UEN"/}}Usability evidence ==
130
131 [['The innate mind: Structure and Contents Part III > Number and natural language'>>url:https://philpapers.org/rec/LAUNAN]], 2005
132
133 [['Formatting the value of a quantity'>>url:https://www.bipm.org/en/publications/si-brochure/section5-3-3.html]], 2006
134
135 [['Show numbers as numerals when writing for online readers'>>url:https://www.nngroup.com/articles/web-writing-show-numbers-as-numerals/]], J. Nielson, 2007
136
137 [['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
138
139 [['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]],
140
141 [[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
142
143 [[GOV.UK Style guide A to Z>>https://www.gov.uk/guidance/style-guide/a-to-z-of-gov-uk-style#dates]], Dates and number ranges, UK Government, 2016
144
145 [['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. Related free access article [['Affect and decision-making: a "hot" topic'>>https://onlinelibrary.wiley.com/doi/epdf/10.1002/bdm.528]], Peters, E., D. Västfjäll, Gärling, T., Slovic, P.
146
147 [['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
148
149 [['‘‘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
150
151 [['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.
152
153 [['Case alternation impairs word identification’>>url:https://www.researchgate.net/publication/271957284_Case_alternation_impairs_word_identification]] Coltheart, M. and Freeman, R. 2013
154
155 [['Letter and symbol misrecognition in highly legible typefaces for general, children, dyslexic, visually impaired and ageing readers'>>https://typography.guru/journal/letters-symbols-misrecognition/]], Thomas Bohm, 4th edition, 2019 plus more [[typography writing and papers from User Design>>https://www.userdesignillustrationandtypesetting.com/awardsandpress/index.html]]
156
157 [['Web style guide'>>https://webstyleguide.com/9-typography.html]] Chapter 9. Typography, Typefaces section, Lynch, P. and S. Horton, 4th edition, 2016
158
159 (% class="box" %)
160 (((
161 See also:
162
163 * [[Hyphens and dashes>>doc:Punctuation and abbreviating.Hyphens and en dashes.WebHome]]
164 * [[Plain English>>doc:Plain English.Plain English, simple sentences.WebHome]]
165 )))