Wiki source code of Inclusive Design
Version 7.1 by Haoran Wang on 2022/03/14 21:32
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
| |
6.1 | 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.]] |
| |
7.1 | 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 | |||
| |
3.1 | 5 | - Perceptual |
| |
2.1 | 6 | * Blind |
| 7 | * Deaf | ||
| 8 | - Motor | ||
| 9 | * | ||
| 10 | |||
| 11 | - Cognitive | ||
| 12 | *Dementia | ||
| 13 | *Down's syndrome | ||
| 14 | *Autism | ||
| 15 | |||
| 16 | |||
| |
5.1 | 17 | There is no generic "disabled user". Creating different personas and scenarios helped us to consider a more robust user. |
| |
2.1 | 18 | |
| |
3.1 | 19 | 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: |
| |
2.1 | 20 | |
| 21 | |||
| |
3.1 | 22 | === Deaf patient === |
| |
2.1 | 23 | |
| 24 | Use of redundant information leveraging both audio and visual channels of communications between Pepper and the PwD | ||
| 25 | |||
| 26 | |||
| |
3.1 | 27 | === Price === |
| |
2.1 | 28 | |
| 29 | Need to do the maths, because it might be that Pepper cost averages out. | ||
| 30 | |||
| 31 | |||
| 32 | |||
| |
4.1 | 33 | We paid additional details to not making wrong assumptions about our users. By not stereotyping, not patronising or stigmatising the patients. |
| |
2.1 | 34 | |
| |
4.1 | 35 | -> Examples? |
| |
2.1 | 36 | |
| |
4.1 | 37 | |
| 38 | |||
| 39 | |||
| 40 |