Skip to Content

Changes for page Presentations

Last modified by Lizzie Bruce on 2020/01/11 23:39
From version Icon 2.1 Icon
edited by Cass Bonner
on 2019/04/11 13:55
Change comment: Minor change to title following feedback
To version Icon 15.1
edited by Lizzie Bruce
on 2020/01/11 23:39
Change comment: on page redirect

Summary

Details

Icon Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Mobiles and tablets
1 +Presentations
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CassBonner
1 +xwiki:XWiki.LizzieBruce
Content
... ... @@ -1,71 +1,1 @@
1 -(% class="box" %)
2 -(((
3 -Following this helps:
4 -
5 -* **people using mobiles **
6 -* **people using tablets**
7 -* **people using laptops and desktop computers**
8 -* **people with visual impairments**
9 -)))
10 -
11 -== ==
12 -
13 -== Guidance ==
14 -
15 -Accessing content on a mobile device exaggerates many readability issues due to the small screen size. Improving content presentation and interaction for mobile use will generally improve its usability across all devices.
16 -
17 -
18 -[[1. Design for mobile first not last.>>doc:||anchor="#1"]]
19 -
20 -[[2. Always ask “How would this look on mobile?”.>>doc:||anchor="#2"]]
21 -
22 -[[3. Put calls to action close to content they relate to.>>doc:||anchor="#3"]]
23 -
24 -[[4. Test content with people using mobiles.>>doc:||anchor="#4"]]
25 -
26 -[[Usability evidence>>doc:||anchor="#UEMD"]]
27 -
28 -
29 -----
30 -
31 -=== {{id name="#1"/}}1. Designing for mobile first not last. ===
32 -
33 -This can help you make your content concise and accessible.
34 -
35 -
36 -=== {{id name="#2"/}}2. Always ask yourself “How would this look on mobile?”. ===
37 -
38 -If you are considering for example how long a paragraph is, think about how much longer it would be on a mobile. That might help you decide whether it should be split into 2 paragraphs.
39 -
40 -
41 -=== {{id name="#3"/}}3. Put calls to action close to content they relate to. ===
42 -
43 -This saves users from scrolling across and down or searching around for the link and getting lost or frustrated. It also helps users who have a small area of visual focus.
44 -
45 -
46 -=== {{id name="#4"/}}4. Test content with people using mobiles. ===
47 -
48 -Find out how they interpret and interact with the content. Did you write something that can be understood in different ways? Did anyone use their mobile in ways you did not expect?
49 -
50 -
51 -----
52 -
53 -==
54 -{{id name="#UEMD"/}}Usability evidence ==
55 -
56 -[[Reading on mobile>>url:https://www.nngroup.com/articles/better-mobile/]], Amy Schade, Neilson Norman Group, 2017
57 -[[Mobile first is not mobile only>>url:https://www.nngroup.com/articles/mobile-first-not-mobile-only/]], Raluca Budiu and Kara Pernice, Neilson Norman Group, 2016
58 -[[Do mobile technologies reshape speaking, writing, or reading?>>url:http://journals.sagepub.com/doi/full/10.1177/2050157912459739]]
59 -Naomi S. Baron, SAGE Journals, 2013
60 -[[Mobile App Design Fundamentals: 10 Tips for an Effective Content Strategy>>url:https://clearbridgemobile.com/mobile-app-design-fundamentals-10-tips-for-an-effective-content-strategy/]], Britt Armour, 2017
61 -[['Content strategy for mobile'>>url:https://abookapart.com/products/content-strategy-for-mobile]], Karen McGrane, 2012
62 -[[How to Create Mobile Friendly Content>>url:https://neilpatel.com/blog/how-to-create-mobile-friendly-content/]], Neil Patel, undated
63 -
64 -
65 -(% class="box" %)
66 -(((
67 -See also:
68 -
69 -* [[Plain English>>doc:Plain English.Plain English, simple sentences.WebHome]]
70 -* [[Calls to action and button copy>>doc:User centred design.Links.Button copy.WebHome]]
71 -)))
1 +Please go to [[readabilityguidelines.co.uk/audiences-devices-channels/presentations>>url:https://readabilityguidelines.co.uk/audiences-devices-channels/presentations/]].