Multimodality and accessibility. Charlotte Magnusson Certec, Department of Design Sciences, Lund University Sweden

Transcription

1 Multimodality and accessibility Charlotte Magnusson Certec, Department of Design Sciences, Lund University Sweden

2 Certec, Division of Rehabilitation Engineering Research Department of Design Sciences Lund University

3 Whyis accessibilityrelevant for me?

4

5 More people will be able to use your products. Your products will be possible to use in more situations. Accessibility is not us & them everyone has limitations and depending on the situation you experience similar problems Aging Society: there will be more and more elderly people that will use information systems (= big market), however, those products have to consider decreasing visual, auditory, motor, cognitive abilities You will be able to sell to organizations that want accessible products there is an increased focus on accessibility for public services and bad/nonexistent accessibility may put you out of the running

6 You can comply with laws & regulations on accessibility (and you can sell to customers who need to do this). People with special needs are still people. Things learned in this context is often applicable to & useful for everyone. If you are differently abled, good design is often more critical - i.e it is harder for a designer to get away with poor design solutions. It can also be a good way of forcing yourself to think "out of the box". Starting from a new perspective can potentially generate new and possibly better solutions. Building things in from the beginning is not necessarily more expensive/more difficult. Changing them later in the process usually is.

7

8 What is it? ISO defines accessibility as: "usability of a product, service, environment, or facility by people with the widest range of capabilities". How to do it?

9 Design is a process "Would you tell me, please, which way I ought to go from here?" "That depends a good deal on where you want to get to," said the Cat. "I don t much care where ----" said Alice. "Then it doesn t matter which way you go," said the Cat. "----- so long as I get somewhere," Alice added as an explanation. "Oh, you re sure to do that," said the Cat, "if you only walk long enough." Alice s Adventures in Wonderland, Lewis Carroll

10 Not linear There is no direct path between the designer s intention and the outcome. As you work a problem, you are continually in the process of developing a path into it, forming new appreciations and understandings as you make new moves. (Schön, Bennett, Bringing Design to Software Winograd, 1996)

11 Explore the design space

12 The user Usability? Relevance Efficiency Attitude Learnability Useworthiness? High priority needs

13 Designers are not users - traps you need to avoid Avoid the temptation. Trap 1: Surely it is enough if I test this myself? Trap 2: This is really simple and elegant! Trap 3: Surely this is just common sense? Trap 4: I did test this on my colleague

14 What do you want? What can I get?

15 User centred design early focus on users and tasks empirical measurement iterative design

16 Some things to do: Lo-fi prototyping. Challenging for this type of interactions, but possible! Make use of existing guidelines, principles, user requirements, personas, scenarios etc etc And of course test (also with real users in real situations).

17 We all make mistakes Get rid of yours early!

18 Mobile devices?

19 What do these persons have in common?

20 Limited overview Sensitive to changes in space and time Needs flexible solutions that give you what you want when you need it

21 W3C/WAI The link mobile - accessibility is in fact already recognized by the W3C/WAI es Perceivable Operable Understandable Robust

22 WAI guidelines, example Scripts, applets, & plug-ins. Provide alternative content in case active features are inaccessible or unsupported.

23 Evaluating Web Site Accessibility: Validating the WAI Guidelines through Usability Testing with Disabled Users Dagfinn Rømen, Dag Svanæs

24 Problems specific to visually impaired users: Links that start with the same letter and almost read the same. These are difficult to distinguish. Links with identical spelling that point to different places (e.g. Click here to go to A and here to got to B ). High number of links and redundant links.

25 Problems specific to motor impaired users (tremor etc.): If the surface of a screen element was larger than the actual clickable surface. Mouse-over menus. Small font size and a high number of links placed closely together increases the risk of erroneous clicks.

26 Problems specific to dyslectic users Positioning of links and navigational mechanisms. Links that are placed far off to either side of the webpage are often missed by dyslectic users. Web pages crowded with a lot of text and links become confusing and difficult to read and navigate.

27 Things to think of Universal design/design for all/inclusive design d/about_ud/udprinciples.htm

28

29 Don t forget Improvisation! Build in the possibility for improvisation your device will not be alone in the world (and neither will the user).

30 The STEP method. esignforcognitive/ Security context Experience/memory Precision

31 FACE ce/ FACE tool, which examines Function based on Attitude, Control and Enabling.

32

33

34 ENACTIVE NoE Guidelines EI_WP11_DLV11_.

35 It is not enough to merely replace graphic information with audio/haptics Make sure the models are haptically accurate and work without vision Provide a clear reference system Clear and timely responses Possible to turn off feedback Users rely on haptics/audio differently

36 MICOLE guidelines deliverables/micole-d14-final.pdf

37 Interface design Exploration/navigation Overview Object properties Manipulation Virtual environment Physical device

38 Group work Context Background knowledge Shared workspace Awareness Guidance Role/initiative/empowerment

39 Help users find and explore objects Provide strategies Rythm (audio/haptic) Directional references need to be similar virtual/real Visually simple is not haptically simple Complete feedback Clear tactons Predictable behaviours Application design -> social dominance

40 Other observations Don t build in unneccessary limitations Design for each modality (remember to close your eyes) (Emulator size vs real size)

41 Gestures

42 Timing important! 0,2 20 ms Musical interfaces

43 Hardware constraints Power consumption Reliability Speed These are general issues, which typically become even more important for users with special needs.

44

45 Much to do

46 Thank you!