Wiki source code of Inclusive Design
Version 10.1 by Haoran Wang on 2022/03/14 21:34
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | Inclusive design is a design process in which a product, service, or environment is designed to be usable for as many people as possible, particularly groups who are traditionally excluded from being able to use an interface or navigate an environment. [[Wikipedia>>https://en.wikipedia.org/wiki/Inclusive_design#:~:text=Inclusive%20design%20is%20a%20design,interface%20or%20navigate%20an%20environment.]] | ||
| 2 | |||
| 3 | For our case, it is necessary to have a universal design that is inclusive to a variety of people that may have different handicaps: | ||
| 4 | 1. Perceptual | ||
| 5 | * Blind | ||
| 6 | * Deaf | ||
| 7 | |||
| 8 | 2. Motor | ||
| 9 | |||
| 10 | * List item | ||
| 11 | * List item | ||
| 12 | |||
| 13 | 3. Cognitive | ||
| 14 | |||
| 15 | * Dementia | ||
| 16 | * Down's Syndrome | ||
| 17 | * Autism | ||
| 18 | |||
| 19 | |||
| 20 | There is no generic "disabled user". Creating different personas and scenarios helped us to consider a more robust user. | ||
| 21 | |||
| 22 | Our design was already made for people with dementia. However, this lecture and the feedback from the presentation of the previous week helped us to consider two more general cases: | ||
| 23 | |||
| 24 | |||
| 25 | === Deaf patient === | ||
| 26 | |||
| 27 | Use of redundant information leveraging both audio and visual channels of communications between Pepper and the PwD | ||
| 28 | |||
| 29 | |||
| 30 | === Price === | ||
| 31 | |||
| 32 | Need to do the maths, because it might be that Pepper cost averages out. | ||
| 33 | |||
| 34 | |||
| 35 | |||
| 36 | We paid additional details to not making wrong assumptions about our users. By not stereotyping, not patronising or stigmatising the patients. | ||
| 37 | |||
| 38 | -> Examples? | ||
| 39 | |||
| 40 | |||
| 41 | |||
| 42 |