Changes for page Presentations
Last modified by Lizzie Bruce on 2020/01/11 23:39
To version 1.2
edited by Lizzie Bruce
on 2019/03/11 18:24
on 2019/03/11 18:24
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - Presentations1 +Mobiles and devices - Content
-
... ... @@ -8,65 +8,41 @@ 8 8 * **people with visual impairments** 9 9 ))) 10 10 11 +(% class="wikigeneratedid" %) 11 11 == == 12 12 13 13 == Guidance == 14 14 15 - 2liner summary16 +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 16 17 17 18 -[[1. Minimisetheamountofext and numberofslides.>>doc:||anchor="#1"]]19 +[[1. Design for mobile first not last.>>doc:||anchor="#1"]] 19 19 20 -[[2. A voidmultiplebulletpoints.>>doc:||anchor="#2"]]21 +[[2. Always ask “How would this look on mobile?”.>>doc:||anchor="#2"]] 21 21 22 -[[3. Includeavarietyofcommunicationmethods.>>doc:||anchor="#3"]]23 +[[3. Put calls to action close to content they relate to.>>doc:||anchor="#3"]] 23 23 24 24 [[4. Test content with people using mobiles.>>doc:||anchor="#4"]] 25 25 26 -Use good visual contrast. 27 - 28 -Use large fonts. 29 - 30 -Use alt text for images on slide decks that are distributed outside of the talk. 31 - 32 -Call out all visual elements on your slides and in the space you are presenting in. 33 - 34 -Don't over-use Gifs and animations. 35 - 36 -Consider using a live captioning service. 37 - 38 -Repeat questions from the audience 39 - 40 -Speak slowly and clearly 41 - 42 -Pause at the start of each slide, then read out the text 43 - 44 -Face your audience 45 - 46 -Use a mic. Test all audio equipment before the talk. 47 - 48 -Don't use pointers on your slides. 49 - 50 50 [[Usability evidence>>doc:||anchor="#UEMD"]] 51 51 52 52 53 53 ---- 54 54 55 -=== {{id name="#1"/}}1. Minimise the amountoftext and number ofslides. ===32 +=== {{id name="#1"/}}1. Designing for mobile first not last. === 56 56 57 -T ry summarising eachpoint you want to make in 1sentence.And make the text on each line no more than7 words: this is optimal for readability. Keepingthe text toa minimumallows audience to follow the speaker,not the slide. Whenyoucreateyour slidecontent,considerpeople who'll photographthem to refer to or shareater.34 +This can help you make your content concise and accessible. 58 58 59 -Too many slides can be distracting. On average we only remember around 20% of what we are presented with. Why make it harder? 60 60 37 +=== {{id name="#2"/}}2. Always ask yourself “How would this look on mobile?”. === 61 61 62 - ==={{id="#2"/}}2.Avoidmultiple bullet points.===39 +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. 63 63 64 -They're great for organising but bad for presenting, as it's harder to absorb and remember multiple points from a presentation slide at a time. Consider 1 image or point for each slide. 65 65 42 +=== {{id name="#3"/}}3. Put calls to action close to content they relate to. === 66 66 67 - === {{idname="#3"/}}3.Includeavarietyofcommunication styles.===44 +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. 68 68 69 -People will be more likely to absorb and remember content from your presentation if you use a range of methods, for example: visual, textual, speech. 70 70 71 71 === {{id name="#4"/}}4. Test content with people using mobiles. === 72 72 ... ... @@ -73,48 +73,19 @@ 73 73 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? 74 74 75 75 76 - 77 -Use good visual contrast 3:1 - various tools to check this. Powerpoint has tools built in. 78 - 79 -Use large fonts. Text needs to be easily read from the back of the room - 36pt minimum, use non-serif of a size larger than you might think - sit as far away from the screen and squint to test. 80 - 81 -Use alt text for slide decks that are distributed outside of the talk. Regardless, explain all images regardless of how obvious you think they are including context, reference to source material etc. Describe pertinent parts of graphics, videos, and other visuals. Describe them to the extent needed to understand the presentation. (You usually do not need to describe decorative images.). 82 - 83 -Remember when asking for people to raise their hands you need to describe the reaction.When using graphs describe the most important point which the graph demonstrates, make sure all labels are as large as possible. twice as large as you think they should be! Avoid 3D graphs - harder to read. Don't use pie charts - hard to read. 84 - 85 -Don't over-use Gifs and animations - can be distracting especially if they loop, always explain what is happening. Having explanations of video content at the ready also mitigates for them not loading or playing properly. 86 - 87 -Use captions for video content. 88 - 89 -Consider using a live captioning service for all of your spoken content. Allowing for the time it takes to translate. Auto captioning by Google or Powerpoint requires a good internet connection and is not nearly as accurate as a dedicated live caption service. 90 - 91 -Repeat questions from the audience, not everyone will hear the question, which makes the answer unintelligible. 92 - 93 -speak slowly and clearly - this helps with interpreter / lip readers / 2nd language / cognitive impairments. Your delivery will seem slower than it is if you are nervous: slow down. Sign language interpretation means that someone who needs this can only focus on one thing at a time (presenter, interpreter, or slide) and translation takes time so allow for this when referring to slides. Pause between slides - give people time to process the information. 94 - 95 -Pause at the start of each slide to allow for deaf and hard of hearing to read it. Then start by reading it for the blind or partially sighted. 96 - 97 -Face your audience, as close as possible - helps especially with lip-readers, but we all have less cognitive load when we can see the face of the person speaking. 98 - 99 -Use a mic. Some assistive tech will require it. For example: ALDs/hearing loops and remote CART writers. 100 - 101 -Take audience questions via a mic so that everyone can hear. Note that asking questions in a crowd can be intimidating and hard for many reasons like disability - consider using alternatives like Slido so people can type their questions. Avoid "Can you hear me OK?" This is not a question everyone will be comfortable replying to. 102 - 103 -Test the amplification, speakers, and mics before the talk. 104 - 105 -don't use pointers on your slides - they are distracting 106 - 107 - 108 - 109 - 110 110 ---- 111 111 112 112 == 113 113 {{id name="#UEMD"/}}Usability evidence == 114 114 115 -Sig Access Accessibile Writing Guide [[http:~~/~~/www.sigaccess.org/welcome-to-sigaccess/resources/accessible-writing-guide/>>url:http://www.sigaccess.org/welcome-to-sigaccess/resources/accessible-writing-guide/]] 57 +[[Reading on mobile>>url:https://www.nngroup.com/articles/better-mobile/]], Amy Schade, Neilson Norman Group, 2017 58 +[[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 59 +[[Do mobile technologies reshape speaking, writing, or reading?>>url:http://journals.sagepub.com/doi/full/10.1177/2050157912459739]] 60 +Naomi S. Baron, SAGE Journals, 2013 61 +[[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 62 +[['Content strategy for mobile'>>url:https://abookapart.com/products/content-strategy-for-mobile]], Karen McGrane, 2012 63 +[[How to Create Mobile Friendly Content>>url:https://neilpatel.com/blog/how-to-create-mobile-friendly-content/]], Neil Patel, undated 116 116 117 -W3C How to Make Your Presentations Accessible to All [[https:~~/~~/www.w3.org/WAI/teach-advocate/accessible-presentations/#basics-for-organizers~~-~~-speakers>>url:https://www.w3.org/WAI/teach-advocate/accessible-presentations/#basics-for-organizers--speakers]] 118 118 119 119 (% class="box" %) 120 120 ((( ... ... @@ -121,5 +121,5 @@ 121 121 See also: 122 122 123 123 * [[Plain English>>doc:Plain English.Plain English, simple sentences.WebHome]] 124 -* Simplesentences71 +* [[Calls to action and button copy>>doc:User centred design.Links.Button copy.WebHome]] 125 125 )))