Bummer! This is just a preview. You need to be signed in with a Pro account to view the entire video.
Accessibility is a Design Tool29:31 with Derek Featherstone
Designing for extreme use cases—outliers—results in a design process that leads to greater success in developing products that are more easily used by everyone. By systematically factoring these extremes into our designs we spark creativity and behaviours that encourage divergent thinking and help to ensure that what we create can be used by everyone, including people with disabilities.
[MUSIC] 0:00 I wanna talk with you today about using accessibility as a design tool. 0:04 We've done a lot of work in the last 15 years which makes me feel 0:09 really old, that leads me to believe 0:14 that accessibility is a design tool that we need to add 0:20 to our, to our arsenal when we're taking on any project. 0:23 I work at a small company called Simply Accessible this is what 0:27 we do we focus on accessibility for people with disabilities all the time. 0:30 And we've had kind of the privilege of working on projects where 0:35 we're not only doing UX work and usability work but also accessibility work. 0:38 And we've seen a lot of things happen where we've made changes 0:44 for people with disabilities that have 0:49 just made things better for everybody else. 0:51 and, and seeing that over and over and over again as 0:53 kind of lead us to believe that there's, that there's something there. 0:57 Something that we need as designer's and developer's to kind of grab, grab hold of. 1:01 So this is me, I'm feather on Twitter. 1:05 If you wanna connect you know, feel free to, to reach out to me there. 1:08 If you wanna email me, feel free. 1:12 Feather@simplyaccessible.com. 1:14 Totally fine. 1:16 you, you can email me, preferably animated gifts would be 1:18 good if you wanna send those over, cuz I like those. 1:22 we, we do a lot of design workshops and this 1:27 is, does anybody recognize what this is on the screen? 1:30 This is like the original Microsoft surface. 1:36 The table. 1:39 Like not the little surfaces that they have now, but 1:40 it was like the four foot by three foot table. 1:42 And when I, when I first I saw this for 1:44 the first time klike in 2007 at a conference room it's 1:49 kind of unveiled and I was, was all over it like, 1:53 I wanna, I wanna talk about the accessibility of this device. 1:56 Is it accessible? 2:01 What could we do? 2:02 How could this device actually make things more accessible for for people 2:03 with disabilities and, and we started to look at this, this photo app. 2:07 And I use this as a, an exercise and a lot of our full-day workshops 2:12 where we basically unpack this photo app from 2:16 an accessibility perspective, and we look at all 2:19 kinds of different disabilities, and we come 2:20 up with all kinds of different challenges that 2:23 people face when they are, when they are 2:25 using this app depending on their disability so. 2:26 One of them for example, is, is for somebody 2:29 that has low vision, they're not, they're not blind, 2:33 they can still see but when they look at 2:35 this, one of the, the problems that they might have 2:37 is that they would have trouble distinguishing one photo 2:40 from the next, particularly in a, in a pile 2:43 like this where there's not really you know, you've 2:46 got a, a small, thin, white border around each photo. 2:49 For somebody with low vision, that may 2:53 be really difficult to, to distinguish between 2:54 the border of one photo and where on photo finishes and the other starts. 2:56 For somebody that has a, a cognitive 3:01 difficulty that, that, they require and, and 3:04 I do mean require, they require a certain amount of order in the interface. 3:07 This view may be may be enough to actually stop somebody with particular type 3:11 of say, autism, where they fit somewhere on the autis, on the autism spectrum. 3:17 This, this clutter in the interface might be 3:21 enough to actually stop them from using the app. 3:24 So they maybe need something where they have a mode where 3:27 they can tap on the sur, on the surface and then say, 3:30 you know, lock this down to a grid so that everything 3:33 becomes a grid, much more orderly, and easy for them to understand. 3:36 So we go through activities like this, and we 3:40 try to put ourselves in the shoes of, of 3:42 different people with different disabilities and what usually happens 3:44 is we go through all of these different ideas. 3:48 So we talk about what are the challenges for somebody that, that is blind, 3:50 or that has low vision or has 3:53 hearing difficulties maybe even mobility and dexterity impairment. 3:56 So somebody may have real challenges with fine motor control. 4:00 That might be very difficult for them, to have 4:03 a steady hand, as they're trying to manipulate that interface. 4:06 To, to, to take a, a photo, and I don't know if 4:09 you, you saw them, but each one of those photos is, is zoomable. 4:12 It was one of the original kind of pinch zoom type interfaces. 4:15 For somebody that has only one hand, that pinch 4:20 zoom is gonna be tough to do, especially on 4:23 a large table when you've got a photo that 4:25 is, you know, maybe already eight inches by ten inches. 4:27 So for them to grab the corners and, and zoom it, if 4:31 they've only got one hand, that's going to be a challenge for them. 4:34 And so we go through all of these, these different things and, and try to 4:36 come up with as many issues as we can, things that are gonna challenge people. 4:41 On the cognitive side, right, what, what, what 4:45 about people that have attention attention deficits or 4:48 memory related issues or literacy related issues, or 4:51 even people that require that routine and predictability. 4:54 So we look at all of these vestibular disorders. 4:58 Have you, have you ever heard of vestibular disorders. 5:00 Does anybody know somebody that has, I can't even see, so you can pretend to 5:03 put up your hand and it's totally fine cuz the light is like right on me. 5:06 Does anybody know anybody that has a vestibular disorder? 5:10 The, people are kind of, just kind of 5:13 getting into this now and understanding what happens, a 5:15 vestibular disorder is where mot, it's, it's kind of 5:18 like constant motion sickness where or a constant vertigo. 5:22 When looking at a webpage, actually brings on 5:27 this feeling of, of nausea, and, and even migraines 5:31 or, or all kinds of other side effects, 5:36 dizziness, vertigo, whatever, whatever you wanna call it and 5:38 it actually limits the amount of work that 5:41 people can do, so you know that fancy parallax 5:43 effect that you can create, that motion can 5:45 actually cause people to kind of physically become ill. 5:49 And so what is the impact of that on on that interface? 5:53 On that surface table, for example if you had those photos, 5:57 and you had the ability to create a rotating slide show. 6:00 Would something like that trigger some kind 6:03 of issues for somebody with a vestibular disorder? 6:06 So we think about these kinds of things all the time. 6:08 We think about what the impact of, of that interface 6:11 is on somebody with speech difficulties, and we're seeing more and 6:14 more prevalence of, of speech, of, of speech recognition 6:17 in interfaces, what does that mean for somebody that has a statter? 6:23 What does it mean for somebody that doesn't 6:27 speak that, that English isn't their first language? 6:29 What does that mean for somebody who has cerebral 6:32 palsy, and has difficulty speaking in the first place. 6:34 All right. 6:38 And so what do we do with, with that type of scenario? 6:38 How do we design for that? 6:43 So we usually come up with a, a whole list of a whole 6:45 list of issues, and I'm not gonna go through every one of them. 6:49 But we usually break them down. 6:51 And people are, this is what I love is, is designers and developers are, are smart. 6:53 All right, we can, we can project all of these things. 6:58 We can put ourselves into the, the shoes of somebody with a disability. 7:00 Even if it's, it may be accurate, it may be inaccurate. 7:04 But that exercise of kinda getting outside of ourselves and, and 7:07 stepping into the shoes of somebody else, yields pretty awesome results. 7:11 And almost every single time I do one of 7:16 these design workshops, whether it's a surface table, or 7:19 it's a website, or it's something, anything else, we 7:22 almost always end up with a quote like this. 7:25 Somebody at the end of the workshop says, you 7:29 know, this, this stuff is great and yes, everything that 7:30 we've done and that you've showed us makes this 7:32 more accessible but you actually just created a better design. 7:35 Right, it was just better, more well thought out design in the first place. 7:38 And this is, this is why I kind of get excited about this type of topic, right? 7:42 How do we use accessibility, to make things better? 7:47 and, and I am all for you you know, a lot of, a 7:52 lot of clients mandate accessibility now and it's it's must have for a project. 7:55 I am all for you saying well it needs to be accessible. 8:01 Use that as much as you can to just make the design better for everybody. 8:05 All right, take that, leverage it. 8:09 Oh, I said that leverage word. 8:11 but, but, use, use accessibility to your 8:14 advantage to improve your design for everyone. 8:16 this, this phenomenon kind of interests me all the 8:21 time, we have it's why I have a biology background. 8:24 I was a biologists and, and I got, got into teaching 8:26 high school biology, chemistry and computers before I got into the web. 8:32 And this idea, this is a pretty 8:36 typical distribution of a characteristic within a population. 8:38 So in any population, we have all range. 8:43 And this, this is just sort of looking at size. 8:46 So you have somebody that's, that's smaller or shorter. 8:49 That's where I fit. 8:52 And, and somebody that's taller and larger and then 8:54 you have a big cluster of people in the middle. 8:56 But we have these, we have these streams, right? 8:58 And then we have a, a cluster in the middle. 9:01 And we look at, at characteristics that way, not 9:05 in terms of, of just physical size, but if you 9:08 look at this in terms of any any ability 9:11 it kind of illuminates things in a slightly different way. 9:14 There's a great video that, that I, I like to 9:18 watch every once in a while, cuz I'm weird that way. 9:22 but, IDEO, is a, a design company here in the U.S.. 9:27 And they have this video it was a special on ABC and it's called The Deep Dive. 9:31 And if you haven't watched it, I, I encourage 9:34 you to watch it just search for The Deep Dive. 9:37 And I love it because they go through and they talk about the design process and 9:41 what they do and how they, they kind of do research on an idea, 9:45 and so what they were looking to do was to design a better shopping cart. 9:51 And not like a digital e-commerce shopping 9:56 cart, an actual physical, I'm going into the 9:59 supermarket to get groceries shopping cart and as 10:01 they were doing that they started to unpack. 10:04 Well how do people use shopping carts? 10:07 They use it to carry their kids, they use it to put their purse in, 10:08 they use it to load groceries up, to unload groceries, to transport to the car. 10:12 And there're, there're all kinds of different scenarios 10:17 that, that they go through and one of the 10:20 things, and, and I hate this but you know, 10:22 traditional shopping carts you get all [COUGH] excuse me, 10:27 get all your food in there, you unload it, you load it back all in and you 10:31 can't find the things that are kind of on 10:34 the bottom and you end up squashing your bread. 10:38 You ever get squished bread? 10:40 That's not, that's not good for anybody, right? 10:41 So what they did, as part of this, 10:43 is they, around the outside of the shopping cart 10:45 they set it up so that there were hooks all around the top of the shopping cart so 10:48 that you could hang your bags so you didn't have to, like, pile bag on top of 10:52 another bag on top of another bag, cuz they 10:56 were trying to save people from squashing their bread. 10:58 So they created it so they hung it around the outside. 11:01 It was actually really kind of interesting. 11:04 One of the, one of the best quotes from the video was, was this, I love this idea. 11:06 By examining the extreme ends of a set of 11:12 phenomena in depth, the entire universe of relationships can 11:14 be illuminated since other instances fall somewhere between on 11:17 the maps on the map of relations and links. 11:21 If we look at the extremes, everybody else is kind of gonna 11:25 be somewhere in the middle, when I think of that binomial distribution. 11:29 Somebody that has no vision, somebody that has normal vision, 11:32 or super vision, cuz it could happen, in my mind anyway. 11:38 Everybody is going to have vision that falls somewhere in 11:44 between no vision and supervision, no hearing and perfect hearing. 11:47 And no, no, dexterity and or very little dexterity and perfect dexterity. 11:53 And so we started to look at, at, this and trying to understand that from an 12:00 accessibility perspective and how we can project these needs onto a design. 12:05 So we have you know, traditionally most people 12:12 have kind of thought of accessibility as this 12:14 black or white thing, like you have an 12:16 accessible site or you don't have an accessible site. 12:18 Someone is blind or they're not blind, but that's, 12:20 that's really not true, it's not black or white. 12:22 We have all, all kinds of shades of gray. 12:24 In between and how you look at that kind of frames 12:27 everything that you're going to learn and, and do about accessibility. 12:30 So let's look at accessibility as a, as a design tool. 12:35 And I've got, kind of, seven uh,different lessons here that I wanna share with you. 12:39 And these are things that are from real 12:44 projects, things we have learned over the years. 12:46 Of how putting accessibility into the design process and 12:49 specific accessibility needs actually helps make things better for everybody. 12:54 So the first is, is to start with content 12:59 and everybody wants their thing to be first, right? 13:02 Content first, Mobile first everything needs to be first at some point. 13:06 We have to think about all these things up front. 13:11 I wanna give you a, a really quick example. 13:13 This is a, a listing of healthcare providers, we were doing 13:17 work with, with a client that's a health care insurance provider. 13:21 And they basically created this, this list, so it was a very straightforward 13:25 search for healthcare providers within, you know, five miles of this zip code. 13:31 And, they get this, they get this list, and 13:36 this could all be made perfectly accessible from a 13:39 technical perspective but when we started working with him 13:41 on this, I asked him the question, I said 13:45 you know, have you considered that in the decision 13:47 making process for someone when they're looking at this 13:51 and trying to decide which person, which healthcare provider 13:54 to go to that it's not just about distance? 13:57 And they said, well, you know, what do you, what do you mean? 13:59 And I said, for, for somebody with a disability, 14:02 they may actually travel five miles farther or ten 14:04 miles farther, 30 miles farther because they're going to 14:06 see a particular specialist that is really relevant to them. 14:10 Or the may actually travel farther not just because of, 14:15 of needing to see a specialist, but because the, the 14:18 wheelchair ramp is right at the front of the building 14:21 instead of all the way around the side of the building. 14:24 Right? 14:26 That kind of stuff matters when you're, 14:27 when someone with a disability is choosing a, 14:28 a healthcare provider, and so we talked about that as a, as a content need. 14:31 Right? 14:36 What content need, what content needs are there for people with disabilities? 14:36 Do they have specific pieces of content that they actually need to, to make 14:40 decisions and to, to move forward and to be able to choose a healthcare provider? 14:46 And so we look for, look for things like that all the time. 14:51 Are there things that people with disabilities need? 14:55 They need the same content as everybody else, but 14:59 they also need content that is specific to them. 15:02 So your job as a designer really is to go and find out what that content is. 15:05 All right for, for somebody if you're working on a, a 15:09 site that is all about movies for example, when somebody with a 15:13 disability wants to go to a movie, they need to find 15:16 out information like, you know, are there captions for this movie available? 15:20 Right? 15:23 What kind of a captioning device is it? 15:24 I was at the movies the other day with, 15:26 with my ten year old son, and right beside us 15:29 was a guy who had basically a caption viewer 15:33 it went into the little drink cup, that was there, 15:35 it plugged in there essentially, and it was like 15:37 this goose neck arm type thing, and it brought a 15:39 little caption display up right in front of him, 15:41 so he didn't need to go into a specific theater. 15:44 It was actually set up for him that he could go 15:46 into any theater in that complex and see any movie, right? 15:48 . 15:52 That's not the case everywhere. 15:52 So for, for that type of scenario, some people might need 15:54 to know, hey, do I, is there captions available for this? 15:57 What kind of device is it? 15:59 Can I do, can I, am I gonna get any value out of this at all? 16:01 We also wanna move from what to why. 16:07 We often think about what we're building, but 16:11 we often forget about why we're building it. 16:13 This was a, a site, and this is a fictionalized example, but we were 16:15 working with a client where, where they 16:20 were basically showing kind of a boundary change. 16:22 So this is the, the City of Ottawa. 16:25 This is where I'm from. 16:26 And you can see there's kind of a purple polygon and a blue 16:28 polygon, and ultimately what they were doing was they wanted to show how 16:31 what, what a change in boundary was going to be, so they visualized 16:37 this on a map, because everyone wants maps on their site, because they can. 16:40 And so when they looked at this they 16:45 actually started thinking about accessibility, and they said, well 16:48 how do we, well how do we make this 16:50 accessible to somebody who can't see, those, those boundaries? 16:52 Right? 16:56 What do we, what do we do for them? 16:56 And so, the, the accessibility need was that we needed 16:58 non-visual access, for for what was being represented with those polygons. 17:01 And so they, they started coming up with different ideas. 17:07 They said things like, oh every polygon there is 17:10 really just a set of latitude and longitude coordinates. 17:13 Right? 17:16 So we can provide that as, as data. 17:16 as, as feed, somebody could take that and put it into another tool. 17:19 They looked at it and said, well we 17:23 could use just some text to describe the boundaries. 17:24 So it would, it would be something along [COUGH], along the lines of 17:28 the current city of Ottawa is bounded to the north by the Ottawa River it extends 17:33 to the west to Armprior where it, you know, the border for 17:38 the city, moves, ten, you know, five miles south, southwest. 17:43 And then heads, south, east, for 50 miles, or, or, whatever it is. 17:49 And they were coming up with these textual descriptions. 17:55 And then, they said they would describe, the pre, you 17:58 know, so here's the current one, here's the proposed one. 18:00 And they would go through all these, textual. 18:02 Base descriptions, they, cuz they know they need to provide 18:04 non-visual access to this, so how do they do it? 18:07 They came up with other things like they, they said well maybe we don't need 18:10 to describe the individual polygons, but maybe 18:14 what we need to describe is the difference. 18:17 Right? 18:19 Maybe it's about the difference, so, the, it's a, 18:20 it would be easier for them to say, the new 18:23 proposed boundary would extend the cities boundary from and a, 18:25 on the southeast side by ten, by ten miles or 18:29 something like that, and on the southeast side by 18:33 five miles, or whatever it was and they get, go 18:35 through all these different iterations of trying to figure out 18:37 how to provide nonvisual access to this very visual interface. 18:40 And so I've asked them, I said, so why is this map on the site in the first place? 18:47 Why does this, why does this matter? 18:53 They were, they were really focused on, we need to 18:55 have a map, and we need to have an accessible map. 18:57 So how are we gonna do that? 19:00 And I asked them, I said, why are people, why are people even gonna look at this? 19:01 Why does this matter? 19:05 Why does, why does a proposed city boundary change matter to anybody? 19:07 Number one reason, you know this. 19:13 Is one of the two certain things in life. 19:16 >> Taxes. 19:17 >> Right. 19:19 It's all about taxes, right? 19:20 The main reason that people want to know boundary changes 19:22 whether or not it's gonna have an impact on their taxes. 19:25 There may be other reasons, but that's a big one. 19:27 And so, what they really are after is, does this affect me? 19:31 Right? 19:35 Knowing whether or not this affects them is the reason for this map to be on there. 19:37 So, when we got to that reason, when we said well why, right? 19:42 Why is this map even there in the first place, they came 19:46 up with a completely different solution, and it was just something like this. 19:49 Right? 19:53 Instead of worrying about providing 100% 19:53 full nonvisual access to those overlapping polygons. 19:56 Because they knew why they were trying to provide it, they changed the solution. 20:00 They just said, then why don't we do a little postal code lookup? 20:04 Then you know right away. 20:07 Does this impact you? 20:08 Yes, you're inside the new boundary of the 20:10 city of Ottawa, congratulations your taxes will go up. 20:11 I mean you will get much more service for the, [COUGH]. 20:14 They changed it, because they knew why. 20:22 All right, they knew why they were putting this on there in the first place. 20:24 And so instead of focusing on a visual description of 20:27 what they were showing visually, they were giving people, the number 20:30 one reason people were coming there was to figure out 20:35 if it actually impacted them, so they created a new way. 20:37 They allowed people multiple methods for getting the same information. 20:40 That's a, a critical, critical piece for accessibility, is 20:43 not relying on just one method to get something done. 20:47 We have a goal, let's find multiple ways of, of achieving the same thing. 20:50 So when you, when you, when you move from what to 20:55 why, you allow people to solve the same problem in multiple ways. 20:58 Right? 21:02 That's a critical piece for accessibility. 21:03 We have a Podcast, and we thought we were doing a great job. 21:05 We were providing the transcript right away so we never 21:10 launched an episode of the Podcast without the transcript going live 21:13 like right then and there, so that people with hearing 21:16 difficulties, they get information at the same time as everyone else. 21:20 And one of our one of our listeners kinda said hey, you know, I'm, I'm 21:24 deaf, it would be really, really helpful for 21:28 me to have a downloadable copy of this. 21:31 And I'm like, and I'm asking like, oh, tell me more about this, like why? 21:34 And she said well, Podcasts are great for somebody that wants to 21:37 load up their on their iPhone or their iPod, or whatever other. 21:41 There are are there other MPC players? 21:46 [LAUGH] Put, put them on my device and take them for my commute. 21:47 And and she said to me I can't use the those audio files that 21:55 way I would love a downloadable copy that I could put on my ebook reader. 21:59 Right? 22:03 Exactly the same way, so that she could take them for her commute, and 22:03 read them read them exactly the same and I was like oh of course. 22:07 Right? 22:11 So providing that audio, that Podcast, is a great 22:12 idea but we can get that information through to 22:14 the same, to to serve the same purpose by 22:17 putting it in to a downloadable format as well. 22:19 Just a, a text based format. 22:23 So that was actually kinda of a revelation for me as well. 22:24 Like, oh, yeah, it totally makes sense, but I've kind of forgotten why. 22:27 I was so caught up in the technical, we have to have a transcript available. 22:30 I didn't even think about making it so that it 22:34 was easily downloadable and transferable to a, to a an e-reader. 22:36 Lesson number three, proximity. 22:43 So, this is a design principle that you should all be familiar with. 22:46 I stayed at a hotel in London, in the UK, and I had this for my faucet, 22:50 where I had a hot water tap on the left and another hot water tap on the right. 22:57 [LAUGH] Hey, I didn't know what to do. 23:01 So, like I'm out. 23:06 I'll be dirty for today. 23:07 I'm not, I'm not doing this. 23:08 And it didn't make sense until I saw this, that told me that 23:11 the left tap operates the shower and the right tap operates the bath. 23:13 So, now I at least know if I'm gonna burn my head or my feet. 23:17 The problem was that the faucet is down there and 23:22 the instructions are about six feet away on the side wall. 23:25 And you all know that those instructions need to be right there 23:30 but they're not, they need to be in the line of sight, right? 23:34 We need to do things an interface where we group, group those 23:36 closely related items, we need to put them together cuz they belong together. 23:41 This is, this is critical for everybody but 23:47 for somebody that has low vision, this is everything. 23:49 So, when we're looking at a layout, we 23:54 need to consider that idea of proximity and 23:56 we also need to consider the pattern of 23:59 use that we have for somebody with low vision. 24:01 This is a form that was coded to be perfectly 24:04 accessible and it was, it was very screen reader friendly. 24:07 It did the job. 24:11 It did the trick. 24:12 It was accessible. 24:13 We can dust off our hands and we're finished, 24:14 and when we're assessing this and we're looking at it, 24:17 we put on the lens of a, of somebody 24:20 with low vision and how they're gonna use this form. 24:22 You can see that there's chunks of information here. 24:25 We've got these two questions and these two answers, and 24:27 these two questions, and these two answers, and we see 24:30 that we've got these buttons at the bottom, and these 24:33 hidden open tips things that almost nobody ever, ever sees. 24:35 Want you to step through this, and we're gonna look 24:40 at this from the perspective of somebody that has low visions. 24:42 So this is where, where I'm gonna ask you 24:45 to participate and you don't have to talk, you 24:47 don't have to do anything, but you do need 24:50 to take either your left or your right hand 24:52 and I want you to make a fist, and look through like you're holding a straw, and I 24:54 want you to look at this interface and go 24:58 through the motion of actually filling out this form. 25:00 Right? 25:04 I mean it. 25:04 You have to do it. 25:05 And while you're doing it, I will take a photo of you. 25:06 [LAUGH] This is one of my favorite parts of teaching about accessibility. 25:09 [BLANK_AUDIO] 25:14 So what did you need to do to fill out that form? 25:24 A 25:29 lot of this, right? 25:31 Left, right, left, right, left, right. 25:32 So think about this for somebody that has low vision they're zoomed in. 25:34 So I'm gonna simulate this we, you're simulating it by, 25:38 by looking through the straw I'm gonna zoom it in here. 25:41 So ultimately what you're looking at somebody that, that 25:44 has low vision may be, may be using a magnifier. 25:47 They may only see this part of the screen. 25:50 All right? 25:52 They see a limited chunk of the screen at 25:54 a time which is why we look through the straw. 25:56 So when I get to these questions and I scroll over to get 25:59 to those answers, I've lost all the context of what those questions even were. 26:02 Right? 26:07 We've got the wrong associations, there's two questions 26:08 and two sets of answers and they're technically 26:11 perfect for a, for a screen mirror user, but they suck for a low vision user. 26:13 All right so we can get this motion back 26:19 and forth back and forth we come down to these 26:20 other set of questions, we come back to these other 26:22 questions, the, the answers and what's the pattern we created? 26:26 Left to right, left to right, left to right, left, 26:31 oh that's a great cult of action for right now. 26:35 [LAUGH] 26:37 And right underneath the answers, the yes no answers, happen to be this. 26:40 Like, kind of all the calls to action that we don't really want people 26:47 to take, are the ones that we presented first for somebody with mobile vision. 26:50 What else did you notice about the buttons? 26:55 The quit, previous, and next. 26:59 The same >> Color. 27:01 >> Same color. 27:02 Same size. 27:03 Same font. 27:06 Same everything. 27:06 The only way to distinguish between those buttons is you have to read them, right? 27:08 You have to read. 27:13 We, we changed up this design, and we weren't able to, to push 27:15 this through, but we changed up the design to make it much more simple. 27:18 We used layout to create the right chunks. 27:22 So, we still have four chunks, but it's all question and answer together. 27:24 Question answer together. 27:28 All right? 27:29 So now, use the straw. 27:30 [BLANK_AUDIO] 27:31 You'll never, ever eliminate left to right scrolling. 27:35 But how much is there? 27:40 Almost none, right? 27:42 Almost none. 27:44 You'll never eliminate the need to scroll. 27:45 That's always going to be there for somebody with low vision. 27:47 But what we can do is make it more efficient. 27:49 And I love this because, this need for creating this 27:51 streamlined interface is really fantastic for mobile interfaces as well. 27:55 I mean for a narrow, for a narrow device display this works really well. 28:00 So now when we're zoomed in it's like, yeah, this is a no-brainer. 28:05 And what's there? 28:09 Big, fat call to action with some visual distinction to it 28:11 that says, yeah, this is the thing we want you to do. 28:13 So we're using this idea of the straw test to simulate low vision. 28:17 What is does, is it helps you, create 28:22 designs that are better, generally speaking for everyone, right? 28:25 You, I want you to use that straw test. 28:29 Every single time that you're creating a design, 28:31 when you're, when you're working with the design, 28:34 you look for things like that and you 28:36 will find them, you'll find them everywhere, right? 28:38 What inefficiencies are created, and we saw this the other day in an app, where 28:41 there was like, editing a title, and there was a done button right beside it, 28:46 and then all kinds of other fields that you could change, and there was no 28:50 button at the bottom that allowed you to do the same thing to save it. 28:53 Or to say you were done. 28:56 So, the lower vision user, they go from that 28:58 title, down through all the other fields that are there. 29:00 And they get to the end and they're expecting 29:02 to see some kind of a finish button, or 29:04 a save, and they had to go all the way up to the top right corner to find it. 29:06 All right? 29:10 That's, it's just not there, it's not, it's not an expected place. 29:11 So, I, I really want you to think about this. 29:14 Examine your interfaces using that straw test, you 29:17 will find so much, you will unearth design problems 29:20 and layout problems for people with low vision that 29:24 will lead you to create better designs for everybody. 29:27
You need to sign up for Treehouse in order to download course files.Sign up