Can you afford this? - Tailoring Technology for Individuals - Amy Dickens - Codemotion Amsterdam 2018
•Download as PPTX, PDF•
0 likes•236 views
If you woke up tomorrow and couldn’t use your arms to get out of bed, or use your voice to call out for help, and couldn’t see beyond your feet. How would you express yourself? Technology has given us almost unimaginable ways to expand our horizons: gesture recognition, voice controlled interfaces and machine learning, are just a few examples. But does this include everyone? This talk follows a case study in which users with complex disabilities interact with music technology. We will discuss techniques for understanding affordances, tailoring interactions and providing access to all.
Recommended
More Related Content
Similar to Can you afford this? - Tailoring Technology for Individuals - Amy Dickens - Codemotion Amsterdam 2018
Similar to Can you afford this? - Tailoring Technology for Individuals - Amy Dickens - Codemotion Amsterdam 2018 (20)
More from Codemotion
More from Codemotion (20)
Recently uploaded
Recently uploaded (20)
Can you afford this? - Tailoring Technology for Individuals - Amy Dickens - Codemotion Amsterdam 2018
- 2. Can You Afford This? Tailoring Technology for the Individual Amy Dickens GitHub Campus Rep @RedRoxProjects
- 4. AFFORDANCES - What are they? METHODS - For User Experience (UX) Design CASE STUDY - Accessible Digital Musical Instruments TOP TIPS - For building accessibility into technology @RedRoxProjects
- 5. @RedRoxProjects How many people are living with a disability?
- 6. @RedRoxProjects 19% of working age adults are disabled (source: Scope, scope.org.uk)
- 9. AFFORDANCES - What are they? METHODS - For User Experience (UX) Design CASE STUDY - Accessible Digital Musical Instruments WHAT NEXT - Tailored Technology for Tomorrow’s User @RedRoxProjects
- 10. @RedRoxProjects AFFORDANCES Do people know what to do based on what they see?
- 11. @RedRoxProjects
- 13. @RedRoxProjects Screen Readers: Dos and Don’ts DO consider your layout and arrange the content so it can be read correctly by screen readers DON’T use html tags to style things - edit your CSS file DO use full descriptive names for images and add alt text where possible DON’T use shortcuts to correct pronunciation
- 14. @RedRoxProjects Let’s talk about FOCUS . . .
- 15. @RedRoxProjects Visual Navigation: Consider FOCUS for those using eye-trackers Published 28th July 2013 by gazepoint https://www.youtube.com/watch?v=SBhNadkCK8o CONSIDER how the interaction might change when using an eye-tracking controller Don’t use emphasis if it isn’t needed, make sure you draw ATTENTION to the right things
- 16. @RedRoxProjects New technologies often focus on the experience of able bodied users - when the potential for users with a disability could be MASSIVE
- 17. @RedRoxProjects Hearing Impairments: There is a SPECTRUM of hearing impairments COCHLEAR IMPLANTS are used by some people Try to always provide CLOSED CAPTIONING for everything that needs to be heard to be understood Relying on algorithms can be a risk - PROVIDE IN ADVANCE where possible
- 19. @RedRoxProjects Hidden Disabilities: Autism Spectrum Disorders (ASD) Mental Health Issues Fatigue & Chronic Pain Sleep disorders Attention Deficit Hyperactivity Disorder (ADHD)
- 20. @RedRoxProjects In the age of PERSONALISATION - the best thing we can do is MAXIMISE this for people with a disability and provide OPTIONS to TAILOR a product to a user
- 21. AFFORDANCES - What are they? METHODS - For User Experience (UX) Design CASE STUDY - Accessible Digital Musical Instruments WHAT NEXT - Tailored Technology for Tomorrow’s User @RedRoxProjects
- 23. @RedRoxProjects REPORTS SURVEYS FOCUS GROUPS BIG DATAARCHIVES
- 25. @RedRoxProjects “Simple, flexible and adaptable technologies that focus on understanding the NEEDS and DESIRES of users in a REAL-WORLD setting” Hutchinson et Al. “ Technology Probes: Inspiring Design for and with Families,” presented at the Proceedings of the SIGCHI Conference on Human Factors in Computing Systems - CHI ’03 , pp. 17– 24 (2003 April), doi:10: 1145/642611: 642616, https:// doi:org/10:1145/642611:642616
- 28. @RedRoxProjects
- 29. @RedRoxProjects GOMS (Goals, Operators, Methods, Selection) testing EXPLORATORY Studies EYE TRACKING Sessions FAIL / BREAK Testing ACCESSIBILITY Checks USER PERSONA Walk Throughs
- 31. @RedRoxProjects SURVEYS online / in person USER INTERVIEWS naturalistic / structured FOCUS GROUPS for important iterations RATINGS in app stores / review sites
- 32. AFFORDANCES - What are they? METHODS - For User Experience (UX) Design CASE STUDY - Accessible Digital Musical Instruments WHAT NEXT - Tailored Technology for Tomorrow’s User @RedRoxProjects
- 33. Digital Musical Instruments (DMIs) & Accessibility... @RedRoxProjects
- 34. @RedRoxProjects
- 35. @RedRoxProjects Build a DMI that can be used by people with disabilities
- 36. @RedRoxProjects
- 37. @RedRoxProjects
- 38. @RedRoxProjects Can the thing withstand a drop? ROBUSTNESS Can we eliminate the risk of cables? WIRELESS Can the user manipulate the thing? MALLEABILITY Is there a direct relationship between input and output? CAUSALITY
- 40. @RedRoxProjects Can we eliminate the risk of cables? WIRELESS
- 41. @RedRoxProjects Is there a direct relationship between input and output? CAUSALITY
- 42. @RedRoxProjects Can the user manipulate the thing? MALLEABILITY
- 43. Can the thing withstand a drop? ROBUSTNESS @RedRoxProjects
- 44. @RedRoxProjects
- 45. @RedRoxProjects RASPBERRY PI ZERO DATA EXCHANGE VIA PYTHON SCRIPT ENVIRO pHAT UNICORN pHAT DATA TO MIDI CONVERSION VIA MAX FOR LIVE MACBOOK PRO ABLETON LIVE SOUND OUTPUT VISUAL OUTPUT
- 47. @RedRoxProjects MY A11Y TOP TIPS Connect with a COMMUNITY of users for UX testing Never ASSUME who your users are, their likes or behaviour! Keep up to date with CHANGES in accessibility (a11y casts by Rob Dodson on Google Chrome Developers YouTube channel) Remember your team are NOT your average users BUILD for accessibility even when you don’t think it is needed
- 48. @RedRoxProjects Accessibility should be a FOUNDATION not a feature that you add on later...
- 49. @RedRoxProjects Thank You Amy Dickens TWEET ME @RedRoxProjects FOLLOW ME github.com/redroxprojects EMAIL ME amy@adickens.co.uk
Editor's Notes
- Introduce me Researcher in UX Design GitHub Campus Rep Teacher of things Git - meet up this week Founder of My Kind Of Tech - community interest company in the UK, focused on providing inclusive event services
- NOW: What are we here to talk about Today I’m going to talk about building products for users with disabilities, be it software or hardware… We will look at some of the core aspects of User Experience Design when considering this user group. To do this I’m going to be taking you through the following: Affordances - what they are and why it’s important to analyse these Methods - in user experience design practice A Case Study - of my work with accessible digital musical instruments And a look into the future in terms of what next for the enabled technology user But before we begin - let’s look at some stats... NEXT: Statistics with doughnuts
- NOW: Statistics with doughnuts Before we get into the talk - let’s look at the stats. I’d like everyone in the room to consider this question - how many people do you think there are in the world living with a disability? Do you personally know someone with a disability? Or perhaps you know of someone with a disability? How many people here would take a guess and say that number is lower than 10% of the population? Raise your hand if you’re able to. NEXT: Stats on disability
- NOW: Stats on disability It’s actually around 19% - but that figure is also questionable because it relies on people disclosing their disability status - which like mental health status is something that people are cautious about doing. So around 19% of the people in the world are living with a disability - which in turn, means that if you have a product out there that doesn’t have accessibility features it can’t be used by these people, you are building a product that isolates nearly a quarter of the potential users without trying. And sure 19% doesn’t sound like a lot, it’s better than 50% but I’m sure many people here wouldn’t like it if they lost 19% of their pay…. In fact in numbers it’s quite large... NEXT: How we interpret the stats
- NOW: How we interpret the stats It’s 1.3 billion people. And what is worse is that over a quarter of disabled people say that they do not frequently have choice and control over their daily lives - which is really hard to swallow because technology can help with so many of the issues that disabled people face in their daily lives. We have the devices, personal assistants, features inbuilt into our laptops and phones, it’s just that NOW: How do we reach that X percent
- NOW: How do we reach that X percent So the question I am trying to help you with today - is how do you make sure you are reaching that 19% by making your thing into something they can easily use... NEXT: Affordances
- NOW: Affordances So first we need to look at a term known in UX design as affordances... NEXT: What are affordances?
- NOW: What are affordances? The word "affordance" was originally invented by the perceptual psychologist J. J. Gibson (1977, 1979) to refer to the actionable properties between the world and an actor (a person or animal). A term popularised by Don Norman in his book The Design of Everyday Things Typically affordances are a visual/physical cue that a) gets the users attention and b) implies a function Do people know what to do based on what they see? The design concept of affordance is to get people doing things with as little training as possible. In design, we care much more about what the user perceives than what is actually true. NEXT: Readability
- NOW: What are affordances? Example - the door handle So what kinds of interactions do we need to think about in order to properly design an experience in a way that the affordances of the thing implicitly tell the user this is how to do X? NEXT: Readability
- NOW: Readability When we think about readability we often default to typography - what about screen readers? Colour options? Did you know that there are already tools out there that can help you to optimise your websites for accessible colour choices? Well now you do and there are no excuses for having unreadable colour combinations!! NEXT: Screen Readers dos and donts
- NOW: Screen Readers Dos and Donts Web layouts & Content for screen readers Think about your tags - please please please don’t use tags for styling… i.e. change your CSS file not repeatedly using a H2 for the formatting it provides - ONLY use a heading when it is one. The rotor - as a map Accessible view on safari - have you ever used it Image Names - picture.jpeg Screen readers on Ipads Voice Assistants - the rule of one breath. Rob Dodson - Accessibility Casts ‘A11ycasts’ NEXT: Keyboard accessibility
- NOW: Keyboard accessibility Keyboard accessibility - have you framed the thing in the right order… have you even tried to navigate your own product with only the keyboard… Focus refers to selecting an element and controlling that element using all the keyboard commands. For some users focus is a primary access point and is absolutely critical. Commonly tab and shift tab keys are assigned for changing focus - especially web. Tab order is the term used for the order in which your product elements will go into. So it’s important to consider your visual layout in correlation to the tab order - if you change the placement of things with CSS in web development without considering their tab order you will end up with a focus that jumps all over your pages with a nonsensical order. You can fix this by moving things in the dom - putting things in the correct order within the dom can result in better focus order. If you have a web presence at all you should consider moving things NEXT: Visual Navigation
- NOW: Visual Navigation So if we have focus in web applications for keyboard navigation - what happens when the user is unable to use a keyboard and navigates visually - not only do you have to consider what elements are able to be interactive - you need to think about the visual draw of your application or website. On the left of my slide here is a video from youtube showing gaze when interacting with a google search and youtube. It is really important to understand your product through your user’s eyes. When we develop the things and even when we are designing the thing we attain this unconscious knowledge of the product that means no matter how much WE might have tried to check for these things - nothing beats bringing someone in who has never seen the thing and asking them to complete a task using your product. Larger companies do these kinds of tests, advertisers are really interested in these kinds of things too but in essence we ALL should be interested because it makes all the difference knowing what is and isn’t glaringly obvious to a user. NEXT: Visual Navigation VR
- NOW: Visual Navigation - VR Think about the potential of something like VR for a person that uses gaze to interact with technology. One thing that’s possible here is to create an environment in which they can seemingly interact as an able bodied person. There are so many possibilities out there through the affordances of new technology - but they are seldom explored for the disabled user, which is really saddening to see as the potential here is huge... NEXT: Hearing Impairments
- NOW: Hearing Impairments We’ve talked about tools for those with low vision - but what about a user with a hearing impairment? Like all disabilities hearing impairments exist on a spectrum… When looking at users with these you might encounter Cochlear implants - these are implants within the brain that communicate with an external device that is placed on the head of the user connected via a magnet - this produces signals in response to sounds and these can be interpreted by the user - this can mean that sound is very different and some frequencies may even be painful or irritating to experience To ensure those with a hearing difficulty can understand the content you put out try to provide closed captioning and audio description where possible, relying on algorithms can be risky - it’s great if you can do this in advance or at least transcribe it correctly afterwards Next: Limited Mobility
- NOW: Limited Mobility Mobility issues and technology When considering limited mobility there are a number of things that might need to be adapted for a user with difficulties.. Screen placement, adapted keyboards, Famous comic about disability - person in a wheelchair & able bodied students outside a school where there has been heavy snow - janitor is shovelling the stairs first and person in a wheelchair points out that if you shovel the ramp we all can get in - when you design for these things it makes your product more accessible to EVERYONE not just the disabled user - so why not make it a priority? NEXT: Hidden Disabilities
- NOW: Hidden Disabilities Hidden disabilities - these are primarily neurological. We talk about hidden disability but in terms of statistics there are people with conditions like this that will not have access or support or be classed as disabled. However their condition can still be very disabling. Managing the way you present information can really help people with Help those with ASD by storifying content or actions expected of them within your product. Ensure compatibility with filters for people who might be trying to avoid blue-light due to sleep disorder. Avoid asking users for prolonged difficult to produce gestures - make things simple NEXT: Tailoring
- NOW: Tailoring Personalisation is the key - allowing users to tailor technologies based on their ability will allow them to have a better experience - machine learning is helping us get somewhere in some contexts but there is a lot more we can do as designers and developers to ensure this is possible - even just providing options on colour modes within a UI is a start and such a small change can be of huge benefit to so many people How do we select the most important things NEXT: UX Methods
- NOW: UX Methods UX methods NEXT: User Research
- NOW: User Research Research NEXT: User Research Tips
- NOW: User Research Tips Surveys / output of reports / focus groups / BIG DATA NEXT: Technology Probes
- NOW: Technology Probes Technology Probes NEXT: Testing
- NOW: Technology Probes Simple flexible and adaptable Technology Probes NEXT: In the wild
- NOW: Putting things into “the Wild” Putting things into “the Wild” No matter what context your product will be used in - you will encounter a user with a disability NEXT: UX testing
- NOW: User Research Research NEXT: User Research Tips
- NOW: UX testing intro When someone says these four words to you it might not be quite clear what “usability” even is… and usable doesn’t always equate to accessible NEXT: Testing
- NOW: Testing Quantitative & Qualitative methods GOMS analysis, Break/Fail testing, Exploratory testing, Gaze Testing, Screen Readers & keyboard access etc. User Personas BE WARNED: User personalities, habits or physical restrictions (for example disabilities) are not accounted for in any of the GOMS models MAKE A TABLE NEXT: Putting things “into the wild”
- NOW: User Research Research NEXT: User Research Tips
- NOW: Getting Feedback Feedback - surveys, ratings, user interviews (naturalistic vs structured) NEXT: User Interviews
- NOW: Case Study
- NOW: Case Study My research is in DMIs and accessibility - so for this case study we will look at some of the findings I have made around supporting access to musical experiences for young people with profound and multiple learning disabilities -- please note from this point I will be talking about disability in this context - where it is at the severe end of the spectrum with many complexities. NEXT: Intro to DMIs
- NOW: Case Study So what is a DMI? People often think of equipment like this when they think of a digital musical instrument - something that resembles an acoustic instrument with some augmentations - but that’s not the case at all. There are midi controllers, ipad apps, gesture controllers, conductive paint, touchboards and all kinds of technology being used for music creation and performance. Again the tools available are largely explored outside of a disabled user’s needs and that’s where the focus of my research is... NEXT: Development
- NOW: Development overview Our starting point is to look at the task - what are we trying to achieve in our development and what can help us do that? The task in my research - looks something like this - what do we need to know to build a DMI that can be used by people with disabilities… NEXT: Starting point
- NOW: Starting point Starting point the user issues: So we start with analysing the needs of a disabled user - we can refer to guidelines, conduct user interviews, field studies and more to gain knowledge of our user and what they need. We want to create something that can be used by everyone - but remember when it comes to disability there is no one size fits all and the best solutions provide a user with opportunities to tailor their experience to suit their individual abilities. NEXT: Expanding this
- NOW: Expanding this Starting point the user issues: So we start with analysing the needs of a disabled user - we can refer to guidelines, conduct user interviews, field studies and more to gain knowledge of our user and what they need. We want to create something that can be used by everyone - but remember when it comes to disability there is no one size fits all and the best solutions provide a user with opportunities to tailor their experience to suit their individual abilities. NEXT: four key areas
- NOW: Four key areas From my experience I have noted that the following areas are of up-most priority when considering this user group. Robustness Make the thing able to withstand being dropped. Wireless Having a wireless technology allows for way more flexibility in this setting and means there is one less risk area to watch out for by eliminating the need for cables. Malleability Causality NEXT: System Requirements
- NOW: So we need a system with this criteria NEXT:
- NOW: First Requirement Starting with point one: Wireless technology NEXT: Second Requirement
- NOW: Second Requirement Then point two: Causality in control through gesture - how does the user know they are interacting with the thing... NEXT: Third Requirement
- NOW: Third Requirement Point three: holdable - malleable - sometimes you find things in places you least expect them - for the minimum viable product this solution was really useful, cheap and could be implemented quickly
- Part 4: robust Design how to house the pi so it can withstand a drop - silicone cover… diffuse the light and add protection to the structure - hard wiring (aka soldering) over changeable connectors to strengthen the electronic structure
- Put it together
- Under the hood
- Blog post about this coming soon NEXT: my top tips
- NOW: My top tips Top tips NEXT: Thank You
- Quote to End
- Please feel free to come talk to me at the back after the session if you have any questions or want to discuss projects <3