Making Touch-based Mobile Phones Accessible for the Visually Impaired
Content
Department of Information Systems and Computing
MSc Information Systems Management
Academic Year 2009-2010
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Alexander Dreyer Johnsen - 0834060
A Dissertation submitted in partial fulfillment of the requirement for the degree of
Master of Science
Brunel University
Department of Information Systems and Computing
Uxbridge, Middlesex UB8 3PH
United Kingdom
Tel: +44 (0) 1895 203397
Fax: +44 (0) 1895 251686
Dissertation Task 2
0834060
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
ABSTRACT
The mobile phone enjoys increased popularity, providing new means of connectivity and
functionality. Today most phones comes equipped with touch-based screens, enabling
the user to interact in an easier and more efficient way, compared to standard buttons.
However, such screens require visual navigation, ruling out access for the visually
impaired; evidently, modern phones are not designed for this user group.
By analyzing the mobile market, available solutions, and current technology, it was
found that neither the society, nor manufacturers of products and services, is designing
for the visually impaired. Thus, this group is denied access to the numerous services and
possibilities sighted people enjoy.
However, it is possible to operate mobile phones through the use of applications called
screen readers; still, these applications have proven to be ineffective and less than userfriendly on touch screens. Hence, this dissertation sets out to find an alternative
approach; to construct a solution that will make touch-based mobile phones accessible
for the visually impaired.
Design research was chosen as the methodology for the project. Design research
highlights the importance of developing a solution over the course of several iterations,
and to perform product evaluation using external participants. A total of five iterations
were carried out, resulting in several artifacts and a prototype for a user interface. The
prototype was designed to replace the phone’s own user interface and provide an easy
and intuitive way of operating a touch-based mobile phone.
Through the process of developing the user interface, virtual prototypes and other
artifacts were created. The virtual prototypes turned out to be of great advantage,
communicating the vision and potentials of the final product to the stakeholders. In
addition, the experience from the project shows that a successful development project
should produce several iterations, have well-documented artifacts and perform external
user testing.
The new user interface was developed for the Android OS to replace the phone’s own
user interface. Operation relies on voice and haptic feedback, where the user receives
information when tapping or dragging the finger across the screen. The proposed
solution is unique in many ways, it keeps gestures to a minimum, it does not rely on
physical keys, and it presents a menu layout similar to most Nokia mobile phones.
Dissertation Task 2
0834060
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
ACKNOWLEDGEMENTS
The process of writing this dissertation has been long and exhausting, and would not
have been possible without the involvement and support from several people; for this I
am grateful.
First, I would like to thank my supervisor Bendik Bygstad for his guidance and academic
support throughout the project. It has been indispensable and a key factor for the
accomplishment of this dissertation.
Secondly, I would like to thank Tor Ulland at Huseby Resource Centre for the blind,
for taking an interest in the project and for sharing his knowledge and insights on life
without vision. Ulland also acquired all of the participants for the evaluations,
ensuring the completion of the project
Without the involvement of May-Britt Haug, at The Norwegian Association of the Blind
and Partially Sighted, I would not have had the possibility of getting in touch with
Huseby or Tor Ulland. Thank you for believing in the project.
I would also like to thank Magne Gabrielsen, Gaby Groff-Jensen and Knut Beck at
SmartPhones Telecom for believing in the project, providing both financial and
developmental resources. Kim Ruben Teigen, whose development skills ensured the
realization of the User Interface, a key contribution to the success of the project.
A special thank you to my wife Ragnhild Eg, for her continued support throughout the
dissertation. You have stayed up countless nights proofreading, and have continued to
support me during the entire process.
I would also like to thank my family, friends, fellow students and colleagues for the
continued support during the process of writing the dissertation.
Last, but not least, I would like to thank the anonymous participants for spending their
spare time on evaluating and providing feedback on the User Interface. Not only once,
but twice!
Thank you!
I certify that the work presented in the dissertation is my own unless referenced
Signature: .........................................
Date............31.01.2011....................
TOTAL NUMBER OF WORDS: 13.031
Dissertation Task 2
0834060
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
TABLE OF CONTENTS
Chapter 1: Introduction .................................................................................................. 7
1.1 Problems that people with vision loss face .................................................. 7
1.2 Back to society ............................................................................................. 8
1.3 Research aim and objectives ........................................................................ 8
1.4 Research approach ....................................................................................... 9
1.5 Dissertation outline ...................................................................................... 9
Chapter 2: Literature review ........................................................................................ 10
2.1 Equal opportunities .................................................................................... 10
2.2 The mobile market ..................................................................................... 11
2.3 Potential problems with smartphones ........................................................ 11
2.4 Improving compatibility ............................................................................ 11
2.5 Assistive technology .................................................................................. 12
2.6 Screen reader .............................................................................................. 12
2.7 Reading and input of text ........................................................................... 13
2.8 Haptics ....................................................................................................... 15
2.9 Making a better user interface.................................................................... 15
2.10 Turning the mobile phone into an assistive aid ....................................... 16
2.11 Framework ............................................................................................... 16
Chapter 3: Research Method ........................................................................................ 18
3.1 Design research .......................................................................................... 18
3.2 Awareness of problem ............................................................................... 20
3.3 Suggestion .................................................................................................. 20
3.4 Development .............................................................................................. 21
3.5 Evaluation .................................................................................................. 22
3.6 Conclusion ................................................................................................. 24
Chapter 4: Research results .......................................................................................... 25
4.1 Results in regards to development ............................................................. 25
4.2 Results in regards to testing ....................................................................... 29
Chapter 5: Discussion .................................................................................................. 34
5.1 Design as an Artifact .................................................................................. 34
5.2 Problem relevance ...................................................................................... 35
5.3 Design evaluation....................................................................................... 35
5.4 Research contributions ............................................................................... 36
5.5 Research rigor ............................................................................................ 36
5.6 Design as a Search progress ....................................................................... 36
5.7 Communication of research ....................................................................... 36
5.8 Summary of discussion .............................................................................. 37
Chapter 6: Critical evaluation of research ................................................................... 38
Chapter 7: Conclusion.................................................................................................. 40
7.1 Summary of the dissertation ...................................................................... 40
7.2 Future research and development .............................................................. 41
Dissertation Task 2
0834060
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
References .................................................................................................................... 42
Appendix A: Ethical approval ..................................................................................... 52
Appendix B: About the author ..................................................................................... 53
Appendix C: The mobile market.................................................................................. 54
Appendix C.A - The new players .................................................................... 54
Appendix D: Using the mobile phone for assitive aid ................................................. 55
Appendix D.A - Object recognition ................................................................. 55
Appendix D.B - Navigation ............................................................................. 55
Appendix E: Interview with Tor Ulland at Huseby (Statped) ..................................... 57
Appendix F: Project plan ............................................................................................. 60
Appendix G: Project meeting reports .......................................................................... 61
Appendix G.A - Initial project workshop meeting, June 14, 2010 .................. 61
Appendix G.B - Approval of functionality, June 25, 2010 .............................. 63
Appendix G.C - Layout of UI, August 30, 2010 ............................................. 66
Appendix G.D - Layout of UI, September 13, 2010 ........................................ 68
Appendix G.E - Layout of UI, October 10, 2010 ............................................ 70
Appendix G.F - Layout of UI, October 13, 2010............................................. 73
Appendix H: Documentation of ui ............................................................................... 76
Appendix H.A – Documentation of UI, version 0.0.5 ..................................... 76
Appendix H.B – Documentation of Conceptual Design .................................. 79
Appendix H.C – Documentation of Second Prototype, round 1 of
testing ................................................................................................... 84
Appendix H.D – Documentation of Third Prototype, round 2 of testing ........ 87
Appendix I: Development and activity log .................................................................. 90
Appendix J: Information to project participants .......................................................... 96
Appendix K: Consent form .......................................................................................... 97
Appendix L: Participant Survey................................................................................... 98
Appendix L.A: participant survey, round 1 ..................................................... 98
Appendix L.B: Participant survey, round 2 ................................................... 100
Appendix M: Ressults from user testing .................................................................... 102
Appendix M.A: Results from round 1, Overview of all responses ................ 102
Appendix M.B: Results from round 1, Participant 1 ..................................... 106
Appendix M.C: Results from round 1, Participant 2 ..................................... 108
Appendix M.D: Results from round 1, Participant 3 ..................................... 110
Appendix M.E: Results from round 1, Participant 4 ..................................... 112
Appendix M.F: Results from round 2, Overview of all responses ................ 114
Appendix M.G: Results from round 2, Participant 1 ..................................... 118
Dissertation Task 2
0834060
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.H: Results from round 2, Participant 2 ..................................... 120
Appendix M.I: Results from round 2, Participant 3....................................... 122
Appendix M.J: Results from round 2, Participant 4 ...................................... 124
Appendix M.K: Results from round 2, Participant 5 ..................................... 126
Appendix M.L: Results from round 1 and round 2 compared against
each other ........................................................................................... 128
Appendix M.M: T-Test and Effect sizes........................................................ 132
LIST OF TABLES
Table 1 - Framework for the top issues people with vision loss encounter when using
mobile phones with touch screen ........................................................................................ 17
Table 2 - Design Research Guidelines by Hevner et al. (2006) .......................................... 20
Table 3 - Tasks the participants were asked to perform ........................................................ 22
Table 4 - Survey completed by participants .............................................................................. 23
Table 5 - Additional tasks presented to participants ............................................................... 24
Table 6 - Additional survey questions ........................................................................................ 24
Table 7 – Summary of survey categories ................................................................................... 30
Table 8 - Table showing subjective feedback from round two ........................................... 33
Table 9 - Overview on aims and objectives .............................................................................. 38
LIST OF FIGURES
Figure 1- Design Research process model by Vaishnavi and Kuechler (2007) ............. 19
Figure 2 - Some of the menus available in the UI ................................................................... 26
Figure 3 - List navigation in the UI ............................................................................................. 26
Figure 4 - Conceptual UI prototype for people with vision loss ......................................... 27
Figure 5 - Flow map for navigation in the UI........................................................................... 28
Figure 6 - Conceptual model of application.............................................................................. 28
Figure 7 - Graph displaying mean scores from the first and second round of testing .. 30
Figure 8 - Graph displaying a comparison between results from first and second round
of testing on the menu system ............................................................................................. 31
Figure 9 - Graph displaying a comparison between results from first and second round
of testing on the complete solution .................................................................................... 32
Dissertation Task 2
0834060
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
CHAPTER 1: INTRODUCTION
1.1 Problems that people with vision loss face
According to the World Health Organization (WHO) (2009), around 314 million people are
visually impaired, of which approximately 45 million are blind. Of the total number, 12
million are children, 82% are of age 50 or older; furthermore, women have the greatest risk of
becoming visually impaired. Developing countries have the largest representation of visually
impaired people, with around 87% representation. Visual impairment blindness can be
defined as the collective term ―vision loss‖, which refers to either the loss of the ability to see,
or vision reduction. The terms ―low vision‖, partially sighted, or visually impaired, can be
used for a person who has not lost the capability to see, but whose vision is significantly
reduced compared to normal vision (Colenbrander, 2002).
Both groups deal with daily situations that vary greatly depending on the severity of their
visual impairment. A blind person will have to rely on other senses and inputs, such as touch
and hearing, as well as assistive aids, such as the long cane and the guide dog. On the other
hand, an individual with low vision can be aided by visual enhancements, like large print,
magnifiers and illumination (Colenbrander, 2002).
Common for both groups is their encounters with situations and problems that a sighted
person would not consider an issue. This can be seen in everyday situations, where the
environment is designed for the sighted, not someone with vision loss. Accessing stores and
businesses, or simply crossing the street, can turn out to be challenging tasks. Much of our means
of communication is through the use of signs and signals; visual symbols that a person with
vision loss cannot see. For example, danger signs or signs providing direction, road blocks or
general information on public transportation. At worst, situations like these may prevent a person
from wanting to step outside, hence limiting contact with the surrounding world (Tjan et al.
2005; Joseph, 2009; Maines, 2008; Appendix E).
The same restrictions apply to other ordinary situations; TV’s, radios, mobile phones, stoves and
ATM’s are just some examples of equipment that are becoming increasingly advanced. In the
past, such items were mostly equipped with buttons; although not originally designed for people
with vision loss, they made it possible to memorize the steps in order to access a certain feature.
With today’s modern design, with touch screens showing dynamic menus; it has become
impossible for a person with vision loss to memorize and use such equipment. It can be argued
that companies do not consider this user group when designing new products (Picard, 2010;
Appendix E).
Another issue facing people with vision loss is the difficulty some sighted people have when
encountering blind people, making it hard for the latter to develop new relationships. Most jobs
are also designed for the sighted. Due to this, blind people do not meet the same expectations and
are often relegated to specific roles. This is an undesirable situation as employers may lose out
on valuable skills and those who lack vision are left unable to prove their potential. Society
should strive for quality and for implementing people with vision loss into the working
environment (The National Federation of the Blind of Connecticut, n.d.).
Dissertation Task 2
0834060
Page 7 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
1.2 Back to society
Several ideologies and assumptions about blindness and rehabilitation exist. One of the more
accepted is the ―restorative approach‖, embraced by Father Thomas Carroll (American Printing
House for the Blind, 2010). This approach works under the idea that most blind people could,
with the help of professional counseling and training, live full lives. Seven basic losses are highlighted, and the focus is on restoring these through training, with the white cane or a guide dog,
learning to read Braille and using assistive technology (R. A. Scott, 1995). With the correct
equipment and training, a person with vision loss can master ordinary tasks like operating a
computer, reading a book or using mobile phones (Appendix E).
People with vision loss can also participate in sports; blind Soccer is a particular example of
how well correct training in applying other senses can enable a blind person to participate in
team activities. Players are able to play soccer in almost the same way as a sighted person by
relying on shouted commands and specially designed soccer balls, containing ball bearings
(Malinowski, 2010).
1.3 Research aim and objectives
While it is clear that the technology and the will to integrate those with vision loss into society
are strongly present, society is not yet properly adapted. Several aspects can be improved,
where one is the mobile phone.
The mobile phone introduces several benefits, but perhaps the most important is the easy
access to communication with friends, family and the surrounding world. However, most new
mobile phones are designed for visual navigation, rendering the mobile phone inaccessible for
people with vision loss. Designing a phone that is inaccessible for people with vision loss can
at worst result in loss of contact with society, thus the author of this project believes in the
importance of making mobile phones not only accessible, but easy to use, for people with
vision loss.
The aim of this dissertation is to present, develop and evaluate a new User Interface (UI) for
touch-based mobile phones, which will make this type of phones available for people with
vision loss.
Based on the aim of developing a UI, the following objectives are presented:
A literature review on issues related to the operation of touch-based mobile phones
and available assistive aids and technologies
Create a framework for designing the UI
Perform an evaluation of the UI through several iterations; both internal and external
Discussion on the results from the project
Dissertation Task 2
0834060
Page 8 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
1.4 Research approach
The project uses Design research method for developing and testing the UI for touch-based
mobile phones. Design research is designed with development and testing in mind,
encouraging projects to create and deliver several versions of a solution, where major releases
are tested on external participants to provide feedback (Hevner et al. 2006; Vaishnavi &
Kuechler, 2007).
Two versions of the solution were tested on external users, allowing them to provide feedback
and comments on the interfaces. Feedback from the first version was used to improve the
second version.
1.5 Dissertation outline
The dissertation report is organized as follows:
Chapter 2: Presentation of literature, research and the current mobile market relating to people
with vision loss.
Chapter 3: The research method Design research is outlined along with documentation of the
steps followed throughout the project.
Chapter 4: Research results are presented, analyzing the different between the two tested
versions.
Chapter 5: Critical discussion comparing the findings from the literature review with the
results from the evaluation of the UI.
Chapter 6: The processes and the research methodology are critically evaluated.
Chapter 7: The report concludes with a summary of the previous discussions and a highlight
of the contributions to the existing research field, with future research suggestions.
Dissertation Task 2
0834060
Page 9 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
CHAPTER 2: LITERATURE REVIEW
The research field on vision loss encompasses several areas of interest, where this
Dissertation focuses on how people with vision loss can operate mobile phones with touch
screens. Hence, this chapter is divided into several subjects starting with rights of people with
vision loss, followed by a description of the current mobile market, for then to present
available assistive aids and technology. The chapter ends in a framework, used to design the
UI.
2.1 Equal opportunities
It goes without saying that people with vision loss have the same rights as sighted people; yet
the misconception that vision loss reduces work efficiency is a common prejudice (Wall,
2003). A Norwegian report on job opportunities for people with disabilities concluded that
this user group has the largest share of unemployed potential workers compared to the rest of
the population (ECON, 2003). However, a different report that looks into people’s experience
with moving from school to work life, suggests that part of the problem is based on lack of
knowledge and improper administration by government organizations (Berge, 2007).
Several organizations are working towards equal rights for people with vision loss; eliminate
prejudice, integration with society, achieve equal rights and benefits and provide aid to
countries and people struggling with diseases causing blindness.
World Blind union (n.d.) (WBU) is an internationally recognized organization that represents
160 million people with vision loss in 177 member countries; as a universal voice, it aims to
achieve equal rights and opportunities in all aspects of society. However, WBU does not
provide direct services such as training, guidance and access to assistive technology (AFB,
n.d.; NABP, n.d.). These services are designated to local and national organizations, like the
American Foundation for the Blind and The Norwegian Association of the Blind and Partially
Sighted (NABP).
Vision 2020 is a joint cooperation between the WHO, the International Agency for the
Prevention of Blindness (IAPB) and professionals within the field. The main focus is to
eliminate the main causes of avoidable blindness by the year 2020 ant to prevent 100 million
people from becoming blind (Vision 2020, 2009; International Agency for the Prevention of
Blindness, 2010).
Organizations are not the only means for support for people with vision loss. Several
countries have also implemented rules to protect the rights of people with vision loss. In the
United Kingdom, the Disability Discrimination Act states that a person should not be treated
less favorable because of his or her disability. The European Union has introduced a similar
act, which directs its member countries to introduce measures to reduce discrimination against
people with disabilities (Wall, 2003). Norway has taken it a step further with the introduction
of a new discrimination and accessibility law, which state that all new products marketed
towards the general public should be equally accessible to all, regardless of personal
limitations or handicaps (Steria, 2009).
Dissertation Task 2
0834060
Page 10 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
2.2 The mobile market
The mobile phone market enjoys increased popularity, with market shares expanding every
day (IDC 2010), it is now considered larger than the PC market (Neset, 2010). The mobile
market consists mainly of two types of mobile phones; feature phones and smartphones.
Where feature phones are considered low-end phones, with limited features and computer
power (Nusca, 2010; Wikipedia, 2010a), smartphones offer more advanced computing power
and operating systems, as well as greater connectivity; they are essentially small mobile
computers (Wikipedia, 2010b).
During the first quarter of 2010, a total of 314.7 million mobile phones were sold to end users
worldwide, with smartphones making up 54.3 million of the sales (Gartner, 2010b); this is an
increase of 17% compared to the same period in 2009. Although, feature phones are still
considered the platform with the largest sales volume, smartphones have had a positive
increase and sales are expected to increase further in the coming years (IDC, 2010).
According to Gartner (2010) the top five OS for smartphones are; Symbian (44,3%),
Blackberry (19.4%), Apple iOS (15.4%), Google Android (9.6%) and Windows Phone
(6.8%). Apple iOS and Google Android are currently the fastest growing (The Nielsen
Company, 2010) and it is estimates that the Android OS will be the second largest OS
worldwide in 2010 and it will challenge Symbian’s top ranking position in 2014 (Gartner,
2010a). The numbers show that smartphones sales are increasing, suggesting that the market
wants more advanced phones, with more functionality and better connectivity.
A more detailed view on the mobile market and its actors is available in Appendix C.
2.3 Potential problems with smartphones
While smartphones come with a range of additional features, there are drawbacks. Studies
have shown that the majority of users only take advantage of a small portion of the
functionalities available (Gomnæs, 2005). In addition, the touch screen can make it more
difficult to type, as no physical feedback is provided. Nevertheless, the increasing sales
indicate that most sighted people do not consider these factors as show stoppers. However,
this is not the case for those with vision loss.
The majority of information on a mobile phone is presented through graphical means,
rendering access almost impossible for a person with vision loss. A touch-based mobile phone
becomes even harder to access with a touch-based visual design and navigation that contains
no physical representation of where or how to press buttons and icons. With these limitations,
it seems likely that a large user group will be unable to use these types of mobile phones,
segregating them further from the general population. This is also in contradiction with laws
set by the government (Meyers, 2008).
2.4 Improving compatibility
Studies on mobile phone accessibility for elderly and people with disabilities; all conclude
that mobile phones are not designed for these user groups. They point out several aspects that
could improve mobile phone accessibility. Mobile phones should be of adequate size and
shape and have texture with good grip. The screen should be large and the buttons should
have a logical placement for easier memorization of layout. Voice feedback should provide
information and confirm execution of commands. The phone should also provide easy access
to emergency numbers. Finally, the number of features should be kept to a minimum to ensure
ease of use (Abascal & Civit, 2001; Plos & Buisine, 2006; Smith-Jackson et al. 2003; S.K.
Kane et al. 2009). These suggestions are all in accordance with the guidelines on how mobile
Dissertation Task 2
0834060
Page 11 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
phones should be designed, provided by the NABP (n d).
Creators are recommended to follow good practices and standards to ensure that their
applications or web pages are accessible to all user groups (Perea et al. 2006). However, this
recommendation is not always followed; not for mobile phones nor for applications or web
sites. A recent study on disabled’s relationship to social media, like Facebook and Twitter,
concludes that these and similar services are designed for visual navigation, forcing those who
are visually impaired to use mobile versions of the media that are better formatted and have
less content (Tollefsen et al. 2011; Rossen, 2011).
Several guidelines have been presented in recent years to show developers how to design
accessible applications and web sites. For instance, the W3C organization has formed such an
initiative, which develops accessibility guidelines (W3C, 2008). These guidelines are in line
with those published by NAPB (n.d.). Furthermore, Fukuda et al. (2005) proposes to
introduce navigability and listenability metrics for designing and developing applications or
web sites, ensuring that screen readers can navigate and present the information in a clear and
consistent way. Similar suggestions were presented by Calabrò et al. (2009) to ensure that ebooks are compatible with screen readers.
With a range of different web browsers, both on computers and mobile phones, compatibility
cannot always be guaranteed. In light of this, The Mobile Web Initiative Device Description
Working Group has proposed the creation of a Device Description Repository; a database
containing information about mobile devices that can be queried by applications to present
data in the most efficient way (K. Smith & Sanders, 2007).
2.5 Assistive technology
Although mobile phones are not designed for use by people with vision loss, there are solutions
that can compensate or improve such use. These are defined by the general term assistive
technology; they include any product, instrument, equipment or technical system designed for or
used by a person with disabilities, which prevents, compensates, supervise, alleviates or
neutralize the effects of the disability (Perea et al. 2006). Products may range from physical and
living objects like the long cane or the guide dog, to software in a device like a screen reader. For
an individual who is blind, it is impossible to read the content on a screen; hence the aid of
assistive technology is a great benefit in their personal and professional life. This section will
look at current solutions and relevant research that addresses the issue of assistive technology
on mobile phones.
2.6 Screen reader
It is possible to operate a mobile phone or computer without being able to see what is on the
screen. Software applications called screen readers can convert text to speech, enabling the
user to read and navigate the content of a screen through hearing. By listening to voice
communication provided by the screen reader application, users are able to perceive and
navigate the content on the screen, making it possible to perform tasks like word processing,
e-mailing, listening to music and surfing the web (Wikipedia, 2010b).
A screen reader is generally made out of two components; the application which monitors the
content on screen, and a synthesizer, which provides the spoken feedback. This is produced
through text-to-speech, where the text input is provided by the screen reader and the synthetic
voice is produced by the synthesizer. The synthesizer works with different languages and
supports phonemes and grammatical rules (AFB, n.d.). For a screen reader to work efficiently,
Dissertation Task 2
0834060
Page 12 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
applications need to follow common standards so that the content can be interpreted and
presented correctly (Babinszki, 2010).
Screen readers are available for both computers and mobile phones, ranging from products
that are free of charge to those that cost closer to $1.000,-. One example of a screen reader for
computers is JAWS, one of the most feature rich products, but also the most expensive
(Freedom Scientific, n.d.). Screen readers can also be run in a web browser, allowing a person
to use almost any computer (Bigham et al. 2008). On mobile phones, screen readers have
been most common for phones with physical buttons, but are becoming available for phones
with touch screens (Babinszki, 2010).
However, a screen reader must not be confused with the voice feedback often built into
modern mobile phones. Although they are capable of representing menu and application
content, these functions are less advanced when it comes to conveying accurate information.
Moreover, they are limited to phone menus; and so unable to access information inside
applications (Theofanos & Redish, 2003).
Mobile Speak is a commercial screen reader designed for mobile phones that run the
Windows Mobile or Symbian OS. It is considered one of the best solutions for mobile phones,
and it supports phones both with physical buttons and with touch screens (Code Factory, n.d.).
TalkBack and Spiel are two open source screen readers designed for the Android OS; both
enable developers to incorporate screen reader functionality into their applications. Although,
not as advanced as commercial versions, they provide developers with an easy and convenient
way making their applications more accessible (C. Chen & Ganov, 2009; Darilek, 2010).
2.7 Reading and input of text
Braille was created to enable blind people to read text. It is not a new language, but a text
system with dots laid out in an organized manner enabling a blind person to read and write
text in the same manner as a sighted person. By moving the finger across the dots, a trained
person is able to understand the letters that the dots represent, and thus able to read the text
just like a sighted person (AFB, n.d.). Reading text from a computer can also be achieved
through Braille, through the use of refreshable Braille displays, Braille printers and Braille
note takers (AFB, n.d.).
Although Braille is a great tool, its reliance on finger sensitivity can exclude the elderly that
may have reduced feeling in the fingertips (AFB, n.d.). For people who have lowered vision,
Braille might not be needed; magnifiers, loupes and special glasses are just some of the
equipment that can assist a person in reading text NABP (n.d.).
However, Braille is not suited for mobile phone use. Instead, users will have to rely on
different means of typing, depending on the phone in use. For a person with vision loss,
mobile phones equipped with physical keyboards are the preferred means of interaction; this
relies on the feedback provided by buttons. In conjunction with a screen reader, operating a
mobile phone is feasible with a keyboard (Babinszki, 2010; Buxton et al. 2008).
Physical keyboards for mobile phones come either with a T9 (text on 9 keys) or a QWERTY
keyboard layout. A T9 layout consists of a phone pad with numbers ranging from 1 to 9 and
three associated letters on each button; while a QWERTY layout represents the same keys as
a keyboard attached to a computer. Just like a computer keyboard, it is possible to memorize
Dissertation Task 2
0834060
Page 13 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
the layout of these buttons and thus write without looking at the keyboard. In addition,
predictive text is often used together with these layouts, enabling the phone to predict what is
being typed, completing the words faster and correcting spelling mistakes (Wikipedia,
2010d).
Mobile phones equipped with touch screens do not always have a physical keyboard; instead
text is entered on a virtual keyboard presented on the screen. This can render their use a
challenge, as the virtual buttons do not provide any tactile feedback (Yfantidis & Evreinov,
2005; Buxton et al. 2008). Several solutions have been presented to improve the typing of text
on touch screens, ranging from physical equipment that work in cooperation with the mobile
phone to software keyboards installed on the phone.
HumanWare (n.d.) has created an overlay for touch screens that encompass the phone screen
and enables the user to interact with the phone and gain access to the most common functions.
The overlay can also communicate with a separate Braille device, making it possible for the
user to read and write using Braille (HumanWare, n.d.). The advantage with this solution is
that the user can carry only one device and interact directly with it; however, the downside is
that it is only compatible with resistive touch screens (Wikipedia, 2010b); conversely, most
modern phones come with capacitive screens that are only capable of interacting with
conductive materials like a human finger (Wikipedia, 2010a).
As mentioned, mobile phones with touch screens come with virtual keyboards. While they are
handy, experience shows that these keyboards can be troublesome when typing. Hence,
several third party software keyboards have been created. A keyboard named ThickButtons
provides a virtual QWERTY layout on the screen; ThickButtons differentiate itself from a
normal keyboard by anticipating the coming letters and making those letters larger and others
smaller (Wells, 2010b). SlideIT and Swype are two other solutions, where the use of a
dictionary enables users to write words by sliding a finger along the letters without removing
it from the screen (Wells, 2010a; Sorrel, 2010a). Yet another option called SwiftKey
anticipates the following word; developers claim that 1/3 of all words will be correctly
anticipated, resulting in up to 50% faster typing (TouchType, 2010).
However, all of these keyboards require some degree of visual navigation, which may be
suitable for people with low vision but not for blind users. A keyboard called BlindType
(Anon, n.d.) might be suitable for blind users, although this was not its original intention.
BlindType is a QWERTY virtual keyboard, which perceives the users’ typing style. Through
an assumption that the user is familiar with the QWERTY layout, the keyboard is able to
recognize where and or what is being typed on screen without the user having to focus on the
screen. Essentially, a word can be typed at any place on the screen without a keyboard
displayed. In theory, this keyboard could also work for blind users, since it does not require
text to be entered in a defined area and it can automatically correct typing errors. Recently,
the company behind the solution was acquired by Google (Noyes, 2010). Google has also
released a technology called Google Scribe, which predicts what the user is planning to type
(Loftås, 2010).
Furthermore, Yfantidis & Evreinov (2005) have designed a gesture based keyboard specifically
for blind users. It works by tapping the screen to make a square appear, which represents eight
directions; where each direction holds a separate letter. By moving the finger towards one of the
directions, the letter is read out loud and proceeding to remove the finger confirms the selection
for typing.
Dissertation Task 2
0834060
Page 14 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
2.8 Haptics
Haptics is a technology that provides tactical feedback, resulting in a more intuitive and less
visually reliant interface. However, haptics can never replace hearing or vision; rather, it
provides an additional sense. For touch-based interfaces, haptics can make a user ―feel‖ and
visualize the shape of an item without looking at the screen, or it can provide feedback when the
finger reaches the border of an element or a button. Haptics is anticipated to become more
advanced in the feature, with an expected ability to provide even more fine-grained details, such
as the fur of an animal (Buxton et al. 2008; Gemperle et al. 2001; Rassmus-Gröhn, 2006).
Yu & Brewster (2003) have developed a solution for presenting graphs and tables to users with
vision loss. Users can explore virtual graphs and tables through a force feedback device that
creates haptic feedback, while audio is used to present detailed and abstract information.
In a study on user reactions to haptics, Rassmus-Gröhn (2006) found that some rely more on the
audio feedback than the haptics feedback. This suggests that, although haptics can be a valuable
additional modality, some users depend more on the senses they are used to. Hence, solutions
that incorporate haptics will likely be greatly improved if they also implement sound.
2.9 Making a better user interface
Mobile phone manufacturers have noticed the inadequacies in usability of the UIs native to
various OS. Most manufacturers develop their own set of UIs for the mobile phones,
replacing the OS’s own UI (HTC, n.d.; Topolsky, 2008). In addition, Nokia, Intel and the
University of Oulu have established a dedicated research center, which focuses on improving
the UI on mobile devices (Darling, 2010).
Raman and Chen (2008) argue that the UI is only a means to an end and should blend
seamlessly into the user’s way of operating the mobile phone. In contradiction to a computer
OS, the mobile OS should provide access to what the user needs and remain unattended when
not in use. According to Karampelas and Akoumianakis (2003), the layout for mobile phones
should include the following, consistent presentations, alternative navigation tools,
accessibility to common options and functions and self-explanatory navigation.
Hence, several solutions have been put forward to improve the navigation of touch screens for
users with vision loss, essentially providing eyes-free navigation.
One of this was presented by Amy K Karlson et al. (2005) in a study on a user-interface
designed for one-hand thumb use. The interface created a 3x3 square-grid; with each square
containing a link to an application or a sub-menu. Selection is done by tapping one of the
squares, while gestures were introduced for zooming and to navigate between menus and.
Results showed that the participants liked the way the navigation and selection of applications
worked, although they were hesitant with the gestures.
Kane et al. (2008) have developed Slide Rule; a UI that solely operates through the use of
gestures and auditory feedback. By using several combinations of gestures, Slide Rule allows
the user to open applications and perform commands. Results revealed that the proposed
solution performed significantly faster than button based menus. However, due to the gesture
commands, more errors were produced.
Dissertation Task 2
0834060
Page 15 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Amar et al. (2003) built a prototype handheld device that used tactile and auditory feedback to
convey a menu structure that provided easy access to common functions. The menu could be
navigated through one hand access, where each finger would perform a specific task. Rotating
a dial would move through various options and menus, a separate button would return to a
previous menu, and four buttons performed navigation and application functions. Most
participants were satisfied with the solution; however, it was noted that users had problems
forming a conceptual model of the hierarchical menu. This was improved by adding the
feature of pressing a button halfway down, which would state the functionality of the selected
button.
With their application, Strumillo et al. (2009) have abandoned the default phone menu on the
Symbian OS and offer a new, simpler menu that provides audible feedback and access to
common functions and features. While navigating through menus, the user is informed of
what is a displayed and possible action to take. The solution has received good feedback;
however, it was developed for an older version of Symbian, making it incompatible with
today’s Symbian phones.
Eyes-free Shell is an open-source project for the Android platform created by Chen and
Raman (2009); it replaces the phone’s existing UI with a new menu system, providing easy
access to applications, as well as information on time and current location. Eyes-free Shell
uses auditory feedback and gestures to navigate between menus. The user can search for
applications by using the same type of technique presented earlier (Yfantidis & Evreinov,
2005). The application is part of a larger open-source initiative, sponsored by Google, which
aims to make touch-based mobile phones more accessible. However, some features require
physical buttons, rendering the proposed solution inaccessible to certain phones. The reliance
on gestures can also be problematic, as indicated from the findings in other projects
mentioned above (Helft, 2009).
2.10 Turning the mobile phone into an assistive aid
Extending on the common functionalities of the mobile phone, several solutions exist today
that turn the phone into an assistive aid. Appendix D presents some of the functions available,
such as object recognition and navigation.
2.11 Framework
The literature review has pointed out several aspects that hinder the effective use of mobile
phones with touch screen for people with vision loss. Although several factors could warrant
further scrutiny, the aspect that stood out as the main obstacle is the operation of the touch
screen itself.
Based on the literature, a framework pointing out the most important factors for the
development of a new UI for touch-based mobile phones are summarized in table 1.
Dissertation Task 2
0834060
Page 16 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Table 1 - Framework for the top issues people with vision loss encounter when using
mobile phones with touch screen
Dissertation Task 2
0834060
Page 17 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
CHAPTER 3: RESEARCH METHOD
Design research was chosen as the research method for the development project in this
Dissertation. This chapter outlines the selected method along with a documentation of the
steps followed throughout the project.
3.1 Design research
Design research aims to provide solutions for human purposes by creating an artifact; the
artifact is tested to provide feedback on improvements (March & Smith, 1995). It is a design
solving process, with several cycles of iterations, where new and improved artifacts are
constantly put forward. Each artifact is evaluated and new artifacts build on the knowledge of
previous ones; thus it is an approach that encourages innovation (Hevner et al. 2006; Grønli &
Bygstad, 2009).
The research field arose as a result of several failed projects; the failures highlighted the
importance of closely studying the design of a product during development (Vaishnavi &
Kuechler, 2008). The same approach is used in engineering, where a product is developed and
tested to further improve the coming versions (Peffers et al. 2006; Vaishnavi & Kuechler,
2007).
Frederick R. Brooks Jr., best known for his book The Mythical Man-Month (Brooks, 1995),
argues that constant incremental iterations should replace the practice of building complete
product versions. Development teams should produce quick and effective prototypes that can
be tested by external users, which provide valuable feedback for further development (Kelly,
2010).
According to Grønli and Bygstad (2009), design research is particularly relevant for
understanding mobile services and innovation. For a project like the current, where the
developers face a previously unfamiliar condition, best guess is not enough (Nielsen, 1993).
In these situations, feedback from the intended target group becomes vital to the project’s
success. Hence, Design research is the process in which it is uncovered what works and what
does not work (Vaishnavi & Kuechler, 2007).
Several models for successful completion of a Design research project have been presented.
One, presented by Grønli and Bygstad (2009), leverages on two widely accepted approaches
to Design research. The method recommends Vaishnavi and Kuechler's (2007) model for the
overall project framework and the model from Hevner et al. (2006) to evaluate the results.
Vaishnavi and Kuechler's (2007) approach is a five step model, designed to guide a project
from startup to the finished solution, as shown in figure 1. The first step is the ―Awareness of
problem‖, which focuses on highlighting or improving the results of an existing problem. This
is followed by the ―Suggestions‖ step, where the problem is further analyzed using existing
knowledge and theory, culminating in a tentative design. ―Development‖ is the next step,
where the project attempts to implement an artifact according to the suggested solution, which
is then ―evaluated‖ in the fourth step. The whole project is completed with a ―conclusion‖
where the project results are evaluated (Grønli & Bygstad, 2009).
Dissertation Task 2
0834060
Page 18 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Development, evaluation and further suggestions are often performed iteratively, allowing the
researcher to step back and evaluate and make changes as necessary. Stepping back achieves
an understanding that could only be gathered from the specific act of construction, the model
refers to this process as ―circumscription‖ (Vaishnavi & Kuechler, 2007).
Figure 1- Design Research process model by Vaishnavi and Kuechler (2007)
Vaishnavi & Kuechler's (2007) model has been criticized for being too dependent on
traditional development methods. The suggestion step is the only stage that allows creative
input and is also the only stage separating the model from the mentioned development
methods. However, it is noted that the steps are only suggestions and not absolute
requirements (Vaishnavi & Kuechler, 2007; Grønli & Bygstad, 2009), thus allowing the
project to make changes as deemed necessary.
Hevner et al. (2006) have developed seven guidelines, presented in table 2, to help provide
better understanding and measurements for effective design research projects. Although quite
general, these guidelines are implemented in the same way as Vaishnavi and Kuechler's
(2007) model, allowing the project freedom to decide on implementation. However, it is
advised to address each of the guidelines during the project’s course (Grønli & Bygstad, 2009;
Hevner et al. 2006).
Dissertation Task 2
0834060
Page 19 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Table 2 - Design Research Guidelines by Hevner et al. (2006)
As mentioned earlier, Vaishnavi and Kuechler's (2007) model were used for the overall
project framework and are described in the following section. Hevner et al.'s (2006) seven
guidelines will be used to evaluate and discuss the results of the project, as described in
chapter 5.
3.2 Awareness of problem
The first stage of Vaishnavi & Kuechler's (2007) model was initiated by a general
assumption, that the majority of today’s mobile phones are touch-based and designed for
those with no visual impairment. The assumption was based on the author’s previous
experience from the mobile industry; former projects had demonstrated that the UI is not
always up to standards and hinder effective use of mobile phones.
Once the general assumptions were in place, these needed to be verified by more thorough
research. The initial literature review focused on the mobile market and recent phone releases,
using resources found mainly through Google and later moving on to the major market
analytics companies. With no prior experience related to vision loss, a literature review on
users with vision loss was needed, not only to identify existing solutions for both daily life
and mobile phone use, but to understand more of the experience if vision loss. Through
resources, such as Google and NABP, literature on the most common problem areas was
collected, along with information regarding manufacturers of assistive technology.
3.3 Suggestion
A more thorough literature review was carried out in the suggestion phase, focusing on all
elements and issues regarding the development of assistive technology for people with vision
loss. The literature review was completed in four iterations, each step contributing with more
information regarding issues facing those with vision loss, how people with vision loss use
mobile phones, application compatibility, operating systems to develop for, screen readers
and haptics, and implementation of such technology. The end result was a framework of
guidelines that worked as a source of reference throughout the project.
The work that came out of the literature review supported the earlier assumptions,
highlighting the need for a UI for touch-based phones, designed specifically for those with
visual impairment. The new design would require operation using touch and sound, menu
elements placed in a logical arrangement, and well-defined categories for assistive
Dissertation Task 2
0834060
Page 20 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
functionalities and standard mobile phone functionality.
It was important for the project to provide new functions and improved access for people with
vision loss. From the literature review, several projects with similar solutions came to the
author’s attention. However, the projects relied mainly on gestures and hardware buttons,
functionalities that could make the solutions harder to learn, and that are certainly
incompatible with mobile phone that are not equipped with buttons. Based on the feedback
from these projects, it became evident that the use of gestures should be kept to a minimum
and that the dependency on hardware buttons should be removed.
3.4 Development
This stage involved the development of the solution in addition to documentation and
planning of the project. The Rational Unified Process (RUP) was chosen as the framework for
the development process due to its emphasis on multiple iterations and its clear and defined
guidelines for developing applications (Gornik, 2004; Pollice, 2002). However, time
constraints necessitated a lightweight implementation of RUP, including only core activities.
Nevertheless, this approach is still in accordance with the framework (Pollice, 2002).
RUP requires all objects to start with an inception, where the project vision is defined and
presented to the stakeholders (Pollice, 2002). Stakeholders for the current project include
representatives NABP, Statped and SmartPhones Telecom; the latter is the company
responsible for providing developer resources. To present the vision and the idea in an
intuitive manner, a virtual prototype was created to show a possible solution for replacing a
touch-based mobile’s GUI. The virtual prototype was created in Microsoft Expression Blend
4 with SketchFlow (Microsoft Corporation, 2009), a tool for creating working prototypes of
applications without writing any code.
Further on, RUP dictates an elaboration on the design and a definition of the baseline,
including functionality requirements and possible applications (Pollice, 2002). The virtual
prototype served as a foundation for the outcome of the project and was used to communicate
the idea and the vision to the developers. During several project meetings, discussions
centered on what would be realistic outcomes from the allocated time. The decision was to
create a working UI prototype for people with vision loss, while ignoring the server side
functionality. Hence, the UI would work and behave as the final product, but all data
presented would be static, not dynamic. An early prototype of the application was developed
at this stage, to test core functionality. Complete logs of the project meetings are available in
Appendix G.
Construction is the third step in RUP; this is where the main development takes place (Pollice,
2002). The application was developed in Java for Android, to support Android version 1.6
onwards. Functionalities for the screen reader and haptics were not developed during this
project. Instead, existing modules were implemented with API integration. During the
construction phase, a total of five iterations of development were completed, with a working
prototype coming from each one. Three iterations were for internal use, while two were tested
externally. With each iteration new virtual prototypes, associated documentation, and added
functionalities evolved. Guidelines and best practices for Android development, defined by
Google, were followed through (Google Inc, 2010b; Google Inc, 2010a). Documentation on
the UIs is available in Appendix H in addition to complete development logs in Appendix I.
Dissertation Task 2
0834060
Page 21 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
3.5 Evaluation
The final phase of RUP is the transition phase, where the developed product is tested on real
users (Pollice, 2002). Each version of the UI was tested in three different scenarios, in a
virtual environment, by the developer on a real device, and by the author, who made sure that
all functionalities were implemented according to specifications. In addition, evaluations of
the prototype were performed through two iterations of user experiments, where external
participants tested and provided feedback on the prototypes.
The participants were recruited with assistance from Statped, a Norwegian agency, which
provides guidance to municipalities for supporting people with learning disabilities and vision
loss (Statped, n.d.). All participants had previous experience from volunteering to other
projects aimed at people with vision loss; moreover, before commencing, they were informed
of their rights and of relevant ethical regulations.
Participants all performed the same steps, starting with a general introduction to the project
with its goals and aims, followed by ten minutes of training and some time to become familiar
with the UI, finally performing a couple of exercises and providing feedback and completing
a survey. Each test was performed on a HTC Hero (HTC, n.d.) device, with an average
duration of one hour. Participants were monitored throughout the test. The introduction to the
project emphasized to the participants that the UI was only a prototype and that the aim was to
improve the navigation on touch-based mobile phones, they could therefor expect limitations
and fewer available options.
During the first iteration, participants were trained in operating the UI. They then had to
choose a language for operating the system, either English or Norwegian. They were informed
that the English version would be more advanced and sound more natural than the Norwegian
version. All menus and feedback would reflect the chosen language.
Table 3summarizes the exercise that the participants were asked to perform. The exercise was
designed to evaluate whether the participants were able to understand and navigate the UI on
their own. Instructions were to perform one task at the time and sufficient time was allowed
for each task.
Table 3 - Tasks the participants were asked to perform
During the exercise, the participants’ behavior, responses, reactions and verbal feedback were
documented. The participants were also providing verbal feedback on functions. Feedback
provided included both comments on current functions and suggestions for improvements.
Dissertation Task 2
0834060
Page 22 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
After the exercise, participants were asked to complete a survey. This collected background
information and presented a set of statements for participants to mark their level of agreement
with. From 1, ―strongly disagree‖ to 5 ―strongly agree‖. Statements were grouped in
categories according to the assessed function of the UI. Table 4 presents a summary of the
most important questions from the survey. The complete survey is available in Appendix L.
Table 4 - Survey completed by participants
Data gathered and analyzed in the first user experiment resulted in a new version where the
major issues and concerns uncovered in the first iteration were improved upon. In the first
iteration, a single tap of the finger would state the function of the selected function, while a
second tap would select the function. Although, this served the purpose, the solution caused
frustration among the participants; they pointed to difficulties with tapping the correct area
and mistakenly opening elements. To overcome these issues, the navigation of the UI was
changed so that a single tap would still state the function of an element, but dragging the
finger to the right would open it.
The second iteration also introduced numbering and made changes to the naming of elements.
One set of numbers reflected the elements; current position in a list, while another set
presented the total number of elements in a list. A new list view, for lists with several
elements, was also introduced. The new list introduced a second row of letters, ranging from
A to Z, on the right side of the screen.
Dissertation Task 2
0834060
Page 23 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
With the introduction of the new functions, the participants were asked to perform the same
exercises and survey once more. Additionally, they were asked to test the new list view and
answer a couple of new questions related to the added functionality, as seen in table 5 and 6.
Table 5 - Additional tasks presented to participants
Table 6 - Additional survey questions
3.6 Conclusion
To conclude the research, the data gathered from the two user iterations were categorized and
further reviewed. Important findings from the surveys and the evaluations were analyzed and
documented for further development of the prototype. The results are also presented in this
report; providing new knowledge to the research field of assistive technology and mobile
phone user access for people with vision loss.
Dissertation Task 2
0834060
Page 24 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
CHAPTER 4: RESEARCH RESULTS
The previous chapter presented the selected research method and the steps taken to produce
the results. This chapter presents and evaluates the research results.
4.1 Results in regards to development
Following the Design research model of Vaishnavi and Kuechler (2007), the current project
has gone through the recommended stages in developing an alternative mobile phone UI. The
new UI provides users with a different way of interacting with the phone, compared to the
mobile phone manufacturers’ original indentation. Through the UI, any function or
application can be utilized in an easier and more efficient way, making the phone more
accessible for people with vision loss. However, it is important to note that the applications
need to be compatible with a screen reader to be useful for people with vision loss.
Interaction with the new UI is made possible through two sensory systems, using sound and
tactile feedback. An organized and intuitive menu system provides the user with access to
relevant information and functionalities. The UI is designed in accordance with Nielsen's
(1993) usability principles, and adapted based on the findings from the framework in the
literature review. It also follows Brook's (1995) recommendation in keeping the number of
available functions to a minimum, avoiding potential confusion.
Figure 2 portrays screenshots from the UI running on a mobile phone; the key words represent
the different menus and functions available. The intended audience is people who are either
blind or that have strongly reduced vision; the text is for the benefit of the latter group. The
key words can also serve as reference points for external users, for instance if customer
support is needed. The font size is formatted according to guidelines from (NABP, n.d.).
Dissertation Task 2
0834060
Page 25 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Figure 2 - Some of the menus available in the UI
As mentioned, the UI is operated through sound and haptics. A single tap on the screen
initiates the UI’s screen reader, which states the function of the selected element, while the
gesture ―tap and drag finger‖ executes the element. The gesture was implemented to simplify
the execution of elements, and to reduce the number of incorrect selections. Moreover,
dragging a finger across the screen commands the UI to read out functions and at the same
time makes the phone vibrate when a new item is available. A back element is placed at the
bottom of every screen, with the exception of the main menu, allowing the user to easily
navigate to the previous menu.
To help the user create a mental map of the different menus and elements, the UI will also
state the level it is currently displaying and give feedback when successfully executing an
element. Furthermore, the UI can be customized to read out the selected element’s position on
a list, for example, number three of five.
Longer lists are displayed in the same way as regular lists, only with an added ribbon on the
screens right side, where an alphabetical list of letters is displayed. Figure 3 shows an
illustration of such a list. The letters refer to the initial letter of available elements, which
could be anything from applications to contacts. Dragging a finger across the ribbon causes
the screen reader to name the letters as the finger crosses them.
Figure 3 - List navigation in the UI
Dissertation Task 2
0834060
Page 26 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
In addition to improved accessibility on touch phones, the UI is intended to work as an
assistive aid that can provide useful information, such as time, date and the weather forecast.
The UI is also designed, to provide navigation and to analyze objects or text using the phone’s
camera; however, the features were not implemented in the current version.
The UI was tailored specifically for people with vision loss and it does not depend on existing
functionality or layout. This approach differs greatly from other solutions that typically rely
on a screen reader and the manufacturer’s UI implementation. By creating a new set of menu
elements, the project did not have to focus so much on compatibility issues and could instead
focus on creating new functionality. At the same time, this allowed freedom to customize the
UI and optimize solutions for the visually impaired.
Design features that were of particular importance in the development of the new UI included,
the reduction of required gestures, a minimal learning curve and no reliance on hardware
buttons. The use of gestures was decided to be reduced since they can be hard to master (Amy
K. Karlson et al. 2005; Shaun K. Kane et al. 2008). In addition, by organizing menu elements
in a vertical layout, the UI operation would be similar to that of the Nokia phones, common
among people with vision loss. Finally, the dependency on hardware buttons was
circumvented, as this could result in compatibility issues with certain phone models.
Figure 4 shows one of several virtual prototypes created. Developing a virtual prototype
turned out to be of great advantage, working as an aid in communicating the vision and as a
tool for developers in finalizing and trying out the product. The virtual prototype resided in a
web browser and was operated with a computer mouse. It behaved like the UI developed for
the mobile phone, with fully operating menus and sound. In addition to the virtual prototype,
figure 5 shows a flow map that was created to visualize the different elements and the
relations between menus.
Figure 4 - Conceptual UI prototype for people with vision loss
Dissertation Task 2
0834060
Page 27 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Figure 5 - Flow map for navigation in the UI
The Android OS was chosen as the developmental platform for the UI, a decision based on
several factors. The Android platform is adopted by several phone manufacturers and is
currently the fastest growing mobile OS in the market (The Nielsen Company, 2010; Gartner,
2010a; Comscore, 2010). Hence, products developed for the Android OS have the potential of
reaching out to a large customer base. The Android OS was also a natural choice for the
developers, since it allows anyone to create a new UI for the phone. Furthermore, it is
considered a very open and flexible OS for application development (Ableson, 2009; Google
Inc, 2010a; Google Inc, 2010b).
Figure 6 presents a conceptual overview of the application, developed in Java for Android,
with support for Android version 1.6 and onwards.
Application
UI - View
Base Activity
Code Behind
Modules
Language packs
English
Norwegian
Etc.
TTS Extended
Haptics
Activity 1
Activity 2
Activity 3
Activity X
OnTouchListener 1
OnTouchListener 2
OnTouchListener 3
OnTouchListener X
Figure 6 - Conceptual model of application
Dissertation Task 2
0834060
Page 28 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Base Activity contains standard functionality and provides communication with the external
modules TTS Extended (Eyes-Free Project, n.d.) and Kickback (Ganov, n.d.); both are
modules used for creating voice feedback (screen reader) and vibration (haptics). All feedback
to the user, menus, voice and haptics are provided through functions called Activities. Each
Activity has an OnTouchlistener, which measures where and how the user is tapping on the
screen. All menu elements reside in XML format, which can easily be translated to different
languages. The current version supports English and Norwegian, but other languages can be
added as appropriate.
4.2 Results in regards to testing
Two iterations of user testing were carried out. A total of four people participated in the first
iteration, three women and one man with an average age of 50 years; a total of five people
took part in the second iteration, the same four with an extra man, making the average age
49.4. As mentioned, statistics from World Health Organization (2009), show that women over
50 make up the largest share of the world’s blind population; thus the project’s sample is
representative of this population. Of the participants, three were blind, one was diagnosed
with very low vision, although her interaction could indicate complete vision loss, the final
participant had low vision and could see objects in very close proximity.
According to Nielsen and Landauer (1993), only a small number of people are required for
usability testing; in fact five people should be sufficient to obtain adequate results (Richtel,
1998). Nielsen (2000) states that such a small number of users will provide better results than
a larger number; largely due to limited project budgets, the advantage of running several
smaller compared to one large test. This notion is in accordance with Design research, which
recommends several iterations of user testing.
The user tests were planned according to usability guidelines from Nielsen (1993), with
usability measured relative to certain users and certain tasks, and where every test should
define a representative and measurable set of tasks relevant to the users. For consistent
measurements, a survey should be completed subsequently. The mean value of the measured
attributes should exceed a specific minimum; on a Likert scale ranging from 1 to 5, the mean
value should be at least 4 (Nielsen & Levy, 1994) and 50% of participants should provide the
score of 5 (Nielsen, 1993). With two iterations of user testing, the ratings from the two
surveys can be compared to evaluate whether the improvements affected usability ratings and
if further improvements are still required (Nielsen, 1993).
Survey questions were categorized to the features they were set to evaluate, these are listed in
Table 7. ―Menu system‖ and ―The solution‖ are considered the two most important categories,
as they measure how well the UI works and the success of the solution. The participants
received the same set of questions in both rounds.
Dissertation Task 2
0834060
Page 29 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Table 7 – Summary of survey categories
Figure 7 presents the results from round one and two, with an overview of the mean scores for
each functionality category. Several questions make up a category, thus the mean scores are
averaged across questions as well as participants.
Comparing components in the UI
Average score
5,0
4,0
3,0
2,0
1,0
Menu
system
Phone
Navigation
Round 1
3,9
4,4
4,1
4,0
4,3
2,3
Round 2
4,5
4,7
4,7
4,7
4,8
4,3
Applications Information The solution
Figure 7 - Graph displaying mean scores from the first and second round of testing
The difference between mean scores from round one and two clearly shows responses were
more positive in round two, where mean were higher than four for all categories. The two
categories of particular interest, ―Menu system‖ and ―The solution‖ both presented fairly poor
feedback in the first round, with initial mean scores as low as 2.3 for ―The solution‖ and 3.9
for ―Menu system‖. According to Nielsen and Levy's (1994) criteria, these low scores would
constitute a project failure. However, round two of testing provided a substantial increase in
positive feedback; thus, it can be concluded that the solution tested in round two is more
efficient and better received among the participants.
Dissertation Task 2
0834060
Page 30 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Figure 8 shows the results from the individual questions for the ―Menu system‖ category. The
mean scores illustrate the changes in the participants reaction between the first and second
iteration.
Average score
Menu system
5,0
4,0
3,0
2,0
1,0
The vibration
The
made it
categorizatio
easier to
n of subchange
menus were
between
logical
menus
The menu
system was
easy to use
The system
made the
touch phone
easier to use
The spoken
options were
easy to
understand
It was easy to
navigate
between
menus and
sub-menus
Round 1
4,0
3,7
4,3
2,5
4,3
4,5
Round 2
4,6
4,6
4,6
4,6
3,6
4,8
Figure 8 - Graph displaying a comparison between results from first and second round
of testing on the menu system
The results show an increase in scores for all but one question, indicating that the second
menu system received a better acceptance than the first version. The reduction in scores for
the questions relating to the vibration function was clarified through verbal feedback from
participants. In the first round of testing, a greater reliance on haptic feedback was required to
navigation; however, in the second round of testing, the improvements facilitated the auditory
feedback and participants chose to rely more on sound than touch. These results are consistent
with findings from Rassmus-Gröhn (2006), who found that people tend to rely more on the
sense they are accustomed to.
Dissertation Task 2
0834060
Page 31 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Figure 9 presents results from the individual questions for the solution category. The mean
scores portray participants acceptance of the solution for rounds one and two.
Average score
Acceptance of the solution
5,0
4,0
3,0
2,0
1,0
I personally felt that the
menu system enabled and
improved my use of the
mobile phone
I prefer this solution above
others*1
I would use this solution in
my daily life*2
Round 1
2,3
2,5
2,3
Round 2
4,6
4,0
4,3
*1 Three participants did not respond due to no prior experience with solutions for touch screens
*2 One participant did not respond due to no prior experience with touch screens to compare against
Figure 9 - Graph displaying a comparison between results from first and second round
of testing on the complete solution
The results show an increase in mean scores for all questions, indicating that the whole
solution received a better acceptance in the second round of testing. It should be noted that
some participants decided not to answer the second and third question, feeling that they
lacked the experience to give an informed response. However, all participants responded to
the most important question, ―I personally felt that the menu system enabled and improved
my use of the mobile phone‖, with a great increase in positive feedback.
While the Design Research method does not require statistical analyses, these were
nevertheless carried out to shed more light on the changes in scoring that were evident
between the two versions of the UI. Effect sizes and differences between means were
evaluated across the categories previously outlined. Due to the small sample size, a certain
measure of leniency with respect to level of significance was judged necessary; this was
therefore set to 0.1. Thus mean scores, available in figure 7, were found to be significantly
higher for the second round of testing, compared to the first round, for the navigation
functions (t(3) = 2.45, p>0.1), for the information functions (t(3) = 2.45, p>0.1), and for the
solution functions (t(3) = 5.44, p>0.05). Effect sizes were judged to be high for all three
functions (r = 0.41; r = 0.40; r = 0.89; respectively). Effect sizes were similarly high for the
menu functions (r = 0.37) and the application functions (r = 0.41), but the differences between
means were non-significant (t(3) = 1.47, ns; t(3) = 1.48, ns; respectively). The remainder of
the analyses is included in Appendix M.M.
Dissertation Task 2
0834060
Page 32 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Nielsen (1993) suggests that participants should be asked for their subjective opinions, to
better provide an understanding of their satisfaction. Participants were asked to state their
thoughts and suggestions to improvements, following each round this feedback was used to
improve the application further. Feedback from round one is available in Appendix M.A,
while a complete list of feedback from round two is available in Appendix M.F. The most
informative comments from round two are summarized in Table 8.
Table 8 - Table showing subjective feedback from round two
The positive feedback from participants shows how much they appreciated the second
iteration of the solution; this is consistent with the survey results. The negative feedback
mainly focuses on the new functionality introduced in the second iteration, indicating that the
issues encountered in the first iteration had been solved and that a third iteration should aim at
solving the new problems. Comments pointing to the inadequacy of the vibration result from
the over-all improvements to the solution causing participants to shift their attention to the
voice, where the participants paid more attention. Participants’ suggestions for improvements
are reasonable and well thought through and should certainly be considered in a third
iteration.
Dissertation Task 2
0834060
Page 33 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
CHAPTER 5: DISCUSSION
This chapter presents a critical discussion, comparing the findings from the literature review
with the results from the evaluation of the UI, as shown in the previous chapter. To evaluate
the collected result, the seven step model from Hevner et al. (2006) will guide the discussion
and evaluation of the outcome of the project. While the model recommends that a project
evaluation follows these steps, it also emphasizes that each project should make its own
judgment regarding the implementation.
5.1 Design as an Artifact
The first guideline in (Hevner et al.'s (2006) model is to create an artifact; this might involve
all models and applications developed throughout a project´s life cycle. Several artifacts were
created in this project; start with the virtual prototype. The virtual prototype served as a way
of communicating the vision to the stakeholders and developers and offered the advantage of
being able to easily create a working application to try out. The virtual prototype was updated
for each new version of the UI, to reflect and communicate changes. The importance of
developing a virtual prototype was clear from the beginning of the project, as experience
showed it to be an efficient means for clarifying ideas to stakeholders and developers.
In addition to the virtual prototype, other important artifacts include the documentation, the
manual, and the conceptual model of the UI. However, the most significant artifact was the UI
for touch-based mobile phones. A total of five versions were developed, three for internal
testing and two for external evaluation. As presented in the research results chapter, the UI
received positive feedback from the participants.
The development of the UI followed findings from the literature review, with a framework
that pointed out several factors for improvement and experience from previous solutions to
learn from.The decision to design the UI for the Android OS, was based on reports from The
Nielsen Company (2010) and Gartner (2010a), which indicated that the Android OS is the
fastest growing mobile OS. Key considerations for the new solution included minimal use of
gestures (Amy K. Karlson et al. 2005; Shaun K Kane et al. n.d.), replacement of the native UI,
providing independence from phone manufacturers (Amy K. Karlson et al. 2005; Amar et al.
2003; Strumillo et al. 2009; C. Chen & Raman, 2009), and no reliance on physical keys,
making the solution compatible to all Android based mobile phones.
Unlike the other implementations, the menu system was inspired by the layout of Nokia based
mobile phones with vertical navigation, in an attempt to smooth the transition for participants
currently using Nokia phones. Moreover, to improve navigation, a feature was implemented
to allow users to find available elements by tapping anywhere on the screen (Amar et al.
2003).
A potential weakness for the proposed solution is the fact that it only works as a UI. Although
the literature review indicated several factors that could improve the experience for people
with vision loss, the current prototype only provides a means for easy access to touch-based
mobile phones. However, the solution cannot be applied to text-writing or web-browsing.
Thus, the solution is just scratching the surface of assistive aid solutions. Furthermore,
applications launched by the UI will need to be coded correctly to work for people with vision
loss. The fact that the current solution replaces the phone’s factory UI, might make it
uninteresting for certain users, some may prefer to preserve the original UI and rather use a
dedicated screen reader.
Dissertation Task 2
0834060
Page 34 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
5.2 Problem relevance
The second guideline involves the development of a solution that solves a business problem.
After a thorough review of the mobile phone industry and currently available solutions for
people with vision loss, findings confirmed that touch-based mobile phones are not designed
for this group. With the majority of newly developed phones support touch capability
(Gartner, 2010b), a clear business opportunity has presented itself.
Solutions to make touch phones accessible are first and foremost screen readers and dedicated
UIs. However, as pointed out in the literature review, screen readers alone will not provide the
necessary support (Babinszki, 2010). Commercial screen readers are incompatible with both
the Android and the iPhone platform (Code Factory, n.d.). As mentioned, earlier solutions
exist only on a research level, with the exception of the open source initiative Eyes-Free Shell
(C. Chen & Raman, 2009) still; this solution has its limitations.
With regulations set in motion, manufacturers will soon be forced to create mobile phones
that are accessible for everyone (Wall, 2003; Steria, 2009). Thus the continued development
of the UI might prove to have commercial value.
5.3 Design evaluation
With the third guideline, artifacts should be evaluated using appropriate methodology and
relevant conclusions drawn from the findings. As previously mentioned, both internal and
external testing was conducted in order to measure the effectiveness of the artifacts.
Internal testing was performed over the course of three iterations, where each new version
was tested in an emulator, on a running device, and by the project team. Bugs and errors were
entered into a source tracking tool, which monitored all changes made to the code, as well as
added functionality introduced by the ever increasing literature review.
However, internal testing could not provide sufficient feedback on its own. Hence, two UI
versions were made for external users; the first was not considered adequate, but participants
indicated satisfaction with the second version. Both verbal feedback and survey results
suggested that participants would use such a solution. Yet, some negative feedback and
suggestions for improvements were recorded. Given that the UI is a prototype still under
development, this feedback will be used to further improve the solution and expand the
feature sets in coming iterations.
With only four participants in the first iteration, in contrast to the five recommended by
Nielsen and Landauer (1993), the number may have been too low to achieve significant
results. However, in order to follow the strict schedule set for the project, their feedback was
considered sufficient. Based on the feedback from round two of testing, where the participants
deemed the solution a success, the decision seems justified.
With the introduction of a fifth participant, not only did the project meet the recommended
number of participants, but the positive responses offered by the late-comer corresponded to
that of the first four. This would rule out the possibility that participants gave higher scores
because they had grown accustomed to the solution.
Another potential criticism is the use of older participants. However, the sample was
representative of the potential user group; according to WHO (2009), the majority of people
Dissertation Task 2
0834060
Page 35 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
with vision loss are at the age of 50 or older. Still, future versions of the UI should include a
younger sample to collect feedback from all potential users.
It was mentioned in the literature review that the screen size should be of adequate size (Plos
& Buisine, 2006; Smith-Jackson et al. 2003); however, actual size was not pointed out. The
phone used for testing (HTC, n.d.) had a screen size of 2,8‖, which should be sufficient for
most users, especially with larger font sizes. However, it would be interesting to investigate
whether a smaller or larger screen size would change the outcome of the study.
5.4 Research contributions
The literature review uncovered missing options for people with vision loss, in regards to the
use of mobile phones. Thus, the outcome of this project should be highly relevant in this area
of research. Based on existing knowledge, a new solution was developed to aid this user
group and the findings were evaluated based on subjective feedback. All results have been
documented, ensuring that future projects can leverage on current findings.
5.5 Research rigor
Comprehensive methodology is required both during and after the construction of artifacts to
verify results, a process ensured through the use of RUP. This framework was chosen based
on its guidelines and procedures that emphasize the importance of producing several iterations
of an artifact (Gornik, 2004), consistent with the practices from Design research (Vaishnavi &
Kuechler, 2007).
Careful consideration went into planning and designing the UI, with guidance from wellknown usability experts like Nielsen (1993) and Brooks (1995), along with a thorough
literature review.
5.6 Design as a Search progress
Desired results should be achieved through appropriate methods. Design research was applied
to the current project, following the model from Vaishnavi and Kuechler (2007). This model
puts emphasis on the process of defining a problem and searching for existing solutions;
furthermore, it recommends a continued search for literature as the artifacts are developed
through multiple iterations. The search for literature went through several sources, ranging
from academic papers and online news articles on the web to general resources regarding
vision loss.
The work of literature grew as the iterations progressed, ensuring an ever-expanding resource
to build future versions on. The search also uncovered new topics, revealing how touch-based
phones may also be used as assistive aids.
In addition to the literature review, the results from the user evaluations provided the
background for further improvements; this resulted in the second version of the UI for user
testing.
5.7 Communication of research
The last guideline emphasizes the importance of presenting the outcome in an efficient
manner, both to a technical and a management oriented audience. Hence, this dissertation is
written in a clear and consistent language, it explains technical terms for a management
audience, and provides useful information for a technical audience. Great care and attention to
detail has been put into documenting the results, as well as documenting and demonstrating
the UI, as shown with the virtual prototype. In addition, the report is submitted as part of a
Dissertation Task 2
0834060
Page 36 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Master’s degree, making it available through the university’s system.
5.8 Summary of discussion
The literature review concluded that today’s phones are not intended for people with vision loss,
due to their use of touch screens that require visual navigation. On button-operated phones, the
simplified menus allow screen readers to be enabled as alternative means of operation. However,
a touch screen operates with a more complicated menu and correct voice representation become
very challenging.
By leveraging on the methodology from Design research, an alternative UI was developed to
replace the phone’s own menu system, enabling the operation of touch-based phones for people
with vision loss. The development process started with a virtual prototype, which demonstrated
the finished product. A total of five iterations of development followed, where two were tested
on external participants.
Of the two versions tested, the first was considered a failure while the second was deemed a
success; users even commented that they would use the product if it was made commercially
available. The experience from the testing sessions emphasize the importance of receiving
external feedback, indicating that Design research is an efficient method for developing new
solutions.
Dissertation Task 2
0834060
Page 37 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
CHAPTER 6: CRITICAL EVALUATION OF RESEARCH
The chapter provides a critical evaluation of the aims, objectives and results presented in the
dissertation. These are presented in the overview in Table 9.
Table 9 - Overview on aims and objectives
The dissertation report was designed like a project, with two successful outcomes, the
dissertation with associated research, and the external development of the UI. In order to
complete the project in the limited time available, parallel processes were defined for each
project, including milestones and tasks. Due to the involvement of external resources, a
separate project was defined for their purpose; this tracked the progress of the development.
Project meetings, progress reports and a bug tracking system ensured that all parties involved
were kept up to date.
The aim of the project was to find a solution that enables people with vision loss to operate
mobile phones with touch screens, and create a new UI that simplifies such phones and make
them accessible for this group. This was accomplished through the development of five
versions, each an improvement on the previous.
Objective 1
The first objective was to perform a literature review. However, with no prior encounter with
people with vision loss, or any knowledge regarding assistive aids, a comprehensive literature
research was needed to better understand the needs of the visually impaired.
Throughout the research process, several areas were investigated, ranging from social aspects
to actual products; the resulting literature review covers the areas of most importance. The
author believes he has learnt a lot about life without vision, not only from reading articles, but
from talking to actual people with vision loss.
An investigation of the mobile industry was not grated high priority due to the author’s prior
experience from the telecom industry. For the past 11 years he has worked in a company on
the forefront in providing Norwegian companies with new technology.
Although the literature review is comprehensive, several of the sources are from online
articles. Most academic papers were not up to date in regards to mobile technology. This
aspect is important when determining the market’s current options and the rapid succession of
new phone models, but makes it impossible for academic journals to stay updated. In regards
Dissertation Task 2
0834060
Page 38 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
to assistive aid, several papers presented developed solutions, but usually referred to older
technology.
Objective 2
A framework was designed based on the literature findings, creating the basis for the
development of the UI. Originally, the intention was to create a solution that covered a much
larger area, not only for accessibility, but also as an assistive aid. Hence, the literature review
covers a broader area than the framework, which is designed according to the aim of the
project.
Objective 3
Five participants took part in the evaluation of the UI, which ran over two iterations. Based on
the feedback, the second version received a tremendous increase in positive feedback
compared to the first; the final version was therefore considered a success. Evaluation was
based on a survey, an informal interview, and on observation; this ensured a large set of data
to base the conclusions on.
Only four people were able to participate in the first version, while five participated in the
second. However, due to the time restrictions this was considered sufficient. Based on the
feedback from the second version, the decision seemed justified as the first round resulted in
an improved solution. It also ruled out the possibility of users voting in favor of the system, as
the new participant provided the same positive feedback as the rest. Future iterations should
also include a younger participant group, to obtain feedback from all potential users.
Objective 4
The last objective was to present a discussion on results, drawing on the literature and
assessing the UI and research results. The seven-step model from Hevner et al. (2006) a guide
specifically designed for design research projects was implemented, ensuring that relevant
aspects of the project were highlighted.
Dissertation Task 2
0834060
Page 39 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
CHAPTER 7: CONCLUSION
The final chapter concludes with a summary of the previous discussions, followed by an
overview of contributions to the existing research field, along with future research
suggestions.
7.1 Summary of the dissertation
This dissertation has investigated the issue of the inaccessibility of today’s modern mobile
phones for people with vision loss. Through an extensive literature review, an in-depth overview
of issues and rights facing people with vision loss has been presented. Furthermore, an
evaluation of the current mobile market and available solutions and technology followed. It was
found that neither the society, nor the manufacturers of products and services, is designing for
people with vision loss. Hence, this user group is denied the benefits these products offer.
The literature review pointed out that most modern mobile phones require visual navigation, to
operate the touch-based screens. Although mobile phones are accessible through the use of
applications called screen readers, those currently on the market are inefficient and difficult to
use with touch screens.
Hence, this project set out to find a new solution, aiming to make touch-based mobile phones
accessible for people with vision loss. With Design research used as methodology for the overall
project, a UI was created. It was designed to replace the phone’s own UI and to provide an easy
and intuitive way of operating a mobile phone. Design research also emphases the importance of
developing a solution over several iterations, and involving external participants for product
evaluation. By using voice and haptic feedback, and a menu system similar to most Nokia
phones, the proposed UI was evaluated to be an effective solution that most of the participants
would use if it became commercially available.
The ideas presented in this dissertation are not unique. Previous research projects have proposed
other solutions, ranging from gesture based navigation or mapping the phone keys to perform
other tasks, to creating a new UI for easier operation of the phone. However, what is unique for
the current proposal is the combination of other ideas put into a new and user-friendly UI. Thus
taking the best from previous research and presenting a solution that focuses on providing a
menu layout which is both easy and intuitive to operate, in addition to providing access to all
relevant applications and functions on the mobile phone.
In summary, the dissertation has covered the following topics:
Issues people with vision loss encounter on a daily basis.
An overview of the mobile market, what is available, the most popular mobile OS’s, and
a look at touch-based navigation.
Presentations of assistive aids and technologies available for people with vision loss,
such as; screen readers, input of text, haptics, compatibility issues, and how to provide a
better UI.
Creation of a framework, used for designing a new UI.
Design research as a methodology for developing applications, with demonstration of the
effectiveness of the method.
The processes involved in developing the UI, resulting in five iterations, each with a new
version.
Dissertation Task 2
0834060
Page 40 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Android OS was used as the development platform, currently the fastest growing mobile
OS on the market.
The UI was designed to be both intuitive and easy to use, with focus on keeping gestures
to a minimum and with a menu users can relate to.
No reliance on physical keys ensures that the UI is compatible with all mobile phones
running the Android OS.
Research findings from two of the iterations, evaluated by external participants. The first
iteration was considered a failure, while the second was considered a success, receiving
only positive scores and feedback.
Discussion covering the different aspects of the research findings.
In conclusion, the dissertation proposed a new UI for touch-based phones, providing an
easy and intuitive way of operating such phones.
7.2 Future research and development
Although the presented UI received only positive feedback and was judged a success, it is only a
prototype and by no means a finished product. The research results show that there are several
aspects which can be further investigated and improved.
Future development should take into consideration the comments and feedback reported during
the last iteration and should also include a younger user base, as this group will provide a broader
set of feedback. Moreover, attention should be given to technical users, since they might find the
current solution too simple. Added functionality should also be investigated, looking at
efficient means for writing text or surfing the web. To make further use of the potential of the
mobile phone, assistive aids, such as navigation from A to B and analysis of objects, could
provide great benefits for this user group.
Future research should look into how the mobile phone can be implemented for assistive living,
or leverage on augmented reality and GPS positions, to better present intelligible content and
information based on current location. Other uses for the UI would also be interesting to
explore; for instance, easier and safer operation of mobile phones while driving a car.
Dissertation Task 2
0834060
Page 41 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
REFERENCES
Abascal, J. & Civit, A., 2001. Universal access to mobile telephony as a way to enhance the
autonomy of elderly people. Workshop on Universal Accessibility of Ubiquitous
Computing Proceedings of the 2001 EC/NSF workshop on Universal accessibility of
ubiquitous computing: providing for the elderly, pp.93-99.
Ableson, F., 2009. Introduction to Android development. IBM. Available at:
http://www.ibm.com/developerworks/opensource/library/os-android-devel/ [Accessed
January 23, 2011].
AFB, a. American Foundation for the Blind - Home Page. Available at: http://afb.org/
[Accessed October 24, 2010].
AFB, b. Reading and Writing. American Foundation For The Blind. Available at:
http://afb.org/Section.asp?SectionID=40&TopicID=200 [Accessed August 15, 2010].
AFB, c. Speech Systems. American Foundation for the Blind. Available at:
http://www.afb.org/Section.asp?SectionID=4&TopicID=31&DocumentID=1284
[Accessed August 16, 2010].
AFB, d. Web-Braille from National Library Service. American Foundation for the Blind.
Available at:
http://afb.org/Section.asp?SectionID=40&TopicID=200&DocumentID=1695 [Accessed
August 15, 2010].
Amar, R. et al., 2003. Mobile ADVICE: an accessible device for visually impaired capability
enhancement. In CHIʼ03 extended abstracts on Human factors in computing systems.
ACM, p. 919.
American Printing House for the Blind, 2010. Hall of Fame: Father Thomas Carroll. Hall of
Fame Leaders and legends of the blindness field. Available at:
http://www.aph.org/hall_fame/bios/carroll.html [Accessed August 14, 2010].
Anon, BlindType - Touch typing the way it should be. Available at: http://blindtype.com/
[Accessed September 24, 2010].
Babinszki, T., 2010. How Do Blind People Use Mobile Phones. Even Grounds. Available at:
http://www.evengrounds.com/blog/how-do-blind-people-use-mobile-phones [Accessed
September 19, 2010].
Berge, A.R., 2007. Fra skole og studier til jobb eller uføretrygd?, Rehab-Nor.
Bigham, J.P., Prince, C.M. & Ladner, Richard E, 2008. WebAnywhere : Enabling a Screen
Reading Interface for the Web on Any Computer WebAnywhere System. In Proceedings
of the 2008 international cross-disciplinary workshop on Web accessibility (W4A) - W4A
’08. pp. 1159-1160.
Bojo AS, knfbReader. Available at: http://bojo.no/650001 [Accessed January 4, 2011].
Dissertation Task 2
0834060
Page 42 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Brooks, F.P., 1995. The Mythical Man-Month: Essays on Software Engineering Anniversar.,
Addison-Wesley Professional.
Brush, A. et al., others, 2010. User experiences with activity-based navigation on mobile
devices. In Proceedings of the 12th international conference on Human computer
interaction with mobile devices and services. ACM, p. 73–82.
Buxton, B. et al., 2008. Big data: the next Google. Interview by Duncan Graham-Rowe.
Nature, 455(7209), pp.8-9.
Calabrò, A., Contini, E. & Leporini, B., 2009. Book4All: A Tool to Make an e-Book More
Accessible to Students with Vision/Visual-Impairments. HCI and Usability for eInclusion, p.236–248.
Chen, C. & Ganov, S., 2009. TalkBack: An Open Source Screenreader For Android.
Available at: http://google-opensource.blogspot.com/2009/10/talkback-open-sourcescreenreader-for.html [Accessed January 4, 2011].
Chen, C. & Raman, T.V., 2009. Announcing Eyes-Free Shell For Android. Available at:
http://google-opensource.blogspot.com/2009/04/announcing-eyes-free-shell-forandroid.html [Accessed January 5, 2011].
Clark, A., 2007. Apple reaps reward for runaway success of iPhone. The Guardian. Available
at: http://www.guardian.co.uk/technology/2007/oct/23/apple.iphone/print [Accessed May
6, 2010].
Code Factory, Introducing Mobile Speak. Available at:
http://www.codefactory.es/en/products.asp?id=316 [Accessed August 27, 2010].
Colenbrander, A., 2002. Visual standards. Aspects and Ranges of Vison loss with Emphasis
on Population Surveys, Sydney.
Comscore, 2010. comScore Reports May 2010 U.S. Mobile Subscriber Market Share.
Available at: http://www.prnewswire.com/news-releases/comscore-reports-may-2010us-mobile-subscriber-market-share-98031904.html [Accessed August 7, 2010].
Coughlan, J. & Manduchi, R., 2009. Functional Assessment of a Camera Phone-Based
Wayfinding System Operated By Blind and Visually Impaired Users. International
journal of artificial intelligence tools : architectures, languages, algorithms, 18(3),
pp.379-397.
Darilek, N., 2010. Spiel: Features. Available at: http://spielproject.info/wiki?name=features
[Accessed January 4, 2011].
Darling, P., 2010. Intel and Nokia Create First Joint Laboratory. Available at:
http://newsroom.intel.com/community/intel_newsroom/blog/2010/08/23/intel-and-nokiacreate-first-joint-laboratory [Accessed January 4, 2011].
ECON, 2003. Funksjonshemmede og arbeid. En kartlegging av situasjonen for synshemmede,
hørselshemmede og rullestolbrukere, Econ Pöyry AS.
Dissertation Task 2
0834060
Page 43 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Eriksen, E., 2010. Windows phone 7: lek eller alvor? amobil.no. Available at:
http://www.amobil.no/artikler/windows_phone_7_lek_eller_alvor/78155 [Accessed
September 6, 2010].
Eyes-Free Project, Text-To-Speech Extended. Available at:
http://www.androlib.com/android.application.com-google-tts-iDB.aspx [Accessed
November 22, 2010].
Freedom Scientific, JAWS for Windows Screen Reading Software. Available at:
http://www.freedomscientific.com/products/fs/jaws-product-page.asp [Accessed January
6, 2011].
Fukuda, K. et al., 2005. Proposing new metrics to evaluate web usability for the blind. CHI
’05 extended abstracts on Human factors in computing systems - CHI ’05, pp.13871390.
Ganov, S., Kickback. Available at: http://www.androlib.com/android.application.com-googleandroid-marvin-kickback-FExn.aspx [Accessed November 22, 2010].
Gartner, 2010a. Gartner Says Android to Become No. 2 Worldwide Mobile Operating System
in 2010 and Challenge Symbian for No. 1 Position by 2014. Available at:
http://www.gartner.com/it/page.jsp?id=1434613 [Accessed January 5, 2011].
Gartner, 2010b. Gartner Says Worldwide Mobile Phone Sales Grew 17 Per Cent in First
Quarter 2010. Available at: http://www.gartner.com/it/page.jsp?id=1372013 [Accessed
August 10, 2010].
Gemperle, F., Ota, N. & Siewiorek, D., 2001. Design of a wearable tactile display.
Proceedings Fifth International Symposium on Wearable Computers, pp.5-12.
Gomnæs, S., 2005. Bruker ikke funksjonene. amobil.no. Available at:
http://www.amobil.no/artikler/bruker_ikke_funksjonene/16353 [Accessed September 5,
2010].
Google, Google Goggles for Android. Available at:
http://www.google.com/mobile/goggles/#text [Accessed August 29, 2010].
Google Inc, 2010a. Android User Interface Guidelines. Available at:
http://developer.android.com/guide/practices/ui_guidelines/index.html [Accessed August
29, 2010].
Google Inc, 2010b. The Developerʼs Guide | Android Developers. Available at:
http://developer.android.com/guide/index.html [Accessed November 21, 2010].
Gornik, D., 2004. IBM Rational Unified Process: Best practices for software development
teams. Rational Software White Paper TP026B, Rev.
Grossman, L., 2007. Invention Of the Year: The iPhone - The Best Inventions Of 2007. Time.
Available at:
Dissertation Task 2
0834060
Page 44 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
http://www.time.com/time/specials/2007/article/0,28804,1677329_1678542_1677891,00
.html [Accessed May 6, 2010].
Grønli, T.-M. & Bygstad, B., 2009. Innovation in Mobile Services - a Design Research
Approach. In S. Love, ed. Handbook of Mobile technology Research Methods. New
York: Nova Science Publishers, p. 176.
Helft, M., 2009. For the Blind, Technology Does What a Guide Dog Can’t. The New York
Times. Available at: http://www.nytimes.com/2009/01/04/business/04blind.html
[Accessed January 5, 2011].
Helland, R., 2003. Øyetelefon for blinde. NRK. Available at:
http://www.nrk.no/helse_forbruk_og_livsstil/1.1313559 [Accessed February 16, 2010].
Hevner, A.R. et al., 2006. Design science in information systems research.
Wirtschaftsinformatik, 11(4), pp.342-135.
Holzer, A. & Ondrus, J., 2010. Mobile application market: A developer’s perspective.
Telematics and Informatics, (2010), pp.1-10.
HTC, a. HTC Hero. Available at: http://www.htc.com/uk/product/hero/overview.html
[Accessed January 9, 2011].
HTC, b. HTC Sense. Available at:
http://www.htc.com/europe/press.aspx?id=127750&lang=1033 [Accessed August 16,
2010].
HumanWare, a. BrailleNote. Available at: http://www.humanware.com/eneurope/products/blindness/braillenotes [Accessed September 19, 2010].
HumanWare, b. Maestro handheld accessible computer. Available at:
http://www.humanware.com/eneurope/products/blindness/handheld_computers/_details/id_28/maestro.html [Accessed
September 19, 2010].
IDC, 2010. Worldwide Converged Mobile Device (Smartphone) Market Griws 56.7% Year
Over Year in First Quarter of 2010, Says IDC. Available at:
http://www.idc.com/getdoc.jsp?containerId=prUS22333410 [Accessed May 11, 2010].
International Agency for the Prevention of Blindness, 2010. International agency for the
prevention of blindness., London.
Joseph, C., 2009. Challenges of Being Blind. eHow. Available at:
http://www.ehow.com/about_5185162_challenges-being-blind.html [Accessed August
14, 2010].
Kane, S.K. et al., 2009. Freedom to roam: a study of mobile device adoption and accessibility
for people with visual and motor disabilities. In Proceeding of the eleventh international
ACM SIGACCESS conference on Computers and accessibility. ACM, p. 115–122.
Dissertation Task 2
0834060
Page 45 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Kane, Shaun K et al., Freedom to Roam : Mobile Device Opportunities and Challenges for
People with Visual and Motor Impairments. Challenges.
Kane, Shaun K., Bigham, J.P. & Wobbrock, Jacob O., 2008. Slide rule. Proceedings of the
10th international ACM SIGACCESS conference on Computers and accessibility - Assets
’08, p.73.
Karampelas, P. & Akoumianakis, D., C, 2003. User interface design for PDAs: Lessons and
experience with the WARD-IN-HAND prototype. , Practice, and Experience, pp.474485.
Karlson, Amy K., Bederson, B.B. & SanGiovanni, J., 2005. AppLens and launchTile.
Proceedings of the SIGCHI conference on Human factors in computing systems - CHI
’05, p.201.
Kelly, K., 2010. The Master Planner. Wired Magazine, iPad edition, 8(18).
Kharif, O., 2010. Qualcomm, AT&T Move in on ―M-Health.‖ Bloomberg Businessweek.
Available at:
http://www.businessweek.com/technology/content/aug2010/tc20100823_511801.htm?lin
k_position=link1 [Accessed August 27, 2010].
Loftås, B.E., 2010. Google Scribe. Dinside.no. Available at:
http://m.dinside.no/php/art.php?id=853173 [Accessed January 4, 2011].
LookTel, What is LookTel? Available at: http://www.looktel.com/ [Accessed August 29,
2010].
Maines, S., 2008. White Cane Walk makes visible the daily challenges of blindness. The
Lawrence Journal-World. Available at:
http://www2.ljworld.com/news/2008/oct/19/white_cane_walk_makes_visible_daily_chal
lenges_bli/ [Accessed August 14, 2010].
Malinowski, E., 2010. For blind soccer stars, field of vision is overrated. Wired. Available at:
http://www.wired.com/playbook/2010/08/blind-soccer/ [Accessed August 27, 2010].
March, S.T. & Smith, G., 1995. Design and natural science research on information
technology. Decision Support Systems, 15, pp.251-266.
Meijer, P.B.L., The vOICe for Android - Augmented Reality for the Blind. Available at:
http://www.seeingwithsound.com/android.htm [Accessed August 29, 2010].
Meyers, M., 2008. Target settles with blind patrons over site accessibility. CNET News.
Available at: http://news.cnet.com/8301-1023_3-10028109-93.html [Accessed January 5,
2011].
Microsoft Corportation, 2009. Expression Blend 4.
Dissertation Task 2
0834060
Page 46 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Mlauf, 2010. Serotek Corporation Announces the Release of DocuScan Plus. SeroTalk.
Available at: http://www.serotalk.com/2010/11/24/serotek-corporation-announces-therelease-of-docuscan-plus/ [Accessed January 4, 2011].
NABP, a. English info — Forside. Available at:
https://www.blindeforbundet.no/internett/english-info [Accessed October 24, 2010].
NABP, b. Hjelpemidler. Available at:
https://www.blindeforbundet.no/internett/tilrettelegging-i-samfunnet/hjelpemidler
[Accessed August 15, 2010].
NABP, c. Tilgjengelige websider for synshemmede. Available at:
https://www.blindeforbundet.no/internett/tilgjengelighet/internett-for-brukere [Accessed
January 4, 2011].
Neset, T., 2010. Mobil har gått forbi PC. ITavisen. Available at:
http://www.itavisen.no/852360/mobil-har-gaatt-forbi-pc [Accessed October 24, 2010].
Nielsen, J., 1993. Usability engineering 1st ed., Morgan Kaufmann.
Nielsen, J., 2000. Usability Testing with 5 Users (Jakob Nielsenʼs Alertbox). Jakob Nielsenʼs
Website. Available at: http://www.useit.com/alertbox/20000319.html [Accessed
December 16, 2010].
Nielsen, J. & Landauer, T.K., 1993. A mathematical model of the finding of usability
problems. In Proceedings of the INTERACT93 and CHI93 conference on Human factors
in computing systems. ACM, pp. 206-213.
Nielsen, J. & Levy, J., 1994. Measuring usability: preference vs. performance.
Communications of the ACM, 37(4), pp.66-75.
Noyes, K., 2010. Googleʼs Blind Type Buy Will Benefit Android Users. PCWorld. Available
at:
http://www.pcworld.com/businesscenter/article/206892/googles_blind_type_buy_will_b
enefit_android_users.html [Accessed January 4, 2011].
Nusca, A., 2010. Smartphone vs. feature phone arms race heats up; which did you buy?
Available at: http://www.zdnet.com/blog/gadgetreviews/smartphone-vs-feature-phonearms-race-heats-up-which-did-you-buy/6836 [Accessed August 8, 2010].
Peffers, K. et al., 2006. The design science research process: A model for producing and
presenting information systems research. In Proceedings of the First International
Conference on Design Science Research in Information Systems and Technology
(DESRIST 2006). p. 83–106.
Perea, G., Usero, M. & Angel, J., 2006. Strategies for tailoring web contents for specific
devices: the case of usable and accessible contents for assistive technologies of web
mobile devices. Annals of Physics, 54(July), pp.1-5.
Dissertation Task 2
0834060
Page 47 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Picard, K., 2010. Minibanker med touch screen. Dinside.no. Available at:
http://www.dinside.no/851363/minibanker-med-touch-screen [Accessed January 4,
2011].
Plos, O. & Buisine, S., 2006. Universal design for mobile phones: a case study. CHI 2006,
pp.1229-1234.
Pollice, G., 2002. Using the Rational Unified Process for Small Projects: Expanding Upon
eXtreme Programming. Rational Software White Paper.
Raman, T.V. & Chen, C.L., 2008. Eyes-Free User Interfaces. Computer, 41(10), pp.100-101.
Rassmus-Gröhn, K., 2006. Enabling Audio-Haptics. Licentiate Thesis,Certec, Department of
Design Sciences, pp.1-126.
Redmine, Redmine. Available at: http://www.redmine.org/ [Accessed November 19, 2010].
Richtel, M., 1998. Making Web Sites More ―Usable‖ Is Former Sun Engineerʼs Goal. The
New York Times. Available at:
http://www.nytimes.com/library/tech/98/07/cyber/articles/13usability.html [Accessed
December 16, 2010].
Rossen, E., 2011. Blinde tyr til tjenesters mobile utgaver. Digi.no. Available at:
http://www.digi.no/859569/blinde-tyr-til-tjenesters-�mobile�-utgaver [Accessed
January 5, 2011].
Scott, R.A., 1995. The Making of Blind Men. In Deviance: A Symbolic Interactionist
Approach. Boston: General Hall, pp. 236-241.
Sendero Group LLC, Sendero Group Home Page, GPS for the Blind. Available at:
http://www.senderogroup.com/ [Accessed January 4, 2011].
Smith, K. & Sanders, D., 2007. Device Description Repository Requirements 1.0. W3C.
Available at: http://www.w3.org/TR/2007/NOTE-DDR-requirements-20071217/#secrequirements [Accessed August 27, 2010].
Smith-Jackson, T., Nussbaum, M. & Mooney, A., 2003. Accessible cell phone design:
development and application of a needs analysis framework. Disability and
rehabilitation, 25(10), pp.549-60.
Sorrel, C., 2010a. Swype: Text Input From the Inventor of T9. Wired.com. Available at:
http://www.wired.com/gadgetlab/2008/09/swype-text-inpu/ [Accessed January 4, 2011].
Sorrel, C., 2010b. Word Lens: Augmented Reality App Translates Street Signs Instantly.
Wired.com. Available at: http://www.wired.com/gadgetlab/2010/12/word-lensaugmented-reality-app-translates-street-signs-instantly/ [Accessed January 4, 2011].
Statped, statped.no - Om Statped. Available at:
http://statped.no/moduler/templates/Module_Overview.aspx?id=13539&epslanguage=N
O [Accessed January 3, 2011].
Dissertation Task 2
0834060
Page 48 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Steria, 2009. Slik lykkes du med universell utforming. Available at:
http://www.steria.no/2007/05/3-minutters-guide-slik-lykkes-du-med-universellutforming [Accessed September 15, 2010].
Strumillo, P., Skulimowski, P. & Polanczyk, M., 2009. Programming Symbian Smartphones
for the Blind and Visually Impaired. In Computers in Medical Activity. Berlin: SpringerVerlag Berlin and Heidelberg GmbH & Co. KG, pp. 129-136.
The Independent, 2010. Augmented Reality smartphone application helps visually impaired,
elderly to see. The Independent. Available at: http://www.independent.co.uk/lifestyle/health-and-families/augmented-reality-smartphone-application-helps-visuallyimpaired-elderly-to-see-1928269.html [Accessed August 29, 2010].
The National Federation of the Blind of Connecticut, The Courtesy Rules of Blindness.
Available at: http://www.nfbct.org/html/courtesy.htm [Accessed August 14, 2010].
The Nielsen Company, 2010. Android Soars, but iPhone Still Most Desired as Smartphones
Grab 25% of U.S. Mobile Market. Available at:
http://blog.nielsen.com/nielsenwire/online_mobile/android-soars-but-iphone-still-mostdesired-as-smartphones-grab-25-of-u-s-mobile-market/ [Accessed August 7, 2010].
Theofanos, M. & Redish, J., 2003. Bridging the gap: between accessibility and usability.
interactions, pp.36-51.
Tjan, B.S. et al., 2005. Digital Sign System for Indoor Wayfinding for the Visually Impaired.
2005 IEEE Computer Society Conference on Computer Vision and Pattern Recognition
(CVPRʼ05) - Workshops, pp.30-30.
Tollefsen, M. et al., 2011. På nett! Et notat om funksjonshemmede og bruk av sosiale medier,
Topolsky, J., 2008. Samsungʼs new TouchWiz UI gets previewed on video. Engadget.
Available at: http://www.engadget.com/2008/02/15/samsungs-new-touchwiz-ui-getspreviewed-on-video [Accessed August 16, 2010].
TouchType, 2010. SwiftKey - Revolutionary text prediction for Android smartphones.
Available at: http://www.swiftkey.net/ [Accessed September 24, 2010].
Vaishnavi, V. & Kuechler, W., 2007. Design Science Research Methods and Patterns:
Innovating Information and Communication Technology New Editio., Taylor & Francis,
Inc.
Vaishnavi, V. & Kuechler, W., 2008. The emergence of design research in information
systems in North America. Journal of Design Research, 7(1), p.1–16.
Virki, T., 2010. Nokia to use Linux for flagship N-series phones. Reuters. Available at:
http://www.reuters.com/article/idUSLDE65N14720100624 [Accessed September 5,
2010].
Dissertation Task 2
0834060
Page 49 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Vision 2020, 2009. How Does VISION 2020 Work? Available at:
http://www.vision2020.org/main.cfm?type=HOWDOESVIS2020WORK [Accessed
October 23, 2010].
Vogelstein, F., 2008. The untold story: How the iPhone blew up the wireless industry. Wired
Magazine, (16.02). Available at: http://www.wired.com/gadgets/wireless/magazine/1602/ff_iphone [Accessed May 14, 2010].
W3C, 2008. Web Content Accessibility Guidelines (WCAG) Overview. Available at:
http://www.w3.org/WAI/intro/wcag.php [Accessed January 4, 2011].
Wall, S.J., 2003. Supporting Vision 2020 : The right to sight. Community Eye Health, 16(45),
pp.1-2.
Wells, A., 2010a. SlideIT Keyboard. Android Tapp. Available at:
http://www.androidtapp.com/slideit-keyboard/ [Accessed September 19, 2010].
Wells, A., 2010b. ThickButtons Keyboard. Android Tapp. Available at:
http://www.androidtapp.com/thickbuttons-keyboard/ [Accessed September 19, 2010].
West, J. & Mace, M., 2010. Browsing as the killer app: Explaining the rapid success of
Appleʼs iPhone. Telecommunications Policy, 34(5-6), pp.270-286.
Wikipedia, 2010a. Capacitive sensing. Wikipedia. Available at:
http://en.wikipedia.org/wiki/Capacitive_sensing.
Wikipedia, 2010b. Feature phone. Wikipedia. Available at:
http://en.wikipedia.org/wiki/Feature_phone [Accessed August 7, 2010].
Wikipedia, 2010c. Resistive touchscreen. Wikipedia. Available at:
http://en.wikipedia.org/wiki/Resistive_touchscreen [Accessed September 19, 2010].
Wikipedia, 2010d. Screen reader. Wikipedia. Available at:
http://en.wikipedia.org/wiki/Screen_reader [Accessed May 7, 2010].
Wikipedia, 2010e. Smartphone. Wikipedia. Available at:
http://en.wikipedia.org/wiki/Smartphone [Accessed August 7, 2010].
Wikipedia, 2010f. T9 (predictive text). Wikipedia. Available at:
http://en.wikipedia.org/wiki/T9_(predictive_text) [Accessed September 18, 2010].
World Blind union, Main page UMC/WBU. Available at:
http://www.worldblindunion.org/en/home.html [Accessed October 24, 2010].
World Health Organization, 2009. Visual impairment and blindness. Available at:
http://www.who.int/mediacentre/factsheets/fs282/en/index.html [Accessed October 23,
2010].
Yfantidis, G. & Evreinov, G., 2005. Adaptive blind interaction technique for touchscreens.
Universal Access in the Information Society, 4(4), pp.328-337.
Dissertation Task 2
0834060
Page 50 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Yu, W. & Brewster, S., 2003. Evaluation of multimodal graphs for blind people. Universal
Access in the Information Society, 2(2), pp.105-124.
Dissertation Task 2
0834060
Page 51 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
APPENDIX A: ETHICAL APPROVAL
Dissertation Task 2
0834060
Page 52 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
APPENDIX B: ABOUT THE AUTHOR
The author of this dissertation has been working in the telecom industry since 1999; initially
as a sales associate of mobile phones, followed by employment within one of Norway’s
largest distributor of mobiles from 2004. Onwards he played a key role in launching the first
Windows Mobile based phones in Norway. Subsequently, he started working in a subsidiary
of the distributor company, focusing on providing mobile solutions for businesses. The
solutions ranged from providing wireless e-mail access on mobile phones, before it became a
standard. Later, mobile device management solutions were directed at ensuring
implementation of correct security measures, as well as providing remote management of
applications and support on mobile phones. Lately, the author has been working on providing
new applications and solutions to companies. For instance a solution for automatic
configuration of mobile phones, which ensures that the phone is set up with a company image
and a solution to replace the mobile phone´s own Graphical User Interface with a simpler one,
thus providing access only to the applications and services that the user needs.
Dissertation Task 2
0834060
Page 53 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
APPENDIX C: THE MOBILE MARKET
The mobile phone market enjoys increased popularity, with market shares expanding every
day (IDC, 2010); it is now considered larger than the PC market (Neset, 2010). The mobile
market consists mainly of two types of mobile phones; feature phones and smartphones.
Where feature phones are considered low-end phones, with limited features and computer
power (Nusca, 2010; Wikipedia, 2010b), smartphones offer more advanced computing power
and operating systems, as well as greater connectivity; they are essentially small mobile
computers (Wikipedia, 2010e).
During the first quarter of 2010, a total of 314.7 million mobile phones were sold to end users
worldwide, with smartphones making up 54.3 million of the sales (Gartner, 2010b); this is an
increase of 17% compared to the same period in 2009. Although, feature phones are still
considered the platform with the largest sales volume, smartphones have had a positive
increase and sales are expected to increase further in the coming years (IDC, 2010).
Looking at the US alone, patterns are the same. Of the 234 million mobile phones that were in
use between March and May 2010, 49.1 million were smartphones (Comscore, 2010). Similar
numbers have been found by The Nielsen Company (2010), who report that smartphones now
hold 25% of the market, an increase from 23% in 2009. Recent trends suggest that
smartphones will surpass feature phones in 2011.
According to Gartner (2010) the top five OS for smartphones are; Symbian (44,3%),
Blackberry (19.4%), Apple iOS (15.4%), Google Android (9.6%) and Windows Phone
(6.8%). In the US, the chart is slightly different; Blackberry (35%), Apple iOS (28%),
Windows Phone (15%), Google Android (13%) and Palm OS (3%) (Comscore, 2010);
moreover, Apple iOS and Google Android are currently the fastest growing (The Nielsen
Company, 2010). Gartner estimates that the Android OS will be the second largest OS
worldwide in 2010 and it will challenge Symbian’s top ranking position in 2014 (Gartner,
2010a). The numbers show that smartphones sales are increasing, suggesting that the market
wants more advanced phones, with more functionality and better connectivity.
To meet the increased demand for smartphones, Nokia has announced that they will
discontinue the Symbian OS on their popular N-series phones and instead focus on a new
system called Meego (Virki, 2010). Microsoft, on the other hand has already released their
new Windows Phone 7 OS, which will replace the outdated Windows Phone range (Eriksen,
2010).
Appendix C.A - The new players
New actors like Apple and Google have in many ways changed the mobile market, enabling
people to use and operate mobile phones in a different way. With the introduction of the
iPhone, consumers no longer need multiple devices. Instead of using separate devices for
making phone calls, sending e-mails and listening to music, the iPhone introduced one device
for all functionalities, which can be further expanded through downloadable applications
(Vogelstein, 2008).
The possibility to download new applications, and thereby extend the phone’s capabilities and
functionalities, is probably the largest contributor to the iPhone’s success. Not only does it
enable the user to personalize the phone, but it also changes the mobile market; where the
handset manufacturer is in control and not the mobile operator (Holzer & Ondrus, 2010; West
& Mace, 2010). Other manufacturers have followed the same path and Google experiences a
Dissertation Task 2
0834060
Page 54 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
similar success; in fact, the Android platform is currently outselling the iPhone in the US
(Comscore, 2010; The Nielsen Company, 2010). The mobile application market will most
likely continue to increase the demand for smartphones, thus ensuring market growth.
Although it was by no means a pioneer, the iPhone also changed the market by replacing
buttons with a touch screen. Furthermore its sleek design and easy access landed it the Times
Magazine’s award ―Innovation of the year‖ in 2007 (Clark, 2007; Grossman, 2007). What
separates the iPhone’s touch screen from others was its implementation, which made users
prefer it above regular keyboard navigation. Today, most smartphones have a touch screen.
APPENDIX D: USING THE MOBILE PHONE FOR ASSITIVE AID
Products and services directed at assisting users with visual impairments are no longer restricted
to government organizations and non-profit communities. Several companies are moving into the
mobile care market with profit in mind; developing applications and wireless devices that
provide health-related services. In the US, sales are expected to expand to $600 million in 2010
and $1.3 billion in 2011. Qualcomm, AT&T, IBM and Best Buy are just a few of the companies
that are planning to release new services in the area. While most of the applications are intended
for the regular consumers who desire health and fitness applications, more specialized solutions
are also in progress. One such solution is designed to streamline information accessibility for
hospitals and doctors, and make it easier to monitor patients regardless of their location (Kharif,
2010).
Appendix D.A - Object recognition
Defining what is in front of one is not always an easy task for someone with vision loss;
hence, by pointing a mobile phones camera on an object, the application will analyze and present
the result to the user through text or voice (The Independent, 2010).
DocuScan and knfbReader are applications using the mobile phones camera to scan and
convert printed text into digital text, for then to have it read out through the use of a screen
reader (Mlauf, 2010; Bojo AS, n.d.). Two other applications are Look Tel (LookTel, n.d.) and
Google Goggles (Google n.d.) that analyzes objects and presents the result in text or voice.
World Lens is an application using the phones inbuilt camera to instantly translate text from
one language to another. The result is displayed on the mobile screen, in the same place as the
original text. Although, intended for a sighted person, the technology demonstrates how the
camera can be used as an aid in communicating information to the user, even when it is in
foreign language (Sorrel, 2010b)
Appendix D.B - Navigation
In a controlled environment, a blind person can familiarize himself with the surroundings,
being able to navigate around without any help. However, this picture is quite different when
moving to an uncontrolled area, like the grocery store or the shopping mall. The guide dog
and the long are cane is indispensable, but these aids cannot tell your exact location or how to
navigate from A to B in new surroundings. Special GPS units for people with vision loss can
aid in this matter (HumanWare, n.d.; Sendero Group LLC, n.d.), but they do not work in
indoor environments.
Tjan et al (2005) has presented a digital sign system, where a handheld camera can detect
Dissertation Task 2
0834060
Page 55 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
special retro-reflective tags, informing the user of their current location. Coughlan and
Manduchi (2009) have presented a similar solution, but instead of a separate camera, a mobile
phone with an inbuilt camera was used to read colored signs.
Brush et al. (2010) created an activity-based application, allowing a user to travel to a location
by essentially following breadcrumbs being displayed on the mobile phone. What
differentiates this solution from other GPS based solutions is that it is not relying on accurate
position, but instead uses the phones activity to remember where it has been. Examples are
changes in the phones accelerometer or lost connection with the Bluetooth in the car stereo.
Another example is a project aiming at enabling blind people to travel alone, and perform the
same tasks as a sighted person. When roaming in known vicinity; a blind person will normally
use a guide dog for assistance, but when encountered with unfamiliar surroundings the
reliance of a real person is often needed. The project aims at developing a mobile solution,
where the user carries a camera that wirelessly transmits information to a help center, where
an operator can instruct the user and provide guidance (Helland, 2003).
Augmented reality can also be used for aiding blind people. A project called ―The voice for
Android‖, developed for mobile phones running Android OS, provides an augmented reality
experience without relying on vision. Sound and voice is used to guide the user around in the
surrounding environment, by leveraging on the phones inbuilt camera. The application can
analyze photo snapshots and provide feedback trough sound, on distance and height of objects,
much like the way sonars operate. In addition, the user can also be informed of compass
direction and colors (Meijer, n.d.).
Dissertation Task 2
0834060
Page 56 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
APPENDIX E: INTERVIEW WITH TOR ULLAND AT HUSEBY (STATPED)
Tor Ulland is as senior advisor at Huseby Resource Centre for the blind, a division of Statped,
were he has been working since 1994. He provides training and guidance to people with
vision loss, with a special focus on assistive aids for computer related equipment, cell phones,
GPS and Daisy audio book players.
What kind of training is provided to people who are blind?
That is a good question. If you are born blind, you get regular school education and learn how
to perform daily activities; such as making food. In addition, you learn Braille, use of
computer aids and the white cane.
For adults experiencing vision loss, there are rehabilitation courses which they can undertake;
both from The Norwegian Association of the Blind and partially sighted and Huseby
(Statped). In addition, The Norwegian Association of the Blind and partially sighted have
several courses called "Adaptation Courses"; guiding an individual through the new life as a
blind. The courses consist of an introductory course followed by three courses; each lasting
fourteen days. Huseby offer is of a more personal character, where each course is tailored for
the participant. It starts with two to three days of a surveying, followed by several courses
lasting one to two weeks each; depending on the specific needs of the participant. Most last
for six weeks, thought in some cases it can last for several years.
It is also possible to receive some extra training if you are using assistive aids; normally from
The Norwegian Labour and Welfare Administration, but may also be from the municipality.
The offer varies from municipality to municipality, depending on available funds and
expertise.
Is it tougher to train someone who has lost sight during adult life?
An individual who experiences vision loss at adulthood will never be any good in Braille.
However, people who are born blind may have greater difficulty understanding concepts such
as space and direction, compared to people who have seen and know these concepts. This is
an oversimplification, but it explains some of the issues which might be a problem.
What kinds of assistive aids are available for people with vision loss?
There are several aids available. On computers, aids can consisting of; synthetic speech,
refreshable Braille displays to read the content of a PC screen, and scanner programs for
optical scanning of text (OCR).
In addition, you also have regular aids like the white cane or the guide dog. But you also have
applications like; watches with Braille marking, clocks that talk, color indicators and speaking
weights.
The Norwegian Association of the Blind and Partially Sighted have a subsidiary called
Adaptor; providing a variety of variety of tools to aid centers and are also available from
www.hjelpemiddelkatalogen.no.
Are there any particular challenges you see in the use of electronic products? Such as
mobile phones, radio, TV, touch screens, ATMs, etc. And would you say that such items
are accessible to those who are visually impaired?
No, they are not good enough. Radio and TVs have become more and more of a problem.
Dissertation Task 2
0834060
Page 57 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
With so many menus where you can define settings, it is impossible to keep track of every
option or setting. In the old days there were buttons, but now everything must be done
through a menu system displayed on the screen. If you would like to set up a channel, it is
often necessary to open a specific menu; which is impossible when cannot see the screen and
receive appropriate feedback
On my home stereo, I could set up 20 radio channels on the remote control. To find out which
channel I was setting up, I would listen a little too each station and program the remote
accordingly. I would then remember the order of each channel, on the remote.
However, I remember one time when I was spending hours setting this up. By accident I
pressed the wrong button and everything got deleted. I had to start all over again. In
retrospective, this is just one of many examples of how bad products are designed for the
blind.
It is even worse on products which remember the last menu you exited. As opposed to always
start in a set place, it is impossible to know where you are in a menu which constantly
changes, since you cannot write it down and memorize what and where to press.
How would you say it is to use public services?
I would say that it is not easy, since many of these systems not available for the partially
sighted. Systems such as Flexus, machines to buy train tickets from, most ATMs and several
other systems are not designed for this user group. The same applies for public transportation
system information; knowing which metro line or bus is coming next.
Would you recon that manufacturers do not include people who are visually impaired
when designing products?
That is correct. They do not think about this group until afterwards and then it is often too
late. It has been said that it would be much cheaper to let all the blind travels in Oslo travel for
free, than instead of changing the system to be compatible.
You have already mentioned that one can learn the order of things, when operating
electronic products, but does this apply to types of equipment, like the oven or stove at
home?
You have to know which button is for function. With older stoves this was easy, but with
newer is increasingly more difficult as most have menu to operate. For instance, my old
washing machine has a button that regulates the temperature. Standing in a right position
equals to 30 degrees, down 60 degrees and to the left is 90 degrees. For 40 degrees I can then
calculate my way around. This is impossible with modern machines.
Do you have any thoughts regarding how the society organizes itself to include people
with vision loss?
Most places or services are not accessible, but I hope that things will get better with the new
anti-discrimination law here in Norway. It came in 2009; require manufacturer to design their
products to be accessible for all user groups. Right now I think that it will take a while before
we will see a change, unless larger markets implement the same rules.
However, USA has adopted new rules, stating that mobile phones should more accessible. If
these rules are extended to the rest of the market, I think that manufacturers will start to
design their products accordingly.
Dissertation Task 2
0834060
Page 58 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Could you name some of the organizations in Norway offering support and assistance to
people who are visually impaired?
Certainly, here is a small sample; The Norwegian Association of the Blind and Partially
Sighted, Association Interest Group for the Visually Impaired Computer users, visually
impaired Scholars Association (intended for people with higher education), Christian work
among the blind and visually impaired (provides books and text), Norwegian sound and Blind
Library (Produces books in Braille and voice, making both fiction and science to higher
education, Statped (Huseby) and Tamatun (work in relation to schools and training).
Dissertation Task 2
0834060
Page 59 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
APPENDIX F: PROJECT PLAN
Dissertation Task 2
0834060
Page 60 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
APPENDIX G: PROJECT MEETING REPORTS
The following appendix contains meeting reports documenting the project meetings held during
the project. The meeting reports consist of initial meetings, before the development process
started and reports documenting each of the iteration versions.
Appendix G.A - Initial project workshop meeting, June 14, 2010
Attendants:
Magne Gabrielsen
Alexander Dreyer Johnsen
Agenda:
Produce an initial list of functionality which the application will support. The list will
at a later meeting be presented to the developers for feedback regarding functionality
and what will be possible to implement in the prototype.
Application requirements:
Platform
o Due to easy access, broad support of mobile phones and easy development, the
solution should be developed for the Android mobile operating system
The User interface (UI)
o The application needs to be built around an easy and light weighted user interface.
All options needs to be concise and provide the same means of performing actions
and navigating through the menus.
o The menus should be in contrast colors, black and orange/brown. All text should be
in a large and bold font, to make reading easier.
Feedback
o Correct orientation
Use the mobile phone’s inbuilt gyro to inform the user if the phone is facing
upwards (correct way), or downwards (wrong way).
o Physical feedback
Use the vibration engine in the phone, to provide feedback when the user
changes/moves the finger between menus. Also called haptics.
o Sound
Sound /voices to be played when user selects an option
Sounds/voices to be played when information are provided to the user
It should not be possible for the user to set the volume below a default “low
level” value. This to prevent the user from turning off sound and not being
able to turn it on again.
Will use Google Voice or another sound library to create computerized voice
messages
o Notifications
Dissertation Task 2
0834060
Page 61 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
The phones own notification messages will have to be suppressed, as they
are designed for visual notification. The system will have to provide its own
set of notifications. Ex. Vibrate three times when running low on battery.
Setup
o When the application launches for the first time, it will prompt the user if it is
intended for a user who is blind or have lowered vision.
o Settings will be set in XML files.
o It is possible to provision new settings through the use of a mobile device
management (MDM) system. An MDM system can provision a new XML file to the
phone, which will automatically change settings without the user getting involved.
o The system should be extended to a web-portal were an administrator easily can
send out new settings
Functionality
o Navigation
Navigation from A to B
Leverage on functionality from Google Maps
Information on current location
o Analyze
The phone’s camera can be used to automatically recognize objects in front
of the camera, for then to provide feedback to the user.
o Remote assistance
It should be possible for the user to request assistance. Through an option in
the menu, the user can select to receive assistance.
The phone will make a connection to a support desk application, were an
operator can accept the request. Once accepted, the operator will be able to
see through the phone’s internal camera and locate the user by the
assistance of the phone’s internal GPS unit.
o Phone calls
It should be possible to perform phone calls
The prototype will only provide a list of pre-set phone numbers which the
user can call.
The defined numbers can be changed in the XML file.
Dissertation Task 2
0834060
Page 62 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix G.B - Approval of functionality, June 25, 2010
Attendants:
Magne Gabrielsen
Alexander Dreyer Johnsen
Espen Snilsberg Richardsen
Kim Ruben Teigen
Agenda:
Present the application, it uses and the proposed list of functionalities for the
prototype. The developers will provide feedback and the meeting will conclude with a
confirmed set of functionality to be implemented.
Application requirements:
Platform
o It was decided that the Android OS was the platform to develop the solution on.
The User interface (UI)
o A visual prototype was presented to the developers, which showed the proposed
idea for how the menu and navigation should look. It was decided that the first
version should be similar to the visual prototype.
o The menus should be in contrast colors, black and orange/brown. All text should be
in a large and bold font, to make reading easier.
o If the setup is designed to be used by blind users, the mobile phones backlight will be
turned off to consume battery.
o It was decided to use the full power of the Android OS, which enables a developer to
create their own UI without having to rely on the one shipped with the OS. The
project will therefor create an entirely new UI, to minimize the risk of messages or
feedback not suited for navigation from a blind or lowered vision user.
Feedback
o Correct orientation
The developers thought it would be possible to use the mobile phones inbuilt gyro to tell whether the phone is facing upwards (correct way), or
downwards (wrong way). However, this might be phone model dependent,
as not every phone comes with a gyro or can tell if which direction it is being
held.
o Physical feedback
It was decided to use the vibration engine in the phone to provide feedback
when the user changes/moves the finger between menus.
o Sound
To create computerized voice messages, a library called TTS Service
Extended will be used. It provides an API which enables developers to create
text messages, which the library plays as a computerized voice. Some
showcases were presented in the meeting, and it was decided that the
output should be satisfactory. However, there might be a problem with the
Dissertation Task 2
0834060
Page 63 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
o
library only supporting English for the moment. For a production system, this
will limit the number of potential users, but for the prototype it was deemed
satisfactory.
Sound /voices will be played when user selects an option
Sounds/voices will be played when information are provided to the user
The user will not be able to set the volume below a default “low level” value.
This to prevent the user from turning off sound and not being able to turn it
on again.
Notifications
The phones own notification messages will be suppressed to best extend.
Creating a new UI will also help on this, since the project will not have to rely
on the same information generated.
The system will provide its own set of notifications. Ex. Vibrate three times
when running low on battery.
Setup
o When the application launches for the first time, it will prompt the user if it is
intended for a user who is blind or have lowered vision.
o Settings will be set in XML files.
o It is possible to provision new settings through the use of a mobile device
management (MDM) system. An MDM system can provision a new XML file to the
phone, which will automatically change settings without the user getting involved.
o The system should be extended to a web-portal were an administrator easily can
send out new settings. This functionality will be developed, but the UI will be created
for test purposes and not production.
Functionality
o Navigation
Google Maps will be used for Navigation.
A pre-defined list of destinations will be entered in the system, which the
user can choose from. Google maps will then generate a route from current
location to the selected destination.
TTS Service Extended will be used to read out the list to the user.
Information on current location will be available
o Remote assistance
It will be possible for the user to request assistance. Through an option in the
menu, the user can select to receive assistance.
For the prototype, the phone will make a connection to a web service and
automatically start sending pictures/video from the phone’s internal camera
and location provided from the internal GPS unit.
o Analyze
It was intended to use Google Goggles for analyzing object. Google Goggles
can automatically recognize text and numbers and should therefore be
sufficient for this purpose. However, the current version of Google Goggles
does not provide an API; hence it cannot be implemented in another
Dissertation Task 2
0834060
Page 64 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
o
application. Because of this limitation, the UI will only link to the Google
Goggles application.
Phone calls
The prototype will provide a list of 5 pre-set phone numbers which the user
can call.
The defined numbers can be changed in the XML file.
Dissertation Task 2
0834060
Page 65 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix G.C - Layout of UI, August 30, 2010
1. Information
a. Time
i. Say: The current time is ”CURRENT TIME”
b. Date
i. Say: Today’s date is
c. Today’s weather
i. Say: The weather at your current location in Oslo is 23 degrees and sunny.
d. Back
2. Phone
a. Contact book
i. Alexander: +47 977 65 888
ii. Home:
iii. Work:
iv. Opplysningen: 1881
v. Back
b. Keypad
i. Is this possible?
ii. Back
c. Back
3. Navigation
a. Current location
i. Say: Your current location is….
b. Compass
i. Display compass
ii. Back
c. Navigate to
i. Home
1. Say: This is just a simulation. Please go back
ii. Work
1. Say: This is just a simulation. Please go back
iii. Grocery store
1. Say: This is just a simulation. Please go back
iv. Bank
1. Say: This is just a simulation. Please go back
v. Back
d. Back
4. Analyze
a. Launch Google Goggles
5. Applications
a. Web browser
b. Facebook
c. Mail
d. Text messages
Dissertation Task 2
0834060
Page 66 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
e. Back
Dissertation Task 2
0834060
Page 67 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix G.D - Layout of UI, September 13, 2010
The application should inform the user of successful opening of a sub-menu, in addition of
informing the user when returning to the main menu.
The menu will also have to be translated to Norwegian, as the participants testing the UI are
from Norway.
1. Information
Say: Opening Information menu
a. Time
i. Say: The current time is ”CURRENT TIME”
b. Date
i. Say: Today’s date is ”CURRENT DATE”
c. Today’s weather
i. Say: The weather at your current location in Oslo is 23 degrees and sunny.
d. Back
2. Phone
Say: Opening Phone menu
a. Contact book
i. Home:
1. Say: Calling Home. HOLD. This is a test of the user interface. Calling
Home will not be provided in this test. Please choose another option.
ii. Work:
1. Say: Calling Work. HOLD. This is a test of the user interface. Calling
Work will not be provided in this test. Please choose another option.
iii. Alexander: +47 977 65 888
1. Say: Calling Alexander
2. Perform call
iv. Taxi
1. Say: Calling Taxi. HOLD. This is a test of the user interface. Calling
Taxi will not be provided in this test. Please choose another option.
v. Back
b. Keypad
i. This is a test of the user interface. Entering numbers will not be provided in
this test. Please choose another option.
ii. Back
c. Back
3. Navigation
Say: Opening Navigation menu
a. Current location
i. Say: Your current location is….
b. Compass
i. Display compass
ii. Back
c. Navigate to
i. Home
Dissertation Task 2
0834060
Page 68 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
ii.
iii.
iv.
1. Say: Navigating to Home. HOLD. This is a test of the user interface.
Navigation will not be provided in this test. Please choose another
option.
Work
1. Navigating to Work. HOLD. This is a test of the user interface.
Navigation will not be provided in this test. Please choose another
option.
Grocery store
1. Navigating to Grocery store. HOLD. This is a test of the user
interface. Navigation will not be provided in this test. Please choose
another option.
Bank
1. Navigating to Bank. HOLD. This is a test of the user interface.
Navigation will not be provided in this test. Please choose another
option.
Back
v.
d. Back
4. Analyze
Say: Opening Analyze menu
a. Launch Google Goggles
b. Back
5. Applications
Say: Opening applications menu
a. Web browser
i. Say: Opening Web browser. HOLD. This is a test of the user interface. The
application will not be opened in this test. Please choose another option.
b. Facebook
i. Say: Opening Facebook. HOLD. This is a test of the user interface. The
application will not be opened in this test. Please choose another option.
c. Mail
i. Say: Opening Mail. HOLD. This is a test of the user interface. The application
will not be opened in this test. Please choose another option.
d. Text messages
i. Say: Opening Text messages. HOLD. This is a test of the user interface. The
application will not be opened in this test. Please choose another option.
e. Back
Dissertation Task 2
0834060
Page 69 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix G.E - Layout of UI, October 10, 2010
The application should inform the user of successful opening of a sub-menu, in addition of
informing the user when returning to the main menu. A problem was discovered in the first
round of testing, where text being read out is canceled if another selection is made. A solution
to this issue is to have the system prioritize menu and sub-menu messages, allowing them to
finish playing before stating elements. Individual elements should still be canceled by other
elements selected.
The operation of elements should to be changed to improve navigation of the UI. Instead of
first tapping once to have an option read out and then tap one more time to select it, a gesture
should to be introduced to improve the selection of elements.
With the introduction of a gesture; menu options are still read out with a single tap, while
opening elements are performed trough holding the finger on the option and slide right to
open. This should make it easier to select elements, as well as improve on incorrectly opening
wrong elements since the finger never leaves the screen.
Second round of testing should also implement list navigation in Contact book, Applications
and Navigate to. Please referrer to visual design for implementation. The UI should pre-load
all applications and contacts, and only display navigation letters matching applications and
contacts. Ex. B should only be displayed if an application begins with B.
1. Information
Say: Opening Information menu
a. Time
i. Say: The current time is ”CURRENT TIME”
b. Date
i. Say: Today’s date is ”CURRENT DATE”
c. Today’s weather
i. Say: The weather at your current location in Oslo is 23 degrees and sunny.
d. Back
2. Phone
Say: Opening Phone menu
a. Contact book
Say: Opening Contact book
i. Home:
1. Say: Calling Home will not be provided in this test. Please choose
another option.
ii. Work:
1. Say: Calling Work will not be provided in this test. Please choose
another option.
iii. Alexander: +47 977 65 888
1. Say: Calling Alexander
2. Perform call
iv. Taxi
1. Say: Calling Taxi will not be provided in this test. Please choose
another option.
Dissertation Task 2
0834060
Page 70 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
v. Back
b. Dial a number
i. Dialing numbers will not be provided in this test. Please choose another
option.
ii. Back
c. Back
3. Navigation
Say: Opening Navigation menu
a. Current location
i. Say: Your current location is….
b. Compass
i. Display compass
ii. Back
c. Navigate to
Say: Opening Navigate to
i. Home
1. Say: Navigating to Home will not be provided in this test. Please
choose another option.
ii. Work
1. Say: Navigating to Work will not be provided in this test. Please
choose another option.
iii. Grocery store
1. Say: Navigating to Grocery store will not be provided in this test.
Please choose another option.
iv. Bank
1. Say: Navigating to Bank will not be provided in this test. Please
choose another option.
v. Back
d. Back
4. Analyze
Say: Opening Analyze menu
a. Launch Google Goggles
b. Back
5. Applications
Say: Opening applications menu
a. Web browser
i. Say: The web browser application will not be opened in this test. Please
choose another option.
b. Facebook
i. Say: The Facebook application will not be opened in this test. Please choose
another option.
c. Mail
i. Say: The mail application will not be opened in this test. Please choose
another option.
d. Text messages
Dissertation Task 2
0834060
Page 71 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
i. Say: The text messages application will not be opened in this test. Please
choose another option.
e. Back
Dissertation Task 2
0834060
Page 72 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix G.F - Layout of UI, October 13, 2010
The application should inform the user of successful opening of a sub-menu, in addition of
informing the user when returning to the main menu. A problem was discovered in the first
round of testing, where text being read out is canceled if another selection is made. A solution
to this issue is to have the system prioritize menu and sub-menu messages, allowing them to
finish playing before stating elements. Individual elements should still be canceled by other
elements selected.
The operation of elements should to be changed to improve navigation of the UI. Instead of
first tapping once to have an option read out and then tap one more time to select it, a gesture
should to be introduced to improve the selection of elements.
With the introduction of a gesture; menu options are still read out with a single tap, while
opening elements are performed trough holding the finger on the option and slide right to
open. This should make it easier to select elements, as well as improve on incorrectly opening
wrong elements since the finger never leaves the screen.
All menu elements should state elements number and total number of elements in the current
list. Example: 1 of 4 Facebook, 2 of 4 Mail etc. This applies for all menus, including main
menu.
To improve navigation, a shortcut to the top-main menu should be introduced. The option
―Home‖, should be at the top of every menu, except for the main menu‖ and take up half the
size of a normal menu option.
Second round of testing should also implement list navigation in Contact book, Applications
and Travel to. Please referrer to visual design for implementation. The UI should pre-load all
applications and contacts, and only display navigation letters matching applications and
contacts. Ex. B should only be displayed if an application begins with B.
1. Information
Say: Opening Information menu
a. Time
i. Say: The current time is ”CURRENT TIME”
b. Date
i. Say: Today’s date is ”CURRENT DATE”
c. Today’s weather
i. Say: The weather at your current location in Oslo is 23 degrees and sunny.
d. Back
2. Phone
Say: Opening Phone menu
a. Contact book
Say: Opening Contact book
i. Home:
1. Say: Calling Home will not be provided in this test. Please choose
another option.
ii. Work:
Dissertation Task 2
0834060
Page 73 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
1. Say: Calling Work will not be provided in this test. Please choose
another option.
iii. Alexander: +47 977 65 888
1. Say: Calling Alexander
2. Perform call
iv. Taxi
1. Say: Calling Taxi will not be provided in this test. Please choose
another option.
v. Back
b. Dial a number
i. Dialing numbers will not be provided in this test. Please choose another
option.
c. Back
3. Navigation
Say: Opening Navigation menu
a. Your location
i. Say: Your current location is….
b. Compass
i. Display compass
c. Travel to
Say: Opening Travel to
i. Home
1. Say: Traveling to Home will not be provided in this test. Please
choose another option.
ii. Work
1. Say: Traveling to Work will not be provided in this test. Please
choose another option.
iii. Grocery store
1. Say: Traveling to Grocery store will not be provided in this test.
Please choose another option.
iv. Bank
1. Say: Traveling to Bank will not be provided in this test. Please choose
another option.
v. Back
d. Back
4. Analyze
Say: Opening Analyze menu
a. Launch Google Goggles
b. Back
5. Applications
Say: Opening applications menu
a. Web browser
i. Say: The web browser application will not be opened in this test. Please
choose another option.
b. Facebook
Dissertation Task 2
0834060
Page 74 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
i. Say: The Facebook application will not be opened in this test. Please choose
another option.
c. Mail
i. Say: The mail application will not be opened in this test. Please choose
another option.
d. Text messages
i. Say: The text messages application will not be opened in this test. Please
choose another option.
e. Back
Dissertation Task 2
0834060
Page 75 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
APPENDIX H: DOCUMENTATION OF UI
The following appendix contains documentation of the UI used during the development. G.A
presents documentation of the UI as it stands in iteration 5. G.B to G.F presents the virtual
models; created in Microsoft Expression Blend 4 with SketchFlow (Microsoft Corportation
2009), a tool allowing non-developers to create working virtual applications of the final
product. The following documentation is the printout of the working applications.
Appendix H.A – Documentation of UI, version 0.0.5
The following document presents the UI prototype at the current stage of development;
version 0.0.5.
Operation of the UI is operated through sound and tactile feedback. A single tap on the screen
will make the UI talk, and state the function of the selected element, while the gesture ―tap
and dragging the finger to the right‖ will execute the element. Dragging the finger across the
screen will make the UI read out functions as the finger approaches and at the same time
make the phone vibrate to indicate that a new item is available. A back element is placed at
the bottom of every screen, except for the top main menu, allowing the user to easily navigate
to the previous menu.
To help the user build a virtual map of the different menus and elements, the UI will state
which level it is displaying and when successfully executing an element. The UI can also be
customized to state the total numbered elements for each view, where current selected
element place number is stated followed by total elements available in the current list.
All screenshots are actual shots of how the application looks on the mobile phone. The
following section will provide screenshots of each sub menu available for the user.
Information
The main menu is the start
page, providing access to
sub menus and functions.
Selecting Information will
present the following menu.
Dissertation Task 2
Time, Date and Todays
weather is available. Each
function will state different
information depending on
selected function.
0834060
Page 76 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Phone menu
The main menu is the
start page, providing
access to sub menus
and functions.
Selecting Phone menu
will present the
following menu.
Phone menu starts
with a sub-menu,
providing access to
Contact book and Dial
a number.
Selecting Contact
book will bring up a
list of available predefined contacts.
Selecting Dial a
number will enable the
user to dial a number
manually through
Enter number.
Navigation
The main menu is the start
page, providing access to
sub menus and functions.
Selecting Navigation will
present the following
menu.
Dissertation Task 2
Navigation starts with a submenu, providing access to
Current location, Compass
and Travel to. Selecting
Current location will state
the phones current location.
Compass will start a third
party application displaying a
compass, while Travel to will
take the user to a new menu.
Travel to allow the user
to navigate through large
lists of data. On the right
side is an alphabetical
list, which will update the
list on the left according
to the selected letter. I
0834060
Page 77 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Analyze
The main menu is the start
page, providing access to
sub menus and functions.
Selecting Analyze will
present the following menu.
The Analyze menu allows
the user to launch an OCR
application. Google
Goggles is used in this
example.
Applications
The main menu is the start
page, providing access to
sub menus and functions.
Selecting Applications will
present the following menu.
Dissertation Task 2
Applications provide a list
of applications which the
user can launch. In this
example Web browser,
Facebook, Mail and Text
messages are available.
0834060
Page 78 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix H.B – Documentation of Conceptual Design
The following document is a general overview on how the intended application will operate
and its functions with a short description. The functions listed are not necessarily the final
one, and should be considered as a work in progress. This can for example change trough the
feedback received from the interviews performed on the test participants.
The document lists an iPhone as the phone of use. This is done for visual representation.
Through the development project, decision during development platform and supported
mobile phones will be made. The only requirement set out by the project is that the phone is
easily available through the general commercial market; have an open operating system
enabling the use of third party developed applications, touch screen, GPS, compass, level
meter and a camera.
Prototype Map
The following map, displays the flow of the virtual prototype application. When starting the
application, the user will begin at ―Start‖ and then navigate to appropriate sub-menus.
Figure 1: SketchFlow Map
Navigation Screens
The following slides display the intended navigation of the program. Although the screens
display text, the navigation is not intended to be used by visual navigation, although it
supports it, but through the use of sound played through the mobile phone’s attached hands
free/headphone. When hovering with the finger over an item, a sound will play stating the
name of the current selected alternative. Tapping with the finger on the same place, will open
the selected alternative.
Dissertation Task 2
0834060
Page 79 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Start
When starting the program, the user will be presented with the following screen. This is the
main menu of the application, and will guide the user to all functions of the application.
Figure 2: Start
Analyze
This tool will use the mobile phones internal camera to automatically recognize elements in
front of the camera. Items that can be detected are pre-configured. If the user holds a NOK
100,- bill in front of the camera, the application will play a sound telling the user that it can
see a ―NOK 100,- bill‖.
It is also intended that the application will include a list of traffic lights and positions of
placement. The first version will start out small, focusing on smaller parts of Oslo, Norway,
but it is intended that the application shall include a list of all traffic lights for supported
countries. For easier navigation, the list will (if possible) include the latitude for the traffic
light as well so that the application can guide the user in pointing the mobile phone’s camera
in the right direction and angle. The application will then detect the color of the light on the
traffic light.
Items that can be detected, in addition to updated traffic light information can be wirelessly
transferred to the mobile phone from the support center.
Dissertation Task 2
0834060
Page 80 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Figure 3: Analyze
Assistance
This function will automatically place a phone call between the user’s phone and the support
center. An internet connection will be established, enabling the support center to remotely see
through the mobile phone’s internal camera. The support center can also re-program the
phone’s pre-defined lists, in case the user wishes to travel to a location not stored on the
mobile phone.
Figure 4: Assistance
Dissertation Task 2
0834060
Page 81 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Local weather
This function will automatically go online and download the latest weather report for the
current location, for then to play the report through the hands free/head phones.
Figure 5: Local weather
Locate me
This function will automatically locate were the user is located and play the position through the
hands free/head phones.
Figure 6: Locate me
Travel
This function includes a pre-defined list of locations, were the user can get travel assistance from
the mobile phone. The first version will include up to four pre-defined locations. If the user would
like to travel to a destination not on the list or would like to have the list updated, the user can use
the Assistance function, to have the support center update the list of pre-defined locations.
Dissertation Task 2
0834060
Page 82 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Figure 7: Travel
Navigate
After proper selection is made, from the previous pre-defined location screen, the user will be
presented with the travel route through the hands free/head phones.
Figure 8: Navigate
Dissertation Task 2
0834060
Page 83 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix H.C – Documentation of Second Prototype, round 1 of testing
SketchFlow Map
Figure 1: SketchFlow Map
Navigation Screens
Start
Figure 2: Start
Analyze
Figure 3: Analyze
Dissertation Task 2
0834060
Page 84 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Applications
Figure 4: Applications
Contact book
Figure 5: Contact book
Information
Figure 6: Information
Dissertation Task 2
0834060
Page 85 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Navigate
Figure 8: Navigate
Navigate to
Figure 9: Navigate to
Phone
Figure 10: Phone
Dissertation Task 2
0834060
Page 86 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix H.D – Documentation of Third Prototype, round 2 of testing
SketchFlow Map
Figure 1: SketchFlow Map
Navigation Screens
Start
Figure 2: Start
Analyze
Figure 3: Analyze
Dissertation Task 2
0834060
Page 87 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Applications
Figure 4: Applications
Contact book
Figure 5: Contact book
Information
Figure 6: Information
Dissertation Task 2
0834060
Page 88 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Navigate
Figure 7: Navigate
Navigate to
Figure 8: Navigate to
Phone
Figure 9: Phone
Dissertation Task 2
0834060
Page 89 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
APPENDIX I: DEVELOPMENT AND ACTIVITY LOG
The following log documents all activities and reported bugs during the development
process of the UI. All documentation was documented in a separate reporting tool
called Redmine (n.d.).
04/11/2010
10:02
Bug #142: New list view, bottom element does not play
A bug has been discovered in the new list view function, where lists containing 2 or 4
elements will not play the bottom element when pressed. Applies only when tapping
individual elements, dragging the finger across the screen works as intended. Alexander
Dreyer Johnsen
03/11/2010
11:57
UIBLV.apk
For public test. Kim Ruben Teigen
11:56
Revision 24: Version for next public test.
Version for next public test. Kim Ruben Teigen
11:55
Revision 23: Fixes issues #130, #139 and #140.
Fixes issues #130, #139 and #140. Kim Ruben Teigen
Feature request #130 (Fixed): State elements number and total number of
elements in the current list
11:55
Kim Ruben Teigen
11:33
Bug #140 (Fixed): Possible dead space below back
Kim Ruben Teigen
11:32
Bug #139 (Fixed): Selecting an item, releasing screen and gesturing to right will
not open element
Kim Ruben Teigen
09:38
UIBLV.apk
Changes after first usertests. Kim Ruben Teigen
09:37
Revision 22: Tag for version 0.0.4.
Tag for version 0.0.4. Kim Ruben Teigen
01/11/2010
11:02
Feature request #130: State elements number and total number of elements in
the current list
Menu elements under applications should state elements number and total number of
elements in the current list. Example: 1 of 4 Facebook, 2 of 4 Mail etc. Alexander Dreyer
Johnsen
11:01
Bug #140: Possible dead space below back
There seems to be dead space/empty pixels below the back button on certain menus. Has
been confirmed on the Navigation screen. Alexander Dreyer Johnsen
Bug #139: Selecting an item, releasing screen and gesturing to right will not
open element
10:59
Certain menus are not responding correctly when opening sub-elements. It should be
possible to tap an element, release the screen for then to be able to select the same area and
gesture to right to open the element. This is workign correctly o... Alexander Dreyer Johnsen
Dissertation Task 2
0834060
Page 90 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
09:30
Feature request #132 (Fixed): Implement list navigation in Contact book,
Applications and Travel to
Applied in changeset r21. Kim Ruben Teigen
09:29
Revision 21: Made the List Activity complete. Every control works with touch.
Fixes #132.
Made the List Activity complete. Every control works with touch. Fixes #132. Kim Ruben
Teigen
28/10/2010
14:03
Revision 20: A basic list is implemented. ListView with touch functionality. An
alphabeth list on...
A basic list is implemented. ListView with touch functionality. An alphabeth list on the right to
help navigating. Kim Ruben Teigen
14:01
Feature request #132: Implement list navigation in Contact book, Applications
and Travel to
Almost done. Only need to add touch functionality to the Back button in the list. Kim Ruben
Teigen
27/10/2010
11:19
Feature request #131 (Ignored): Add "Home" functionality
Kim Ruben Teigen
10:15
Feature request #131 (On hold): Add "Home" functionality
There are some problems with the main menu top bar. The best way to implement this would
perhaps be to just add an text element at the top instead of a whole new element. Need to
discuss this with Alexander. Kim Ruben Teigen
26/10/2010
15:03
Feature request #129 (Fixed): Change the way elements are selected
Applied in changeset r19. Kim Ruben Teigen
Revision 19: Implemented methods to navigate by sliding towards the right
after the menu item is ...
15:03
Implemented methods to navigate by sliding towards the right after the menu item is chosen.
Fixes #129. Kim Ruben Teigen
Feature request #130 (On hold): State elements number and total number of
elements in the current...
12:24
Kim Ruben Teigen
11:59
Change request #136 (Ignored): Change Applications menu
Kim Ruben Teigen
11:38
Change request #135 (Fixed): Change Navigation menu
Applied in changeset r18. Kim Ruben Teigen
11:38
Revision 18: Changed some text basicly. Fixes #135.
Changed some text basicly. Fixes #135. Kim Ruben Teigen
10:54
Change request #134 (Fixed): Change of Phone menu
Applied in changeset r17. Kim Ruben Teigen
Revision 17: Changed some strings for the contact book and the phone menu.
Fixes #134.
10:54
Dissertation Task 2
0834060
Page 91 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Changed some strings for the contact book and the phone menu. Fixes #134. Kim Ruben
Teigen
10:04
Change request #134: Change of Phone menu
Due to time restrictions we will only implement simple "not implemented" feedback and not a
detailed information as wanted. Kim Ruben Teigen
09:48
Change request #133 (Fixed): Change of information menu
Applied in changeset r16. Kim Ruben Teigen
09:48
Revision 16: Added some pre text for time and date. Changed how the delay
should work with items ...
Added some pre text for time and date. Changed how the delay should work with items that
only speaks when selected. Fixes #133. Kim Ruben Teigen
09:23
Change request #137 (Closed): Documentation for version 0.0.4
Kim Ruben Teigen
Bug #128 (Fixed): The application should always inform the user of successful
opening of a sub-menu
09:21
Applied in changeset r15. Kim Ruben Teigen
Revision 15: All activities will now implement the BaseActivity and also the delay
to prevent tou...
09:21
All activities will now implement the BaseActivity and also the delay to prevent touch events.
Fixes #128. Kim Ruben Teigen
25/10/2010
Revision 14: Started to move some shared Activity values and logic into a
BaseActivity class. Add...
15:34
Started to move some shared Activity values and logic into a BaseActivity class. Added logic
to delay touch events OnResume. Kim Ruben Teigen
13/10/2010
16:13
Layout_of_UI_13102010.docx
Alexander Dreyer Johnsen
16:13
Document: Documentation for 0.0.4
Alexander Dreyer Johnsen
16:12
Change request #137: Documentation for version 0.0.4
A visual model of version 0.0.4 can be accessed from http://www.adj.no/master/v4 The
attached document provides a complete overview of all functions and layout Alexander
Dreyer Johnsen
16:10
Change request #136: Change Applications menu
Applications menu should be changed to Applications Say: Opening applications menu Web
browser Say: The web browser application will not be opened in this test. Please choose
another option. Facebook Say: The Facebook application will ... Alexander Dreyer Johnsen
16:09
Change request #135: Change Navigation menu
Navigation Say: Opening Navigation menu Your location Say: Your current location is….
Compass Display compass Travel to (Changed from Navigate to) Say: Opening Travel to
(opening sub-menu) * Home Say: Traveling to Home will not b... Alexander Dreyer Johnsen
16:06
Change request #134: Change of Phone menu
The phone menu should be changed to the following Phone Say: Opening Phone menu
Contact book Say: Opening Contact book (start of sub-menu) * * Home: Say: Calling Home
will not be provided in this test. Please choose another option. ... Alexander Dreyer Johnsen
Dissertation Task 2
0834060
Page 92 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
16:02
Change request #133: Change of information menu
Change the information menu to the following Information * Say: Opening Information menu
Time * Say: The current time is ”CURRENT TIME” Date * Say: Today’s date is ”CURRENT
DATE” Today’s weather * Say: The weather at your current ... Alexander Dreyer Johnsen
Feature request #132: Implement list navigation in Contact book, Applications
and Travel to
16:00
Implement list navigation in Contact book, Applications and Travel to. Please referrer to
visual design for implementation (http://www.adj.no/master/v3). The UI should pre-load all
applications and contacts, and only display navigation letters mat... Alexander Dreyer
Johnsen
15:58
Feature request #131: Add "Home" functionality
To improve navigation, a shortcut to the top-main menu should be introduced. The option
“Home”, should be at the top of every menu, except for the main menu” and take up half the
size of a normal menu option. Alexander Dreyer Johnsen
15:56
Feature request #130: State elements number and total number of elements in
the current list
All menu elements should state elements number and total number of elements in the
current list. Example: 1 of 4 Facebook, 2 of 4 Mail etc. This applies for all menus, including
main menu. Alexander Dreyer Johnsen
15:55
Feature request #129: Change the way elements are selected
The operation of elements should to be changed to improve navigation of the UI. Instead of
first tapping once to have an option read out and then tap one more time to select it, a
gesture should to be introduced to improve the selection of element... Alexander Dreyer
Johnsen
Bug #128: The application should always inform the user of successful opening
of a sub-menu
15:53
The application should inform the user of successful opening of a sub-menu, in addition of
informing the user when returning to the main menu. A problem was discovered in the first
round of testing, where text being read out is canceled if another... Alexander Dreyer
Johnsen
06/10/2010
08:44
Revision 13
Kim Ruben Teigen
08:43
UIBLV.apk
This was sent to test outside the house. Kim Ruben Teigen
28/09/2010
11:41
Bug #125 (Fixed): Opening string must remove colon
Applied in changeset r12. Kim Ruben Teigen
11:41
Revision 12: Fixes #125. Removed ":" from the strings.xml.
Fixes #125. Removed ":" from the strings.xml. Kim Ruben Teigen
27/09/2010
14:53
Revision 11: Alpha 2 version
Alpha 2 version Kim Ruben Teigen
14:42
Bug #125: Opening string must remove colon
When accessing one of the sub-meuns, and going back to the main menu; the voice feedback
pronounces the :. This applieas for all sub-menues except Analyze. Alexander Dreyer Johnsen
22/09/2010
Dissertation Task 2
0834060
Page 93 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
09:56
UIBLV.apk
Android install package Kim Ruben Teigen
15/09/2010
15:02
Revision 10: Added opening strings to all menues that should have them.
Added opening strings to all menues that should have them. Kim Ruben Teigen
14:02
Change request #105 (Fixed): Change several menu actions
Kim Ruben Teigen
Revision 9: Fixes #103. Added values-nb folder to hold norwegian language
strings.
14:01
Fixes #103. Added values-nb folder to hold norwegian language strings. Kim Ruben Teigen
14:00
Feature request #103 (Fixed): Norwegian language support
Kim Ruben Teigen
13:19
Revision 8: This fixes #104. Added 3 lvl menues and fixed all navigation.
This fixes #104. Added 3 lvl menues and fixed all navigation. Kim Ruben Teigen
13:18
Change request #104 (Fixed): 3 level menu system
Kim Ruben Teigen
09:30
Change request #105: Change several menu actions
Several of the menu actions should not start external applications anymore. Thay should
instead inform the user that the action is not yet implemented. Kim Ruben Teigen
09:25
Change request #104: 3 level menu system
There should be three levels of menues. This is specifically for the Phone Menu. Kim Ruben
Teigen
09:19
Feature request #103: Norwegian language support
The application should have support for Norwegian language. This is due to the fact that most
users will be Norwegians. Kim Ruben Teigen
07:39
Revision 7: Tag for versrion 0.0.1, First Alpha.
Tag for versrion 0.0.1, First Alpha. Kim Ruben Teigen
07:30
Layout_of_UI_13092010.docx
New UI description from Alexander Kim Ruben Teigen
07:30
Layout_of_UI_30082010.docx
UI description from Alexander Kim Ruben Teigen
07:29
UIBLV.apk
Android install file Kim Ruben Teigen
31/08/2010
14:52
Revision 6: Initial version done with english language as default.
Initial version done with english language as default. Kim Ruben Teigen
30/08/2010
15:44
Revision 5: Most of the menus are added. Information is finished.
Most of the menus are added. Information is finished. Kim Ruben Teigen
Dissertation Task 2
0834060
Page 94 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
27/08/2010
15:20
Revision 4: First simple menu test.
First simple menu test. Kim Ruben Teigen
23/08/2010
11:42
Revision 3: More initial import.
More initial import. Kim Ruben Teigen
11:40
Revision 2: Initial import.
Initial import. Kim Ruben Teigen
11:13
Wiki edit: Info (#1)
Kim Ruben Teigen
09:48
Revision 1: Skeleton created
Skeleton created root
Dissertation Task 2
0834060
Page 95 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
APPENDIX J: INFORMATION TO PROJECT PARTICIPANTS
The following information was provided to all participants taking part in the study.
Dissertation Task 2
0834060
Page 96 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
APPENDIX K: CONSENT FORM
All participants in the study accepted and filled out the following consent form.
Dissertation Task 2
0834060
Page 97 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
APPENDIX L: PARTICIPANT SURVEY
The following survey questionnaires were used in the first round of testing. Due to the
fact that the people participating in the study had vision loss, the questions and
responses were provided verbally and written down by the author of this report.
Appendix L.A: participant survey, round 1
Date:
Personal information
Sex
Male
Age
Type of vision
Full
If vision is low or blind, indicate how long
Born this way
Do you use a mobile phone today?
Buttons
Yes
If yes, is it operated trough
Female
Low
Blind
Since the age of ____
No
Touch screen
If no, why do you not use a mobile phone?
Rate your general technical knowledge
1 = “Not very knowledgeable”, 5 = “Very
knowledgeable”
Survey on UI
On a scale from 1 to 5, where 1 is ―strongly disagree‖ and 5 is ―strongly agree‖ please mark the
following statements
1 = “strongly disagree”, 5 = “strongly agree”
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between
menus/options
The categorization of sub-menus were logical
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
1 = “strongly disagree”, 5 = “strongly agree”
Navigation
It was easy to locate the navigation option
It was easy to locate the ―Locate me‖ option
It was easy to select one of the available pre-defined
locations
1 = “strongly disagree”, 5 = “strongly agree”
Dissertation Task 2
0834060
Page 98 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Applications
It was easy to locate the applications option
It was easy to find available applications
It was easy to launch an application
1 = ―strongly disagree‖, 5 = ―strongly agree‖
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
1 = ―strongly disagree‖, 5 = ―strongly agree‖
The solution/product
I personally felt that the menu system was limiting my
use of the mobile phone (Note: All features have not been
1 = ―strongly disagree‖, 5 = ―strongly agree
implemented in this prototype)
I prefer this solution above others
I would use this solution in my daily life
Please provide suggestions to improvements
Dissertation Task 2
0834060
Page 99 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix L.B: Participant survey, round 2
Date:
Personal information
Sex
Male
Female
Age
Type of vision
Full
If vision is low or blind, indicate how long
Born this way
Do you use a mobile phone today?
Buttons
Yes
If yes, is it operated trough
Low
Blind
Since the age of ____
No
Touch screen
If no, why do you not use a mobile phone?
Rate your general technical knowledge
1 = “Not very knowledgeable”, 5 = “Very
knowledgeable”
Survey on UI
On a scale from 1 to 5, where 1 is ―strongly disagree‖ and 5 is ―strongly agree‖ please mark the
following statements
1 = ―strongly disagree‖, 5 = ―strongly agree
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between
menus/options
The categorization of sub-menus were logical
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
1 = ―strongly disagree‖, 5 = ―strongly agree
Navigation
It was easy to locate the navigation option
It was easy to locate the ―Locate me‖ option
It was easy to select one of the available pre-defined
locations
1 = ―strongly disagree‖, 5 = ―strongly agree
Applications
It was easy to locate the applications option
It was easy to find available applications
1 = ―strongly disagree‖, 5 = ―strongly agree
Dissertation Task 2
0834060
Page 100 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
It was easy to launch an application
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
1 = ―strongly disagree‖, 5 = ―strongly agree
New select view (Travel to)
It was easy to browse through the list view letters
It was easy to locate items available in the list
It was easy to execute an item
1 = ―strongly disagree‖, 5 = ―strongly agree
Numbers in front of list elements
It makes it easier to navigate when numbers are in front
of list elements
1 = ―strongly disagree‖, 5 = ―strongly agree
The solution/product
I personally felt that the menu system was enabling and
improved my use the mobile phone (Note: All features
1 = ―strongly disagree‖, 5 = ―strongly agree
have not been implemented in this prototype)
I prefer this solution above others
I would use this solution in my daily life
Please provide suggestions to improvements
Dissertation Task 2
0834060
Page 101 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
APPENDIX M: RESSULTS FROM USER TESTING
The following appendix provides all of the results from the user testing. Round 1 is first summarized, followed by the individual data from
that round. Round 2 then follows, with a summary and individual data. The appendix concludes with a comparison of results from round 1
and round 2.
Appendix M.A: Results from round 1, Overview of all responses
Participant 1 Participant 2 Participant 3 Participant 4 Statistics
Personal Information
Sex
Age
Type of vision
Been blind since
Use mobile phones
Operated trough
Technical knowledge
SURVEY of UI
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between menus/options
The categorization of sub-menus were logical
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
Dissertation Task 2
Female
46
Low
Birth
Yes
Buttons
3
3
2
4
2
5
5
5
4
Female
50
Very low
Age 13
Yes
Buttons
2
4
4
4
2
3
3
4
4
Female
54
Blind
Birth
Yes
Buttons
3
4
N/A
5
2
4
5
4
4
Male
50
Blind
Birth
Yes
Buttons
4
Female
50,0
Split
Birth
Yes
Buttons
3,0
5
5
4
4
5
5
Score
4,0
3,7
4,3
2,5
4,3
4,5
5
5
Score
4,5
4,3
0834060
Page 102 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Navigation
It was easy to locate the navigation option
It was easy to locate the "Locate me" option
It was easy to select one of the available pre-defined locations
Applications
It was easy to locate the applications option
It was easy to find available applications
It was easy to launch an application
4
4
4
3
4
4
5
5
2
4
4
4
4
4
4
4
4
1
5
5
5
Score
4,0
4,3
4,3
5
5
5
Score
4,5
4,5
3,0
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
4
4
5
5
5
3
3
3
4
4
4
4
5
5
5
5
Score
4,5
4,0
4,3
4,3
The solution/product
I personally felt that the menu system was limiting my use of the mobile phone
I prefer this solution above others
I would use this solution in my daily life
3
1
1
2
N/A
2
2
N/A
3
2
4
3
Score
2,3
2,5
2,3
COMMON FEEDBACK & OBSERVATIONS
Negative
It is too easy to cancel what is being said by taping somewhere else
Had to remember were elements were located
Audible feedback is a little hard to understand
Dissertation Task 2
Count
4
3
3
0834060
Page 103 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Too easy to select an item
Having to lift the finger to make a selection, makes it hard to select
Skeptical to how it will be to navigate through several contacts (more than 5)
The phone is “nagging”
Felt not having control
Positive
Voice feedback
Easier to deal with text than icons
The text is bright and clear, easy to read
Liked that the number of elements were limited
Preferred list view instead of grid view
Liked the way menus were organized
It was nice to be able to use a touch phone
Practice makes you better
2
2
2
1
1
Count
3
1
1
1
1
1
1
1
1
Would have used the solution, as long as it provides access to useful
applications and features
Observations
User regularly presses to fast, hence stopping the messages from being read
The back key is not always working
The "this is a test message" is too long
If an option is pressed more than once, it will play messages the number of times
the option is pressed
The "Locate me" option is hard to locate
The options should be presented in the users native language
The feedback from this user might suggest that people with low vision
prefers grid view while blind people prefer list view
Dissertation Task 2
Count
4
1
1
3
1
1
1
0834060
Page 104 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
1
The user tried to press the screen between elements, hence not being able
to select any element
Uses the index finger to navigate
The phone can be a little slow at times
Holds the phone in the right hand, and uses the left to select
(two hand operation)
Does not read back each time it is pressed
The technical knowledge can turn out to be a challenge
Suggestions
It is easier to drag the finger left and release, than double tap to select an
element
Items could be opened by selecting/holding for a couple of seconds
It would be better to perform selections with another finger, instead of having
to tap on the same area
Should be possible to choose if text should be read out or not
Prefers the way the iPhone operates, although it can only display icons and it
is not possible to both enlarge the text and have spoken feedback
The knowledge of sales people selling mobile phones, is to low when it comes
to people with vision loss
User-friendliness is important
The phone should vibrate when the finger is on an element
It can be a good idea to define different level of information provided
to the user
Dissertation Task 2
1
1
1
1
1
Count
1
1
1
1
1
1
1
1
1
0834060
Page 105 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.B: Results from round 1, Participant 1
Test performed
29.09.2010
Personal Information
Sex
Age
Type of vision
Been blind since
Use mobile phones
Operated trough
Technical knowledge
Statistics
Female
Low
Birth
Yes
Buttons
3
SURVEY of UI
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between menus/options
The categorization of sub-menus were logical
Score
3
2
4
2
5
5
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
Score
5
4
Navigation
It was easy to locate the navigation option
It was easy to locate the "Locate me" option
It was easy to select one of the available pre-defined locations
Score
4
4
4
Applications
It was easy to locate the applications option
It was easy to find available applications
It was easy to launch an application
Score
5
5
2
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
Score
4
4
5
5
The solution/product
I personally felt that the menu system was limiting my use of the mobile phone
I prefer this solution above others
I would use this solution in my daily life
Score
3
1
1
Dissertation Task 2
0834060
Page 106 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
FEEDBACK & OBSERVATIONS
Negative
Prefers to navigate in grid view compared to list view
Too easy to hit an item
Having to lift the finger to make a selection, makes it hard to select
Positive
Voice feedback
Easier to deal with text than icons
The text is bright and clear, easy to read
Observations
User regularly presses to fast, hence stopping the messages from being read
The back key is not always working
The "this is a test message" is to long
If an option is pressed more than once, it will play messages the number of times the
option is pressed
The "Locate me" option is hard to locate
The options should be presented in the users native language
The feedback from this user might suggest that people with low vision prefers grid
view while blind people prefer list view
Suggestions
Items could be opened by selecting/holding for a couple of seconds
Should be possible to choose if text should be read out or not
Prefers the way the iPhone operates, although it can only display icons and it is not
possible to both enlarge the text and have spoken feedback
The knowledge of sales people selling mobile phones, is to low when it comes to
people with vision loss
User-friendliness is important
Dissertation Task 2
0834060
Page 107 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.C: Results from round 1, Participant 2
Test performed
STATISTICS
Personal Information
Sex
Age
Type of vision
Been blind since
Use mobile phones
Operated trough
Technical knowledge
29.09.2010
Statistics
Female
50
Low
Age 13
Yes
Buttons
2
SURVEY of UI
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between menus/options
The categorization of sub-menus were logical
Score
4
4
4
2
3
3
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
Score
4
4
Navigation
It was easy to locate the navigation option
It was easy to locate the "Locate me" option
It was easy to select one of the available pre-defined locations
Score
3
4
4
Applications
It was easy to locate the applications option
It was easy to find available applications
It was easy to launch an application
Score
4
4
4
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
Score
5
3
3
3
The solution/product
I personally felt that the menu system was limiting my use of the mobile phone
I prefer this solution above others
I would use this solution in my daily life
Score
2
N/A
2
Dissertation Task 2
0834060
Page 108 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
FEEDBACK & OBSERVATIONS
Negative
The logical placement of elements was a little hard, but can be learnt
Had to remember were elements were located
Audible feedback is a little hard to understand (Norwegian voice)
Positive
Liked that the number of elements were limited
Preferred list view instead of grid view
Liked the way menus were organized
Although the users’ vision is low, she preferred to use the audible feedback
It was nice to be able to use a touch phone
Screen reader
Observations
If you press a new element too quickly, it will overwrite the audible feedback
from the previous element
The user tried to press the screen between elements, hence not being able to
select any element
If you press an element several times, the feedback will be announced the
number of times the element was pressed
Suggestions
The phone should vibrate when the finger is on an element
Dissertation Task 2
0834060
Page 109 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.D: Results from round 1, Participant 3
Test performed
STATISTICS
Personal Information
Sex
Age
Type of vision
Been blind since
Use mobile phones
Operated trough
Technical knowledge
30.09.2010
Statistics
Female
54
Blind
Birth
Yes
Buttons
3
SURVEY of UI
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between menus/options
The categorization of sub-menus were logical
Score
4
N/A
5
2
4
5
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
Score
4
4
Navigation
It was easy to locate the navigation option
It was easy to locate the "Locate me" option
It was easy to select one of the available pre-defined locations
Score
4
4
4
Applications
It was easy to locate the applications option
It was easy to find available applications
It was easy to launch an application
Score
4
4
1
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
Score
4
4
4
4
The solution/product
I personally felt that the menu system was limiting my use of the mobile phone
I prefer this solution above others
I would use this solution in my daily life
Score
2
N/A
3
Dissertation Task 2
0834060
Page 110 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
FEEDBACK & OBSERVATIONS
Negative
It is hard to tap at the same place
Audible feedback is a little hard to understand (Norwegian voice)
The phone is “nagging”
She felt she did not have control
It is too easy to double tap
Messages are read a little slow
Does not state the current level adequately
Positive
Preferred a smaller phone, 3,2” screen
Practice makes you better
Observations
If you press a new element too quickly, it will overwrite the audible feedback
from the previous element
Uses the index finger to navigate
If you press an element several times, the feedback will be announced the
number of times the element was pressed
The phone can be a little slow at times
Holds the phone in the right hand, and uses the left to select (two hand operation)
Does not read back each time it is pressed
The technical knowledge can turn out to be a challenge
Suggestions
It can be a good idea to define different level of information provided to the user
It is easier to drag the finger left and release, than double tap to select an element
Dissertation Task 2
0834060
Page 111 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.E: Results from round 1, Participant 4
Test performed
STATISTICS
Personal Information
Sex
Age
Type of vision
Been blind since
Use mobile phones
Operated trough
Technical knowledge
30.09.2010
Statistics
Male
50
Blind
Birth
Yes
Buttons
4
SURVEY of UI
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between menus/options
The categorization of sub-menus were logical
Score
5
5
4
4
5
5
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
Score
5
5
Navigation
It was easy to locate the navigation option
It was easy to locate the "Locate me" option
It was easy to select one of the available pre-defined locations
Score
5
5
5
Applications
It was easy to locate the applications option
It was easy to find available applications
It was easy to launch an application
Score
5
5
5
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
Score
5
5
5
5
The solution/product
I personally felt that the menu system was limiting my use of the mobile phone
I prefer this solution above others
I would use this solution in my daily life
Score
2
4
3
Dissertation Task 2
0834060
Page 112 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
FEEDBACK & OBSERVATIONS
Negative
It is too easy to cancel what is being said by taping somewhere else
Skeptical to how it will be to navigate through several contacts (more than 5)
Skeptical to how it will be to navigate through several applications (more than 5)
Positive
Would have used the solution, as long as it provides access to useful applications
and features
Observations
If you press a new element too quickly, it will overwrite the audible feedback
from the previous element
Suggestions
It would be better to perform selections with another finger, instead of having to
tap on the same area
Dissertation Task 2
0834060
Page 113 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.F: Results from round 2, Overview of all responses
Participant 1 Participant 2 Participant 3 Participant 4 Participant 5 Statistics
Personal Information
Sex
Age
Type of vision
Been blind since
Use mobile phones
Operated trough
Technical knowledge
SURVEY of UI
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between
menus/options
The categorization of sub-menus were logical
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
Dissertation Task 2
Male
Female
50
Blind
Birth
Yes
Buttons
Female
54
Blind
Birth
Yes
Buttons
5
Female
46
Low
Birth
Yes
Buttons
3
Male
50
Very low
5
47
Blind
13
Yes
Buttons
3
Female
49,4
Blind
Birth
Yes
Buttons
3,6
30
Yes
Buttons
2
5
5
5
5
4
4
4
4
4
3
5
5
5
5
5
4
4
4
4
2
5
5
5
5
4
Score
4,6
4,6
4,6
4,6
3,6
5
5
5
4
5
4,8
5
5
Score
4,8
4,6
5
5
5
5
5
5
4
3
0834060
Page 114 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Navigation
It was easy to locate the navigation option
It was easy to locate the "Locate me" option
5
5
5
4
5
5
4
4
5
5
Score
4,8
4,6
Applications
It was easy to locate the applications option
It was easy to find available applications
It was easy to launch an application
5
5
5
5
5
4
5
5
4
4
4
4
5
5
5
Score
4,8
4,8
4,4
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
5
5
5
5
5
5
5
5
5
5
5
5
4
4
4
4
5
5
5
5
Score
4,8
4,8
4,8
4,8
New select view (Travel to)
It was easy to browse through the list view letters
It was easy to locate items available in the list
It was easy to execute an item
Numbers in front of list elements
It makes it easier to navigate when numbers are in front of list
elements
4
5
5
3
5
2
3
5
5
3
3
4
5
5
5
Score
3,6
4,6
4,2
4
5
2
3
5
Score
3,8
4
5
5
4
5
Score
4,6
The solution/product
I personally felt that the menu system was enabling and
improving my use of the mobile phone
Dissertation Task 2
0834060
Page 115 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
I prefer this solution above others
I would use this solution in my daily life
COMMON FEEDBACK & OBSERVATIONS
Negative
List view has too small letters
List view is too sensitive on selecting letters
4 N/A
4 N/A
Dissertation Task 2
N/A
4
5
4,0
4,3
Count
4
4
1
"Opening main menu" may seem like it is loading the menu,
and not finished opening
Wonders if elements needs to be closed
(time/date/weather)
Did not like having numbers in front of elements
The vibration is a little short
Dragging the finger sloping downward open elements
Positive
It is a good thing to have numbers in front of elements
The voice feedback is good
It is a good thing to open elements with the gesture of
dragging the finger to the right
Appreciated that feedback from the first round was
encountered for in this version
Likes that it is a list
Everything works much better now!
The whole application feels different
Has a more positive view on touch phones with this solution!
Likes that it is only displaying a window/menu at the time
It is fun to use a touch phone
4 N/A
4
1
1
1
1
Count
2
2
1
1
1
1
1
1
1
1
0834060
Page 116 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Observations
Sometimes tries to make a selection between elements
Let's go of the finger a little late on the right side
Participant normally navigates only through speech
Count
2
1
1
1
Tries to select items too fast at times, resulting in the phone
not responding fast enough
Did not consider the vibration, was listening to the voice instead
Vibration was not needed
Suggestions
Should be possible to turn numbering elements on or off
Should be possible to define the amount of text being read
The user should be able to define the necessary settings
Vibration should be stronger
Should be possible to turn vibration on or off
It should be possible to search in a list, not just selecting the
first letter
Numbers are good on larger lists, but not on smaller lists
Instead of having an element called back, introduce a gesture
were dragging the finger to the left will go back one menu
An individual not used to syntactical voice would soon get
tired of it
Element number should be read after the element name,
not in front
Dissertation Task 2
1
1
Count
4
2
2
1
1
1
1
1
1
1
0834060
Page 117 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.G: Results from round 2, Participant 1
Test performed
04.11.2010
Personal Information
Sex
Age
Type of vision
Been blind since
Use mobile phones
Operated trough
Technical knowledge
Statistics
Male
50
Blind
Birth
Yes
Buttons
5
SURVEY of UI
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between menus/options
The categorization of sub-menus were logical
Score
5
5
5
5
4
5
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
Score
5
5
Navigation
It was easy to locate the navigation option
It was easy to locate the "Locate me" option
Score
5
5
Applications
It was easy to locate the applications option
It was easy to find available applications
It was easy to launch an application
Score
5
5
5
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
Score
5
5
5
5
New select view (Travel to)
It was easy to browse through the list view letters
It was easy to locate items available in the list
It was easy to execute an item
Score
4
5
5
Dissertation Task 2
0834060
Page 118 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Numbers in front of list elements
It makes it easier to navigate when numbers are in front of list elements
Score
4
The solution/product
I personally felt that the menu system was enabling and improving my use of the
mobile phone
I prefer this solution above others
I would use this solution in my daily life
Score
4
4
4
FEEDBACK & OBSERVATIONS
Negative
List view has too small letters
List view is too sensitive on selecting letters
"Opening main menu" may seem like it is loading the menu, and not finished opening
Positive
It is a good thing to have numbers in front of elements
Observations
Suggestions
It should be possible to turn off numbering elements
Should be possible to define the amount of text being read
Dissertation Task 2
0834060
Page 119 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.H: Results from round 2, Participant 2
Test performed
04.11.2010
Personal Information
Sex
Age
Type of vision
Been blind since
Use mobile phones
Operated trough
Technical knowledge
Statistics
Female
54
Blind
Birth
Yes
Buttons
3
SURVEY of UI
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between menus/options
The categorization of sub-menus were logical
Score
4
4
4
4
3
5
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
Score
5
5
Navigation
It was easy to locate the navigation option
It was easy to locate the "Locate me" option
Score
5
4
Applications
It was easy to locate the applications option
It was easy to find available applications
It was easy to launch an application
Score
5
5
4
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
Score
5
5
5
5
New select view (Travel to)
It was easy to browse through the list view letters
It was easy to locate items available in the list
It was easy to execute an item
Score
3
5
2
Dissertation Task 2
0834060
Page 120 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Numbers in front of list elements
It makes it easier to navigate when numbers are in front of list elements
Score
5
The solution/product
I personally felt that the menu system was enabling and improving my use of the
mobile phone
I prefer this solution above others
I would use this solution in my daily life
Score
5
N/A
N/A
FEEDBACK & OBSERVATIONS
Negative
Wonders if elements needs to be closed (time/date/weather)
List view is too sensitive on selecting letters
List view has too small letters
Positive
It is a good thing to have numbers in front of elements
It is a good thing to open elements with the gesture of dragging the finger to the right
Appreciated that feedback from the first round was encountered for in this version
Observations
Let's go of the finger a little late on the right side
Sometimes tries to make a selection between elements
Suggestions
It should be possible to turn off numbering elements
Should be possible to define the amount of text being read
The user should be able to define the necessary settings
Vibration should be stronger
Dissertation Task 2
0834060
Page 121 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.I: Results from round 2, Participant 3
Test performed
05.11.2010
Personal Information
Sex
Age
Type of vision
Been blind since
Use mobile phones
Operated trough
Technical knowledge
Statistics
Female
46
Low
Birth
Yes
Buttons
3
SURVEY of UI
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between menus/options
The categorization of sub-menus were logical
Score
5
5
5
5
5
5
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
Score
5
5
Navigation
It was easy to locate the navigation option
It was easy to locate the "Locate me" option
Score
5
5
Applications
It was easy to locate the applications option
It was easy to find available applications
It was easy to launch an application
Score
5
5
4
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
Score
5
5
5
5
New select view (Travel to)
It was easy to browse through the list view letters
It was easy to locate items available in the list
It was easy to execute an item
Score
3
5
5
Dissertation Task 2
0834060
Page 122 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Numbers in front of list elements
It makes it easier to navigate when numbers are in front of list elements
Score
2
The solution/product
I personally felt that the menu system was enabling and improving my use of the
mobile phone
I prefer this solution above others
I would use this solution in my daily life
Score
5
4
4
FEEDBACK & OBSERVATIONS
Negative
Did not like having numbers in front of elements
The vibration is a little short
The voice feedback is good
List view is too sensitive on selecting letters
List view has too small letters
Positive
Likes that it is a list
Everything works much better now!
The whole application feels different
Observations
Normally navigates only trough speech
Sometimes tries to make a selection between elements
Tries to select items too fast at times, resulting in the phone not responding fast enough
Suggestions
Should be possible to turn numbers off
Should be possible to define settings
Dissertation Task 2
0834060
Page 123 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.J: Results from round 2, Participant 4
Test performed
05.11.2010
Personal Information
Sex
Age
Type of vision
Been blind since
Use mobile phones
Operated trough
Technical knowledge
Statistics
Female
50
Very low
13
Yes
Buttons
2
SURVEY of UI
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between menus/options
The categorization of sub-menus were logical
Score
4
4
4
4
2
4
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
Score
4
3
Navigation
It was easy to locate the navigation option
It was easy to locate the "Locate me" option
Score
4
4
Applications
It was easy to locate the applications option
It was easy to find available applications
It was easy to launch an application
Score
4
4
4
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
Score
4
4
4
4
New select view (Travel to)
It was easy to browse through the list view letters
It was easy to locate items available in the list
It was easy to execute an item
Score
3
3
4
Dissertation Task 2
0834060
Page 124 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Numbers in front of list elements
It makes it easier to navigate when numbers are in front of list elements
Score
3
The solution/product
I personally felt that the menu system was enabling and improving my use of the
mobile phone
I prefer this solution above others
I would use this solution in my daily life
Score
4
N/A
4
FEEDBACK & OBSERVATIONS
Negative
Dragging the finger sloping downward open elements
List view is too sensitive on selecting letters
List view has too small letters
Positive
Has a more positive view on touch phones with this solution!
Observations
Did not consider the vibration, was listening to the voice instead
Suggestions
It should be possible to search in a list, not just selecting the first letter
Numbers are good on larger lists, but not on smaller lists
Dissertation Task 2
0834060
Page 125 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.K: Results from round 2, Participant 5
Test performed
Personal Information
Sex
Age
Type of vision
Been blind since
Use mobile phones
Operated trough
Technical knowledge
20.11.2010
Statistics
Male
47
Blind
30
Yes
Buttons
5
SURVEY of UI
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between menus/options
The categorization of sub-menus were logical
Score
5
5
5
5
4
5
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
Score
5
5
Navigation
It was easy to locate the navigation option
It was easy to locate the "Locate me" option
Score
5
5
Applications
It was easy to locate the applications option
It was easy to find available applications
It was easy to launch an application
Score
5
5
5
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
Score
5
5
5
5
New select view (Travel to)
It was easy to browse through the list view letters
It was easy to locate items available in the list
It was easy to execute an item
Score
5
5
5
Dissertation Task 2
0834060
Page 126 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Numbers in front of list elements
It makes it easier to navigate when numbers are in front of list elements
Score
5
The solution/product
I personally felt that the menu system was limiting my use of the mobile phone
I prefer this solution above others
I would use this solution in my daily life
Score
5
N/A
5
FEEDBACK & OBSERVATIONS
Negative
Positive
Likes that it is only displaying a window/menu at the time
Likes the voice feedback
It is fun to use a touch phone
Observations
Vibration was not needed
Suggestions
Instead of having an element called back, introduce a gesture were dragging the
finger to the left will go back one menu
An individual not used to syntactical voice would soon get tired of it
Should be possible to turn vibration on or off
Should be possible to turn numbering elements on or off
Element number should be read after the element name, not in front
Dissertation Task 2
0834060
Page 127 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.L: Results from round 1 and round 2 compared against each other
Part. 1
STATISTICS
Personal Information
Sex
Age
Type of vision
Been blind since
Use mobile phones
Operated trough
Technical knowledge
SURVEY of UI
Menu system
The menu system was easy to use
The menu system made the touch
phone easier to use
Part. 2
Part. 3
Part. 4
Round 1 Part. 1
Female Female Female Male Female Male
46
50
54
50
50,0
50
Low Very low Blind
Blind
Split Blind
Birth
13
Birth
Birth
Birth Birth
Yes
Yes
Yes
Yes
Yes
Yes
Buttons Buttons Buttons Buttons Buttons Buttons
3
2
3
4
3,0
5
Round 2 Change
Part. 2
Part. 3
Part. 4
Part. 5
Female
54
Blind
Birth
Yes
Buttons
3
Female
46
Low
Birth
Yes
Buttons
3
Female
50
Very low
13
Yes
Buttons
2
Male
Female Female
47
49,4
49,3
Blind
Blind
Blind
30
Birth
Birth
Yes
Yes
Yes
Buttons Buttons Buttons
5
3,6
0,6
3
2
4
4
4
N/A
5
5
4,0
3,7
5
5
4
4
5
5
4
4
5
5
4,6
4,6
0,6
0,9
The options spoken was easy to
understand
4
4
5
4
4,3
5
4
5
4
5
4,6
0,4
It was easy to navigate between
menus and sub-menus
2
2
2
4
2,5
5
4
5
4
5
4,6
2,1
The vibration made it easier to
change between menus/options
5
3
4
5
4,3
4
3
5
2
4
3,6
-0,7
The categorization of sub-menus
were logical
Average
5
3
5
5
4,5
5
5
5
4
5
4,8
0,3
Dissertation Task 2
3,9
4,5
0,6
0834060
Page 128 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Phone
It was easy to locate the phone
option
5
4
4
5
4,5
5
5
5
4
5
4,8
0,3
It was easy to navigate through
phone contacts
Average
4
4
4
5
4,3
5
5
5
3
5
4,6
0,4
Navigation
It was easy to locate the navigation
option
It was easy to locate the "Locate
me" option
It was easy to select one of the
available pre-defined locations
Average
Applications
It was easy to locate the
applications option
It was easy to find available
applications
It was easy to launch an application
Average
Dissertation Task 2
4,4
4,7
0,3
4
3
4
5
4,0
5
5
5
4
5
4,8
0,8
4
4
4
5
4,3
5
4
5
4
5
4,6
0,4
4
4
4
5
4,3
4,3
4,1
4,7
0,6
5
4
4
5
4,5
5
5
5
4
5
4,8
0,3
5
4
4
5
4,5
5
5
5
4
5
4,8
0,3
2
4
1
5
3,0
5
4
4
4
5
4,4
1,4
4,0
4,7
0,7
0834060
Page 129 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Information
It was easy to locate the
information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays
weather is
Average
New select view (Travel to)
It was easy to browse through the
list view letters
It was easy to locate items available
in the list
It was easy to execute an item
Average
4
5
4
5
4,5
5
5
5
4
5
4,8
0,3
4
5
5
3
3
3
4
4
4
5
5
5
4,0
4,3
4,3
5
5
5
5
5
5
5
5
5
4
4
4
5
5
5
4,8
4,8
4,8
0,8
0,6
0,6
4,3
4,8
0,6
4
3
3
3
5
3,6
3,6
5
5
5
3
5
4,6
4,6
5
2
5
4
5
4,2
4,2
4,1
Numbers in front of list elements
It makes it easier to navigate when
numbers are in front of list
elements
Average
Dissertation Task 2
4
5
2
3
5
3,8
3,8
3,8
0834060
Page 130 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
The solution/product
I personally felt that the menu
system was enabling and improving
my use of the mobile phone
I prefer this solution above others
I would use this solution in my daily
life
Average
Dissertation Task 2
3
2
2
2
2,3
4
5
5
4
5
4,6
2,4
1
1
N/A
2
N/A
3
4
3
2,5
2,3
4
4
N/A
N/A
4
4
N/A
4
N/A
5
4,0
4,3
1,5
2,0
2,3
4,3
2,0
0834060
Page 131 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.M: T-Test and Effect sizes
While the Design Research method does not require statistical analyses, these were
nevertheless carried out to shed more light on the changes in scoring that were evident
between the two versions of the UI. Effect sizes and differences between means were
evaluated across the categories previously outlined. Due to the small sample size, a
certain measure of leniency with respect to level of significance was judged
necessary; this was therefore set to 0.1. Thus mean scores, available in figure 7, were
found to be significantly higher for the second round of testing, compared to the first
round, for the navigation functions (t(3) = 2.45, p>0.1), for the information functions
(t(3) = 2.45, p>0.1), and for the solution functions (t(3) = 5.44, p>0.05). Effect sizes
were judged to be high for all three functions (r = 0.41; r = 0.40; r = 0.89;
respectively). Effect sizes were similarly high for the menu functions (r = 0.37) and
the application functions (r = 0.41), but the differences between means were nonsignificant (t(3) = 1.47, ns; t(3) = 1.48, ns; respectively).
Paired Samples Test
Paired Differences
Std. Error 95% Confidence Inter.
Mean
Std. Dev.
Mean
Lower
Upper
t
df
Sig.
Pair 1 Menu_1 - Menu_2
-.50000
.68041
.34021
-1.58269
.58269
-1.470
3
.238
Pair 2 Phone_1 - Phone_2
-.25000
.64550
.32275
-1.27713
.77713
-.775
3
.495
Pair 3 Nav_1 - Nav_2
-.50000
.40825
.20412
-1.14961
.14961
-2.449
3
.092
Pair 4 App_1 - App_2
-.58333
.78764
.39382
-1.83664
.66997
-1.481
3
.235
Pair 5 Info_1 - Info_2
-.50000
.40825
.20412
-1.14961
.14961
-2.449
3
.092
Pair 6 Solu_1 - Solu_2
-2.04167
.75000
.37500
-3.23508
-.84825
-5.444
3
.012
* Contrast marked in green is significant to the 0.05 level
(0.05 is standard: 95% chance that the difference is not due to coincidence)
* Contrast marked in blue is significant to the 0.10 level
(0.10 is less used, but can be justified due to the low number of participants:
90% chance that the difference is not due to coincidence)
Effect sizes
d
r
r2
Pair 1
Menu_1 - Menu_2
0.80418
0.37306
0.13917
Pair 2
Phone_1 - Phone_2
0.39736
0.19487
0.03797
Pair 3
Nav_1 - Nav_2
0.89443
0.40825
0.16667
Pair 4
App_1 - App_2
0.89866
0.40986
0.16798
Pair 5
Info_1 - Info_2
0.86602
0.39736
0.15789
Pair 6
Solu_1 - Solu_2
3.84971
0.88739
0.78746
Dissertation Task 2
0834060
Page 132 of 132
MSc Information Systems Management
Academic Year 2009-2010
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Alexander Dreyer Johnsen - 0834060
A Dissertation submitted in partial fulfillment of the requirement for the degree of
Master of Science
Brunel University
Department of Information Systems and Computing
Uxbridge, Middlesex UB8 3PH
United Kingdom
Tel: +44 (0) 1895 203397
Fax: +44 (0) 1895 251686
Dissertation Task 2
0834060
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
ABSTRACT
The mobile phone enjoys increased popularity, providing new means of connectivity and
functionality. Today most phones comes equipped with touch-based screens, enabling
the user to interact in an easier and more efficient way, compared to standard buttons.
However, such screens require visual navigation, ruling out access for the visually
impaired; evidently, modern phones are not designed for this user group.
By analyzing the mobile market, available solutions, and current technology, it was
found that neither the society, nor manufacturers of products and services, is designing
for the visually impaired. Thus, this group is denied access to the numerous services and
possibilities sighted people enjoy.
However, it is possible to operate mobile phones through the use of applications called
screen readers; still, these applications have proven to be ineffective and less than userfriendly on touch screens. Hence, this dissertation sets out to find an alternative
approach; to construct a solution that will make touch-based mobile phones accessible
for the visually impaired.
Design research was chosen as the methodology for the project. Design research
highlights the importance of developing a solution over the course of several iterations,
and to perform product evaluation using external participants. A total of five iterations
were carried out, resulting in several artifacts and a prototype for a user interface. The
prototype was designed to replace the phone’s own user interface and provide an easy
and intuitive way of operating a touch-based mobile phone.
Through the process of developing the user interface, virtual prototypes and other
artifacts were created. The virtual prototypes turned out to be of great advantage,
communicating the vision and potentials of the final product to the stakeholders. In
addition, the experience from the project shows that a successful development project
should produce several iterations, have well-documented artifacts and perform external
user testing.
The new user interface was developed for the Android OS to replace the phone’s own
user interface. Operation relies on voice and haptic feedback, where the user receives
information when tapping or dragging the finger across the screen. The proposed
solution is unique in many ways, it keeps gestures to a minimum, it does not rely on
physical keys, and it presents a menu layout similar to most Nokia mobile phones.
Dissertation Task 2
0834060
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
ACKNOWLEDGEMENTS
The process of writing this dissertation has been long and exhausting, and would not
have been possible without the involvement and support from several people; for this I
am grateful.
First, I would like to thank my supervisor Bendik Bygstad for his guidance and academic
support throughout the project. It has been indispensable and a key factor for the
accomplishment of this dissertation.
Secondly, I would like to thank Tor Ulland at Huseby Resource Centre for the blind,
for taking an interest in the project and for sharing his knowledge and insights on life
without vision. Ulland also acquired all of the participants for the evaluations,
ensuring the completion of the project
Without the involvement of May-Britt Haug, at The Norwegian Association of the Blind
and Partially Sighted, I would not have had the possibility of getting in touch with
Huseby or Tor Ulland. Thank you for believing in the project.
I would also like to thank Magne Gabrielsen, Gaby Groff-Jensen and Knut Beck at
SmartPhones Telecom for believing in the project, providing both financial and
developmental resources. Kim Ruben Teigen, whose development skills ensured the
realization of the User Interface, a key contribution to the success of the project.
A special thank you to my wife Ragnhild Eg, for her continued support throughout the
dissertation. You have stayed up countless nights proofreading, and have continued to
support me during the entire process.
I would also like to thank my family, friends, fellow students and colleagues for the
continued support during the process of writing the dissertation.
Last, but not least, I would like to thank the anonymous participants for spending their
spare time on evaluating and providing feedback on the User Interface. Not only once,
but twice!
Thank you!
I certify that the work presented in the dissertation is my own unless referenced
Signature: .........................................
Date............31.01.2011....................
TOTAL NUMBER OF WORDS: 13.031
Dissertation Task 2
0834060
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
TABLE OF CONTENTS
Chapter 1: Introduction .................................................................................................. 7
1.1 Problems that people with vision loss face .................................................. 7
1.2 Back to society ............................................................................................. 8
1.3 Research aim and objectives ........................................................................ 8
1.4 Research approach ....................................................................................... 9
1.5 Dissertation outline ...................................................................................... 9
Chapter 2: Literature review ........................................................................................ 10
2.1 Equal opportunities .................................................................................... 10
2.2 The mobile market ..................................................................................... 11
2.3 Potential problems with smartphones ........................................................ 11
2.4 Improving compatibility ............................................................................ 11
2.5 Assistive technology .................................................................................. 12
2.6 Screen reader .............................................................................................. 12
2.7 Reading and input of text ........................................................................... 13
2.8 Haptics ....................................................................................................... 15
2.9 Making a better user interface.................................................................... 15
2.10 Turning the mobile phone into an assistive aid ....................................... 16
2.11 Framework ............................................................................................... 16
Chapter 3: Research Method ........................................................................................ 18
3.1 Design research .......................................................................................... 18
3.2 Awareness of problem ............................................................................... 20
3.3 Suggestion .................................................................................................. 20
3.4 Development .............................................................................................. 21
3.5 Evaluation .................................................................................................. 22
3.6 Conclusion ................................................................................................. 24
Chapter 4: Research results .......................................................................................... 25
4.1 Results in regards to development ............................................................. 25
4.2 Results in regards to testing ....................................................................... 29
Chapter 5: Discussion .................................................................................................. 34
5.1 Design as an Artifact .................................................................................. 34
5.2 Problem relevance ...................................................................................... 35
5.3 Design evaluation....................................................................................... 35
5.4 Research contributions ............................................................................... 36
5.5 Research rigor ............................................................................................ 36
5.6 Design as a Search progress ....................................................................... 36
5.7 Communication of research ....................................................................... 36
5.8 Summary of discussion .............................................................................. 37
Chapter 6: Critical evaluation of research ................................................................... 38
Chapter 7: Conclusion.................................................................................................. 40
7.1 Summary of the dissertation ...................................................................... 40
7.2 Future research and development .............................................................. 41
Dissertation Task 2
0834060
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
References .................................................................................................................... 42
Appendix A: Ethical approval ..................................................................................... 52
Appendix B: About the author ..................................................................................... 53
Appendix C: The mobile market.................................................................................. 54
Appendix C.A - The new players .................................................................... 54
Appendix D: Using the mobile phone for assitive aid ................................................. 55
Appendix D.A - Object recognition ................................................................. 55
Appendix D.B - Navigation ............................................................................. 55
Appendix E: Interview with Tor Ulland at Huseby (Statped) ..................................... 57
Appendix F: Project plan ............................................................................................. 60
Appendix G: Project meeting reports .......................................................................... 61
Appendix G.A - Initial project workshop meeting, June 14, 2010 .................. 61
Appendix G.B - Approval of functionality, June 25, 2010 .............................. 63
Appendix G.C - Layout of UI, August 30, 2010 ............................................. 66
Appendix G.D - Layout of UI, September 13, 2010 ........................................ 68
Appendix G.E - Layout of UI, October 10, 2010 ............................................ 70
Appendix G.F - Layout of UI, October 13, 2010............................................. 73
Appendix H: Documentation of ui ............................................................................... 76
Appendix H.A – Documentation of UI, version 0.0.5 ..................................... 76
Appendix H.B – Documentation of Conceptual Design .................................. 79
Appendix H.C – Documentation of Second Prototype, round 1 of
testing ................................................................................................... 84
Appendix H.D – Documentation of Third Prototype, round 2 of testing ........ 87
Appendix I: Development and activity log .................................................................. 90
Appendix J: Information to project participants .......................................................... 96
Appendix K: Consent form .......................................................................................... 97
Appendix L: Participant Survey................................................................................... 98
Appendix L.A: participant survey, round 1 ..................................................... 98
Appendix L.B: Participant survey, round 2 ................................................... 100
Appendix M: Ressults from user testing .................................................................... 102
Appendix M.A: Results from round 1, Overview of all responses ................ 102
Appendix M.B: Results from round 1, Participant 1 ..................................... 106
Appendix M.C: Results from round 1, Participant 2 ..................................... 108
Appendix M.D: Results from round 1, Participant 3 ..................................... 110
Appendix M.E: Results from round 1, Participant 4 ..................................... 112
Appendix M.F: Results from round 2, Overview of all responses ................ 114
Appendix M.G: Results from round 2, Participant 1 ..................................... 118
Dissertation Task 2
0834060
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.H: Results from round 2, Participant 2 ..................................... 120
Appendix M.I: Results from round 2, Participant 3....................................... 122
Appendix M.J: Results from round 2, Participant 4 ...................................... 124
Appendix M.K: Results from round 2, Participant 5 ..................................... 126
Appendix M.L: Results from round 1 and round 2 compared against
each other ........................................................................................... 128
Appendix M.M: T-Test and Effect sizes........................................................ 132
LIST OF TABLES
Table 1 - Framework for the top issues people with vision loss encounter when using
mobile phones with touch screen ........................................................................................ 17
Table 2 - Design Research Guidelines by Hevner et al. (2006) .......................................... 20
Table 3 - Tasks the participants were asked to perform ........................................................ 22
Table 4 - Survey completed by participants .............................................................................. 23
Table 5 - Additional tasks presented to participants ............................................................... 24
Table 6 - Additional survey questions ........................................................................................ 24
Table 7 – Summary of survey categories ................................................................................... 30
Table 8 - Table showing subjective feedback from round two ........................................... 33
Table 9 - Overview on aims and objectives .............................................................................. 38
LIST OF FIGURES
Figure 1- Design Research process model by Vaishnavi and Kuechler (2007) ............. 19
Figure 2 - Some of the menus available in the UI ................................................................... 26
Figure 3 - List navigation in the UI ............................................................................................. 26
Figure 4 - Conceptual UI prototype for people with vision loss ......................................... 27
Figure 5 - Flow map for navigation in the UI........................................................................... 28
Figure 6 - Conceptual model of application.............................................................................. 28
Figure 7 - Graph displaying mean scores from the first and second round of testing .. 30
Figure 8 - Graph displaying a comparison between results from first and second round
of testing on the menu system ............................................................................................. 31
Figure 9 - Graph displaying a comparison between results from first and second round
of testing on the complete solution .................................................................................... 32
Dissertation Task 2
0834060
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
CHAPTER 1: INTRODUCTION
1.1 Problems that people with vision loss face
According to the World Health Organization (WHO) (2009), around 314 million people are
visually impaired, of which approximately 45 million are blind. Of the total number, 12
million are children, 82% are of age 50 or older; furthermore, women have the greatest risk of
becoming visually impaired. Developing countries have the largest representation of visually
impaired people, with around 87% representation. Visual impairment blindness can be
defined as the collective term ―vision loss‖, which refers to either the loss of the ability to see,
or vision reduction. The terms ―low vision‖, partially sighted, or visually impaired, can be
used for a person who has not lost the capability to see, but whose vision is significantly
reduced compared to normal vision (Colenbrander, 2002).
Both groups deal with daily situations that vary greatly depending on the severity of their
visual impairment. A blind person will have to rely on other senses and inputs, such as touch
and hearing, as well as assistive aids, such as the long cane and the guide dog. On the other
hand, an individual with low vision can be aided by visual enhancements, like large print,
magnifiers and illumination (Colenbrander, 2002).
Common for both groups is their encounters with situations and problems that a sighted
person would not consider an issue. This can be seen in everyday situations, where the
environment is designed for the sighted, not someone with vision loss. Accessing stores and
businesses, or simply crossing the street, can turn out to be challenging tasks. Much of our means
of communication is through the use of signs and signals; visual symbols that a person with
vision loss cannot see. For example, danger signs or signs providing direction, road blocks or
general information on public transportation. At worst, situations like these may prevent a person
from wanting to step outside, hence limiting contact with the surrounding world (Tjan et al.
2005; Joseph, 2009; Maines, 2008; Appendix E).
The same restrictions apply to other ordinary situations; TV’s, radios, mobile phones, stoves and
ATM’s are just some examples of equipment that are becoming increasingly advanced. In the
past, such items were mostly equipped with buttons; although not originally designed for people
with vision loss, they made it possible to memorize the steps in order to access a certain feature.
With today’s modern design, with touch screens showing dynamic menus; it has become
impossible for a person with vision loss to memorize and use such equipment. It can be argued
that companies do not consider this user group when designing new products (Picard, 2010;
Appendix E).
Another issue facing people with vision loss is the difficulty some sighted people have when
encountering blind people, making it hard for the latter to develop new relationships. Most jobs
are also designed for the sighted. Due to this, blind people do not meet the same expectations and
are often relegated to specific roles. This is an undesirable situation as employers may lose out
on valuable skills and those who lack vision are left unable to prove their potential. Society
should strive for quality and for implementing people with vision loss into the working
environment (The National Federation of the Blind of Connecticut, n.d.).
Dissertation Task 2
0834060
Page 7 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
1.2 Back to society
Several ideologies and assumptions about blindness and rehabilitation exist. One of the more
accepted is the ―restorative approach‖, embraced by Father Thomas Carroll (American Printing
House for the Blind, 2010). This approach works under the idea that most blind people could,
with the help of professional counseling and training, live full lives. Seven basic losses are highlighted, and the focus is on restoring these through training, with the white cane or a guide dog,
learning to read Braille and using assistive technology (R. A. Scott, 1995). With the correct
equipment and training, a person with vision loss can master ordinary tasks like operating a
computer, reading a book or using mobile phones (Appendix E).
People with vision loss can also participate in sports; blind Soccer is a particular example of
how well correct training in applying other senses can enable a blind person to participate in
team activities. Players are able to play soccer in almost the same way as a sighted person by
relying on shouted commands and specially designed soccer balls, containing ball bearings
(Malinowski, 2010).
1.3 Research aim and objectives
While it is clear that the technology and the will to integrate those with vision loss into society
are strongly present, society is not yet properly adapted. Several aspects can be improved,
where one is the mobile phone.
The mobile phone introduces several benefits, but perhaps the most important is the easy
access to communication with friends, family and the surrounding world. However, most new
mobile phones are designed for visual navigation, rendering the mobile phone inaccessible for
people with vision loss. Designing a phone that is inaccessible for people with vision loss can
at worst result in loss of contact with society, thus the author of this project believes in the
importance of making mobile phones not only accessible, but easy to use, for people with
vision loss.
The aim of this dissertation is to present, develop and evaluate a new User Interface (UI) for
touch-based mobile phones, which will make this type of phones available for people with
vision loss.
Based on the aim of developing a UI, the following objectives are presented:
A literature review on issues related to the operation of touch-based mobile phones
and available assistive aids and technologies
Create a framework for designing the UI
Perform an evaluation of the UI through several iterations; both internal and external
Discussion on the results from the project
Dissertation Task 2
0834060
Page 8 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
1.4 Research approach
The project uses Design research method for developing and testing the UI for touch-based
mobile phones. Design research is designed with development and testing in mind,
encouraging projects to create and deliver several versions of a solution, where major releases
are tested on external participants to provide feedback (Hevner et al. 2006; Vaishnavi &
Kuechler, 2007).
Two versions of the solution were tested on external users, allowing them to provide feedback
and comments on the interfaces. Feedback from the first version was used to improve the
second version.
1.5 Dissertation outline
The dissertation report is organized as follows:
Chapter 2: Presentation of literature, research and the current mobile market relating to people
with vision loss.
Chapter 3: The research method Design research is outlined along with documentation of the
steps followed throughout the project.
Chapter 4: Research results are presented, analyzing the different between the two tested
versions.
Chapter 5: Critical discussion comparing the findings from the literature review with the
results from the evaluation of the UI.
Chapter 6: The processes and the research methodology are critically evaluated.
Chapter 7: The report concludes with a summary of the previous discussions and a highlight
of the contributions to the existing research field, with future research suggestions.
Dissertation Task 2
0834060
Page 9 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
CHAPTER 2: LITERATURE REVIEW
The research field on vision loss encompasses several areas of interest, where this
Dissertation focuses on how people with vision loss can operate mobile phones with touch
screens. Hence, this chapter is divided into several subjects starting with rights of people with
vision loss, followed by a description of the current mobile market, for then to present
available assistive aids and technology. The chapter ends in a framework, used to design the
UI.
2.1 Equal opportunities
It goes without saying that people with vision loss have the same rights as sighted people; yet
the misconception that vision loss reduces work efficiency is a common prejudice (Wall,
2003). A Norwegian report on job opportunities for people with disabilities concluded that
this user group has the largest share of unemployed potential workers compared to the rest of
the population (ECON, 2003). However, a different report that looks into people’s experience
with moving from school to work life, suggests that part of the problem is based on lack of
knowledge and improper administration by government organizations (Berge, 2007).
Several organizations are working towards equal rights for people with vision loss; eliminate
prejudice, integration with society, achieve equal rights and benefits and provide aid to
countries and people struggling with diseases causing blindness.
World Blind union (n.d.) (WBU) is an internationally recognized organization that represents
160 million people with vision loss in 177 member countries; as a universal voice, it aims to
achieve equal rights and opportunities in all aspects of society. However, WBU does not
provide direct services such as training, guidance and access to assistive technology (AFB,
n.d.; NABP, n.d.). These services are designated to local and national organizations, like the
American Foundation for the Blind and The Norwegian Association of the Blind and Partially
Sighted (NABP).
Vision 2020 is a joint cooperation between the WHO, the International Agency for the
Prevention of Blindness (IAPB) and professionals within the field. The main focus is to
eliminate the main causes of avoidable blindness by the year 2020 ant to prevent 100 million
people from becoming blind (Vision 2020, 2009; International Agency for the Prevention of
Blindness, 2010).
Organizations are not the only means for support for people with vision loss. Several
countries have also implemented rules to protect the rights of people with vision loss. In the
United Kingdom, the Disability Discrimination Act states that a person should not be treated
less favorable because of his or her disability. The European Union has introduced a similar
act, which directs its member countries to introduce measures to reduce discrimination against
people with disabilities (Wall, 2003). Norway has taken it a step further with the introduction
of a new discrimination and accessibility law, which state that all new products marketed
towards the general public should be equally accessible to all, regardless of personal
limitations or handicaps (Steria, 2009).
Dissertation Task 2
0834060
Page 10 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
2.2 The mobile market
The mobile phone market enjoys increased popularity, with market shares expanding every
day (IDC 2010), it is now considered larger than the PC market (Neset, 2010). The mobile
market consists mainly of two types of mobile phones; feature phones and smartphones.
Where feature phones are considered low-end phones, with limited features and computer
power (Nusca, 2010; Wikipedia, 2010a), smartphones offer more advanced computing power
and operating systems, as well as greater connectivity; they are essentially small mobile
computers (Wikipedia, 2010b).
During the first quarter of 2010, a total of 314.7 million mobile phones were sold to end users
worldwide, with smartphones making up 54.3 million of the sales (Gartner, 2010b); this is an
increase of 17% compared to the same period in 2009. Although, feature phones are still
considered the platform with the largest sales volume, smartphones have had a positive
increase and sales are expected to increase further in the coming years (IDC, 2010).
According to Gartner (2010) the top five OS for smartphones are; Symbian (44,3%),
Blackberry (19.4%), Apple iOS (15.4%), Google Android (9.6%) and Windows Phone
(6.8%). Apple iOS and Google Android are currently the fastest growing (The Nielsen
Company, 2010) and it is estimates that the Android OS will be the second largest OS
worldwide in 2010 and it will challenge Symbian’s top ranking position in 2014 (Gartner,
2010a). The numbers show that smartphones sales are increasing, suggesting that the market
wants more advanced phones, with more functionality and better connectivity.
A more detailed view on the mobile market and its actors is available in Appendix C.
2.3 Potential problems with smartphones
While smartphones come with a range of additional features, there are drawbacks. Studies
have shown that the majority of users only take advantage of a small portion of the
functionalities available (Gomnæs, 2005). In addition, the touch screen can make it more
difficult to type, as no physical feedback is provided. Nevertheless, the increasing sales
indicate that most sighted people do not consider these factors as show stoppers. However,
this is not the case for those with vision loss.
The majority of information on a mobile phone is presented through graphical means,
rendering access almost impossible for a person with vision loss. A touch-based mobile phone
becomes even harder to access with a touch-based visual design and navigation that contains
no physical representation of where or how to press buttons and icons. With these limitations,
it seems likely that a large user group will be unable to use these types of mobile phones,
segregating them further from the general population. This is also in contradiction with laws
set by the government (Meyers, 2008).
2.4 Improving compatibility
Studies on mobile phone accessibility for elderly and people with disabilities; all conclude
that mobile phones are not designed for these user groups. They point out several aspects that
could improve mobile phone accessibility. Mobile phones should be of adequate size and
shape and have texture with good grip. The screen should be large and the buttons should
have a logical placement for easier memorization of layout. Voice feedback should provide
information and confirm execution of commands. The phone should also provide easy access
to emergency numbers. Finally, the number of features should be kept to a minimum to ensure
ease of use (Abascal & Civit, 2001; Plos & Buisine, 2006; Smith-Jackson et al. 2003; S.K.
Kane et al. 2009). These suggestions are all in accordance with the guidelines on how mobile
Dissertation Task 2
0834060
Page 11 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
phones should be designed, provided by the NABP (n d).
Creators are recommended to follow good practices and standards to ensure that their
applications or web pages are accessible to all user groups (Perea et al. 2006). However, this
recommendation is not always followed; not for mobile phones nor for applications or web
sites. A recent study on disabled’s relationship to social media, like Facebook and Twitter,
concludes that these and similar services are designed for visual navigation, forcing those who
are visually impaired to use mobile versions of the media that are better formatted and have
less content (Tollefsen et al. 2011; Rossen, 2011).
Several guidelines have been presented in recent years to show developers how to design
accessible applications and web sites. For instance, the W3C organization has formed such an
initiative, which develops accessibility guidelines (W3C, 2008). These guidelines are in line
with those published by NAPB (n.d.). Furthermore, Fukuda et al. (2005) proposes to
introduce navigability and listenability metrics for designing and developing applications or
web sites, ensuring that screen readers can navigate and present the information in a clear and
consistent way. Similar suggestions were presented by Calabrò et al. (2009) to ensure that ebooks are compatible with screen readers.
With a range of different web browsers, both on computers and mobile phones, compatibility
cannot always be guaranteed. In light of this, The Mobile Web Initiative Device Description
Working Group has proposed the creation of a Device Description Repository; a database
containing information about mobile devices that can be queried by applications to present
data in the most efficient way (K. Smith & Sanders, 2007).
2.5 Assistive technology
Although mobile phones are not designed for use by people with vision loss, there are solutions
that can compensate or improve such use. These are defined by the general term assistive
technology; they include any product, instrument, equipment or technical system designed for or
used by a person with disabilities, which prevents, compensates, supervise, alleviates or
neutralize the effects of the disability (Perea et al. 2006). Products may range from physical and
living objects like the long cane or the guide dog, to software in a device like a screen reader. For
an individual who is blind, it is impossible to read the content on a screen; hence the aid of
assistive technology is a great benefit in their personal and professional life. This section will
look at current solutions and relevant research that addresses the issue of assistive technology
on mobile phones.
2.6 Screen reader
It is possible to operate a mobile phone or computer without being able to see what is on the
screen. Software applications called screen readers can convert text to speech, enabling the
user to read and navigate the content of a screen through hearing. By listening to voice
communication provided by the screen reader application, users are able to perceive and
navigate the content on the screen, making it possible to perform tasks like word processing,
e-mailing, listening to music and surfing the web (Wikipedia, 2010b).
A screen reader is generally made out of two components; the application which monitors the
content on screen, and a synthesizer, which provides the spoken feedback. This is produced
through text-to-speech, where the text input is provided by the screen reader and the synthetic
voice is produced by the synthesizer. The synthesizer works with different languages and
supports phonemes and grammatical rules (AFB, n.d.). For a screen reader to work efficiently,
Dissertation Task 2
0834060
Page 12 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
applications need to follow common standards so that the content can be interpreted and
presented correctly (Babinszki, 2010).
Screen readers are available for both computers and mobile phones, ranging from products
that are free of charge to those that cost closer to $1.000,-. One example of a screen reader for
computers is JAWS, one of the most feature rich products, but also the most expensive
(Freedom Scientific, n.d.). Screen readers can also be run in a web browser, allowing a person
to use almost any computer (Bigham et al. 2008). On mobile phones, screen readers have
been most common for phones with physical buttons, but are becoming available for phones
with touch screens (Babinszki, 2010).
However, a screen reader must not be confused with the voice feedback often built into
modern mobile phones. Although they are capable of representing menu and application
content, these functions are less advanced when it comes to conveying accurate information.
Moreover, they are limited to phone menus; and so unable to access information inside
applications (Theofanos & Redish, 2003).
Mobile Speak is a commercial screen reader designed for mobile phones that run the
Windows Mobile or Symbian OS. It is considered one of the best solutions for mobile phones,
and it supports phones both with physical buttons and with touch screens (Code Factory, n.d.).
TalkBack and Spiel are two open source screen readers designed for the Android OS; both
enable developers to incorporate screen reader functionality into their applications. Although,
not as advanced as commercial versions, they provide developers with an easy and convenient
way making their applications more accessible (C. Chen & Ganov, 2009; Darilek, 2010).
2.7 Reading and input of text
Braille was created to enable blind people to read text. It is not a new language, but a text
system with dots laid out in an organized manner enabling a blind person to read and write
text in the same manner as a sighted person. By moving the finger across the dots, a trained
person is able to understand the letters that the dots represent, and thus able to read the text
just like a sighted person (AFB, n.d.). Reading text from a computer can also be achieved
through Braille, through the use of refreshable Braille displays, Braille printers and Braille
note takers (AFB, n.d.).
Although Braille is a great tool, its reliance on finger sensitivity can exclude the elderly that
may have reduced feeling in the fingertips (AFB, n.d.). For people who have lowered vision,
Braille might not be needed; magnifiers, loupes and special glasses are just some of the
equipment that can assist a person in reading text NABP (n.d.).
However, Braille is not suited for mobile phone use. Instead, users will have to rely on
different means of typing, depending on the phone in use. For a person with vision loss,
mobile phones equipped with physical keyboards are the preferred means of interaction; this
relies on the feedback provided by buttons. In conjunction with a screen reader, operating a
mobile phone is feasible with a keyboard (Babinszki, 2010; Buxton et al. 2008).
Physical keyboards for mobile phones come either with a T9 (text on 9 keys) or a QWERTY
keyboard layout. A T9 layout consists of a phone pad with numbers ranging from 1 to 9 and
three associated letters on each button; while a QWERTY layout represents the same keys as
a keyboard attached to a computer. Just like a computer keyboard, it is possible to memorize
Dissertation Task 2
0834060
Page 13 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
the layout of these buttons and thus write without looking at the keyboard. In addition,
predictive text is often used together with these layouts, enabling the phone to predict what is
being typed, completing the words faster and correcting spelling mistakes (Wikipedia,
2010d).
Mobile phones equipped with touch screens do not always have a physical keyboard; instead
text is entered on a virtual keyboard presented on the screen. This can render their use a
challenge, as the virtual buttons do not provide any tactile feedback (Yfantidis & Evreinov,
2005; Buxton et al. 2008). Several solutions have been presented to improve the typing of text
on touch screens, ranging from physical equipment that work in cooperation with the mobile
phone to software keyboards installed on the phone.
HumanWare (n.d.) has created an overlay for touch screens that encompass the phone screen
and enables the user to interact with the phone and gain access to the most common functions.
The overlay can also communicate with a separate Braille device, making it possible for the
user to read and write using Braille (HumanWare, n.d.). The advantage with this solution is
that the user can carry only one device and interact directly with it; however, the downside is
that it is only compatible with resistive touch screens (Wikipedia, 2010b); conversely, most
modern phones come with capacitive screens that are only capable of interacting with
conductive materials like a human finger (Wikipedia, 2010a).
As mentioned, mobile phones with touch screens come with virtual keyboards. While they are
handy, experience shows that these keyboards can be troublesome when typing. Hence,
several third party software keyboards have been created. A keyboard named ThickButtons
provides a virtual QWERTY layout on the screen; ThickButtons differentiate itself from a
normal keyboard by anticipating the coming letters and making those letters larger and others
smaller (Wells, 2010b). SlideIT and Swype are two other solutions, where the use of a
dictionary enables users to write words by sliding a finger along the letters without removing
it from the screen (Wells, 2010a; Sorrel, 2010a). Yet another option called SwiftKey
anticipates the following word; developers claim that 1/3 of all words will be correctly
anticipated, resulting in up to 50% faster typing (TouchType, 2010).
However, all of these keyboards require some degree of visual navigation, which may be
suitable for people with low vision but not for blind users. A keyboard called BlindType
(Anon, n.d.) might be suitable for blind users, although this was not its original intention.
BlindType is a QWERTY virtual keyboard, which perceives the users’ typing style. Through
an assumption that the user is familiar with the QWERTY layout, the keyboard is able to
recognize where and or what is being typed on screen without the user having to focus on the
screen. Essentially, a word can be typed at any place on the screen without a keyboard
displayed. In theory, this keyboard could also work for blind users, since it does not require
text to be entered in a defined area and it can automatically correct typing errors. Recently,
the company behind the solution was acquired by Google (Noyes, 2010). Google has also
released a technology called Google Scribe, which predicts what the user is planning to type
(Loftås, 2010).
Furthermore, Yfantidis & Evreinov (2005) have designed a gesture based keyboard specifically
for blind users. It works by tapping the screen to make a square appear, which represents eight
directions; where each direction holds a separate letter. By moving the finger towards one of the
directions, the letter is read out loud and proceeding to remove the finger confirms the selection
for typing.
Dissertation Task 2
0834060
Page 14 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
2.8 Haptics
Haptics is a technology that provides tactical feedback, resulting in a more intuitive and less
visually reliant interface. However, haptics can never replace hearing or vision; rather, it
provides an additional sense. For touch-based interfaces, haptics can make a user ―feel‖ and
visualize the shape of an item without looking at the screen, or it can provide feedback when the
finger reaches the border of an element or a button. Haptics is anticipated to become more
advanced in the feature, with an expected ability to provide even more fine-grained details, such
as the fur of an animal (Buxton et al. 2008; Gemperle et al. 2001; Rassmus-Gröhn, 2006).
Yu & Brewster (2003) have developed a solution for presenting graphs and tables to users with
vision loss. Users can explore virtual graphs and tables through a force feedback device that
creates haptic feedback, while audio is used to present detailed and abstract information.
In a study on user reactions to haptics, Rassmus-Gröhn (2006) found that some rely more on the
audio feedback than the haptics feedback. This suggests that, although haptics can be a valuable
additional modality, some users depend more on the senses they are used to. Hence, solutions
that incorporate haptics will likely be greatly improved if they also implement sound.
2.9 Making a better user interface
Mobile phone manufacturers have noticed the inadequacies in usability of the UIs native to
various OS. Most manufacturers develop their own set of UIs for the mobile phones,
replacing the OS’s own UI (HTC, n.d.; Topolsky, 2008). In addition, Nokia, Intel and the
University of Oulu have established a dedicated research center, which focuses on improving
the UI on mobile devices (Darling, 2010).
Raman and Chen (2008) argue that the UI is only a means to an end and should blend
seamlessly into the user’s way of operating the mobile phone. In contradiction to a computer
OS, the mobile OS should provide access to what the user needs and remain unattended when
not in use. According to Karampelas and Akoumianakis (2003), the layout for mobile phones
should include the following, consistent presentations, alternative navigation tools,
accessibility to common options and functions and self-explanatory navigation.
Hence, several solutions have been put forward to improve the navigation of touch screens for
users with vision loss, essentially providing eyes-free navigation.
One of this was presented by Amy K Karlson et al. (2005) in a study on a user-interface
designed for one-hand thumb use. The interface created a 3x3 square-grid; with each square
containing a link to an application or a sub-menu. Selection is done by tapping one of the
squares, while gestures were introduced for zooming and to navigate between menus and.
Results showed that the participants liked the way the navigation and selection of applications
worked, although they were hesitant with the gestures.
Kane et al. (2008) have developed Slide Rule; a UI that solely operates through the use of
gestures and auditory feedback. By using several combinations of gestures, Slide Rule allows
the user to open applications and perform commands. Results revealed that the proposed
solution performed significantly faster than button based menus. However, due to the gesture
commands, more errors were produced.
Dissertation Task 2
0834060
Page 15 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Amar et al. (2003) built a prototype handheld device that used tactile and auditory feedback to
convey a menu structure that provided easy access to common functions. The menu could be
navigated through one hand access, where each finger would perform a specific task. Rotating
a dial would move through various options and menus, a separate button would return to a
previous menu, and four buttons performed navigation and application functions. Most
participants were satisfied with the solution; however, it was noted that users had problems
forming a conceptual model of the hierarchical menu. This was improved by adding the
feature of pressing a button halfway down, which would state the functionality of the selected
button.
With their application, Strumillo et al. (2009) have abandoned the default phone menu on the
Symbian OS and offer a new, simpler menu that provides audible feedback and access to
common functions and features. While navigating through menus, the user is informed of
what is a displayed and possible action to take. The solution has received good feedback;
however, it was developed for an older version of Symbian, making it incompatible with
today’s Symbian phones.
Eyes-free Shell is an open-source project for the Android platform created by Chen and
Raman (2009); it replaces the phone’s existing UI with a new menu system, providing easy
access to applications, as well as information on time and current location. Eyes-free Shell
uses auditory feedback and gestures to navigate between menus. The user can search for
applications by using the same type of technique presented earlier (Yfantidis & Evreinov,
2005). The application is part of a larger open-source initiative, sponsored by Google, which
aims to make touch-based mobile phones more accessible. However, some features require
physical buttons, rendering the proposed solution inaccessible to certain phones. The reliance
on gestures can also be problematic, as indicated from the findings in other projects
mentioned above (Helft, 2009).
2.10 Turning the mobile phone into an assistive aid
Extending on the common functionalities of the mobile phone, several solutions exist today
that turn the phone into an assistive aid. Appendix D presents some of the functions available,
such as object recognition and navigation.
2.11 Framework
The literature review has pointed out several aspects that hinder the effective use of mobile
phones with touch screen for people with vision loss. Although several factors could warrant
further scrutiny, the aspect that stood out as the main obstacle is the operation of the touch
screen itself.
Based on the literature, a framework pointing out the most important factors for the
development of a new UI for touch-based mobile phones are summarized in table 1.
Dissertation Task 2
0834060
Page 16 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Table 1 - Framework for the top issues people with vision loss encounter when using
mobile phones with touch screen
Dissertation Task 2
0834060
Page 17 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
CHAPTER 3: RESEARCH METHOD
Design research was chosen as the research method for the development project in this
Dissertation. This chapter outlines the selected method along with a documentation of the
steps followed throughout the project.
3.1 Design research
Design research aims to provide solutions for human purposes by creating an artifact; the
artifact is tested to provide feedback on improvements (March & Smith, 1995). It is a design
solving process, with several cycles of iterations, where new and improved artifacts are
constantly put forward. Each artifact is evaluated and new artifacts build on the knowledge of
previous ones; thus it is an approach that encourages innovation (Hevner et al. 2006; Grønli &
Bygstad, 2009).
The research field arose as a result of several failed projects; the failures highlighted the
importance of closely studying the design of a product during development (Vaishnavi &
Kuechler, 2008). The same approach is used in engineering, where a product is developed and
tested to further improve the coming versions (Peffers et al. 2006; Vaishnavi & Kuechler,
2007).
Frederick R. Brooks Jr., best known for his book The Mythical Man-Month (Brooks, 1995),
argues that constant incremental iterations should replace the practice of building complete
product versions. Development teams should produce quick and effective prototypes that can
be tested by external users, which provide valuable feedback for further development (Kelly,
2010).
According to Grønli and Bygstad (2009), design research is particularly relevant for
understanding mobile services and innovation. For a project like the current, where the
developers face a previously unfamiliar condition, best guess is not enough (Nielsen, 1993).
In these situations, feedback from the intended target group becomes vital to the project’s
success. Hence, Design research is the process in which it is uncovered what works and what
does not work (Vaishnavi & Kuechler, 2007).
Several models for successful completion of a Design research project have been presented.
One, presented by Grønli and Bygstad (2009), leverages on two widely accepted approaches
to Design research. The method recommends Vaishnavi and Kuechler's (2007) model for the
overall project framework and the model from Hevner et al. (2006) to evaluate the results.
Vaishnavi and Kuechler's (2007) approach is a five step model, designed to guide a project
from startup to the finished solution, as shown in figure 1. The first step is the ―Awareness of
problem‖, which focuses on highlighting or improving the results of an existing problem. This
is followed by the ―Suggestions‖ step, where the problem is further analyzed using existing
knowledge and theory, culminating in a tentative design. ―Development‖ is the next step,
where the project attempts to implement an artifact according to the suggested solution, which
is then ―evaluated‖ in the fourth step. The whole project is completed with a ―conclusion‖
where the project results are evaluated (Grønli & Bygstad, 2009).
Dissertation Task 2
0834060
Page 18 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Development, evaluation and further suggestions are often performed iteratively, allowing the
researcher to step back and evaluate and make changes as necessary. Stepping back achieves
an understanding that could only be gathered from the specific act of construction, the model
refers to this process as ―circumscription‖ (Vaishnavi & Kuechler, 2007).
Figure 1- Design Research process model by Vaishnavi and Kuechler (2007)
Vaishnavi & Kuechler's (2007) model has been criticized for being too dependent on
traditional development methods. The suggestion step is the only stage that allows creative
input and is also the only stage separating the model from the mentioned development
methods. However, it is noted that the steps are only suggestions and not absolute
requirements (Vaishnavi & Kuechler, 2007; Grønli & Bygstad, 2009), thus allowing the
project to make changes as deemed necessary.
Hevner et al. (2006) have developed seven guidelines, presented in table 2, to help provide
better understanding and measurements for effective design research projects. Although quite
general, these guidelines are implemented in the same way as Vaishnavi and Kuechler's
(2007) model, allowing the project freedom to decide on implementation. However, it is
advised to address each of the guidelines during the project’s course (Grønli & Bygstad, 2009;
Hevner et al. 2006).
Dissertation Task 2
0834060
Page 19 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Table 2 - Design Research Guidelines by Hevner et al. (2006)
As mentioned earlier, Vaishnavi and Kuechler's (2007) model were used for the overall
project framework and are described in the following section. Hevner et al.'s (2006) seven
guidelines will be used to evaluate and discuss the results of the project, as described in
chapter 5.
3.2 Awareness of problem
The first stage of Vaishnavi & Kuechler's (2007) model was initiated by a general
assumption, that the majority of today’s mobile phones are touch-based and designed for
those with no visual impairment. The assumption was based on the author’s previous
experience from the mobile industry; former projects had demonstrated that the UI is not
always up to standards and hinder effective use of mobile phones.
Once the general assumptions were in place, these needed to be verified by more thorough
research. The initial literature review focused on the mobile market and recent phone releases,
using resources found mainly through Google and later moving on to the major market
analytics companies. With no prior experience related to vision loss, a literature review on
users with vision loss was needed, not only to identify existing solutions for both daily life
and mobile phone use, but to understand more of the experience if vision loss. Through
resources, such as Google and NABP, literature on the most common problem areas was
collected, along with information regarding manufacturers of assistive technology.
3.3 Suggestion
A more thorough literature review was carried out in the suggestion phase, focusing on all
elements and issues regarding the development of assistive technology for people with vision
loss. The literature review was completed in four iterations, each step contributing with more
information regarding issues facing those with vision loss, how people with vision loss use
mobile phones, application compatibility, operating systems to develop for, screen readers
and haptics, and implementation of such technology. The end result was a framework of
guidelines that worked as a source of reference throughout the project.
The work that came out of the literature review supported the earlier assumptions,
highlighting the need for a UI for touch-based phones, designed specifically for those with
visual impairment. The new design would require operation using touch and sound, menu
elements placed in a logical arrangement, and well-defined categories for assistive
Dissertation Task 2
0834060
Page 20 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
functionalities and standard mobile phone functionality.
It was important for the project to provide new functions and improved access for people with
vision loss. From the literature review, several projects with similar solutions came to the
author’s attention. However, the projects relied mainly on gestures and hardware buttons,
functionalities that could make the solutions harder to learn, and that are certainly
incompatible with mobile phone that are not equipped with buttons. Based on the feedback
from these projects, it became evident that the use of gestures should be kept to a minimum
and that the dependency on hardware buttons should be removed.
3.4 Development
This stage involved the development of the solution in addition to documentation and
planning of the project. The Rational Unified Process (RUP) was chosen as the framework for
the development process due to its emphasis on multiple iterations and its clear and defined
guidelines for developing applications (Gornik, 2004; Pollice, 2002). However, time
constraints necessitated a lightweight implementation of RUP, including only core activities.
Nevertheless, this approach is still in accordance with the framework (Pollice, 2002).
RUP requires all objects to start with an inception, where the project vision is defined and
presented to the stakeholders (Pollice, 2002). Stakeholders for the current project include
representatives NABP, Statped and SmartPhones Telecom; the latter is the company
responsible for providing developer resources. To present the vision and the idea in an
intuitive manner, a virtual prototype was created to show a possible solution for replacing a
touch-based mobile’s GUI. The virtual prototype was created in Microsoft Expression Blend
4 with SketchFlow (Microsoft Corporation, 2009), a tool for creating working prototypes of
applications without writing any code.
Further on, RUP dictates an elaboration on the design and a definition of the baseline,
including functionality requirements and possible applications (Pollice, 2002). The virtual
prototype served as a foundation for the outcome of the project and was used to communicate
the idea and the vision to the developers. During several project meetings, discussions
centered on what would be realistic outcomes from the allocated time. The decision was to
create a working UI prototype for people with vision loss, while ignoring the server side
functionality. Hence, the UI would work and behave as the final product, but all data
presented would be static, not dynamic. An early prototype of the application was developed
at this stage, to test core functionality. Complete logs of the project meetings are available in
Appendix G.
Construction is the third step in RUP; this is where the main development takes place (Pollice,
2002). The application was developed in Java for Android, to support Android version 1.6
onwards. Functionalities for the screen reader and haptics were not developed during this
project. Instead, existing modules were implemented with API integration. During the
construction phase, a total of five iterations of development were completed, with a working
prototype coming from each one. Three iterations were for internal use, while two were tested
externally. With each iteration new virtual prototypes, associated documentation, and added
functionalities evolved. Guidelines and best practices for Android development, defined by
Google, were followed through (Google Inc, 2010b; Google Inc, 2010a). Documentation on
the UIs is available in Appendix H in addition to complete development logs in Appendix I.
Dissertation Task 2
0834060
Page 21 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
3.5 Evaluation
The final phase of RUP is the transition phase, where the developed product is tested on real
users (Pollice, 2002). Each version of the UI was tested in three different scenarios, in a
virtual environment, by the developer on a real device, and by the author, who made sure that
all functionalities were implemented according to specifications. In addition, evaluations of
the prototype were performed through two iterations of user experiments, where external
participants tested and provided feedback on the prototypes.
The participants were recruited with assistance from Statped, a Norwegian agency, which
provides guidance to municipalities for supporting people with learning disabilities and vision
loss (Statped, n.d.). All participants had previous experience from volunteering to other
projects aimed at people with vision loss; moreover, before commencing, they were informed
of their rights and of relevant ethical regulations.
Participants all performed the same steps, starting with a general introduction to the project
with its goals and aims, followed by ten minutes of training and some time to become familiar
with the UI, finally performing a couple of exercises and providing feedback and completing
a survey. Each test was performed on a HTC Hero (HTC, n.d.) device, with an average
duration of one hour. Participants were monitored throughout the test. The introduction to the
project emphasized to the participants that the UI was only a prototype and that the aim was to
improve the navigation on touch-based mobile phones, they could therefor expect limitations
and fewer available options.
During the first iteration, participants were trained in operating the UI. They then had to
choose a language for operating the system, either English or Norwegian. They were informed
that the English version would be more advanced and sound more natural than the Norwegian
version. All menus and feedback would reflect the chosen language.
Table 3summarizes the exercise that the participants were asked to perform. The exercise was
designed to evaluate whether the participants were able to understand and navigate the UI on
their own. Instructions were to perform one task at the time and sufficient time was allowed
for each task.
Table 3 - Tasks the participants were asked to perform
During the exercise, the participants’ behavior, responses, reactions and verbal feedback were
documented. The participants were also providing verbal feedback on functions. Feedback
provided included both comments on current functions and suggestions for improvements.
Dissertation Task 2
0834060
Page 22 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
After the exercise, participants were asked to complete a survey. This collected background
information and presented a set of statements for participants to mark their level of agreement
with. From 1, ―strongly disagree‖ to 5 ―strongly agree‖. Statements were grouped in
categories according to the assessed function of the UI. Table 4 presents a summary of the
most important questions from the survey. The complete survey is available in Appendix L.
Table 4 - Survey completed by participants
Data gathered and analyzed in the first user experiment resulted in a new version where the
major issues and concerns uncovered in the first iteration were improved upon. In the first
iteration, a single tap of the finger would state the function of the selected function, while a
second tap would select the function. Although, this served the purpose, the solution caused
frustration among the participants; they pointed to difficulties with tapping the correct area
and mistakenly opening elements. To overcome these issues, the navigation of the UI was
changed so that a single tap would still state the function of an element, but dragging the
finger to the right would open it.
The second iteration also introduced numbering and made changes to the naming of elements.
One set of numbers reflected the elements; current position in a list, while another set
presented the total number of elements in a list. A new list view, for lists with several
elements, was also introduced. The new list introduced a second row of letters, ranging from
A to Z, on the right side of the screen.
Dissertation Task 2
0834060
Page 23 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
With the introduction of the new functions, the participants were asked to perform the same
exercises and survey once more. Additionally, they were asked to test the new list view and
answer a couple of new questions related to the added functionality, as seen in table 5 and 6.
Table 5 - Additional tasks presented to participants
Table 6 - Additional survey questions
3.6 Conclusion
To conclude the research, the data gathered from the two user iterations were categorized and
further reviewed. Important findings from the surveys and the evaluations were analyzed and
documented for further development of the prototype. The results are also presented in this
report; providing new knowledge to the research field of assistive technology and mobile
phone user access for people with vision loss.
Dissertation Task 2
0834060
Page 24 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
CHAPTER 4: RESEARCH RESULTS
The previous chapter presented the selected research method and the steps taken to produce
the results. This chapter presents and evaluates the research results.
4.1 Results in regards to development
Following the Design research model of Vaishnavi and Kuechler (2007), the current project
has gone through the recommended stages in developing an alternative mobile phone UI. The
new UI provides users with a different way of interacting with the phone, compared to the
mobile phone manufacturers’ original indentation. Through the UI, any function or
application can be utilized in an easier and more efficient way, making the phone more
accessible for people with vision loss. However, it is important to note that the applications
need to be compatible with a screen reader to be useful for people with vision loss.
Interaction with the new UI is made possible through two sensory systems, using sound and
tactile feedback. An organized and intuitive menu system provides the user with access to
relevant information and functionalities. The UI is designed in accordance with Nielsen's
(1993) usability principles, and adapted based on the findings from the framework in the
literature review. It also follows Brook's (1995) recommendation in keeping the number of
available functions to a minimum, avoiding potential confusion.
Figure 2 portrays screenshots from the UI running on a mobile phone; the key words represent
the different menus and functions available. The intended audience is people who are either
blind or that have strongly reduced vision; the text is for the benefit of the latter group. The
key words can also serve as reference points for external users, for instance if customer
support is needed. The font size is formatted according to guidelines from (NABP, n.d.).
Dissertation Task 2
0834060
Page 25 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Figure 2 - Some of the menus available in the UI
As mentioned, the UI is operated through sound and haptics. A single tap on the screen
initiates the UI’s screen reader, which states the function of the selected element, while the
gesture ―tap and drag finger‖ executes the element. The gesture was implemented to simplify
the execution of elements, and to reduce the number of incorrect selections. Moreover,
dragging a finger across the screen commands the UI to read out functions and at the same
time makes the phone vibrate when a new item is available. A back element is placed at the
bottom of every screen, with the exception of the main menu, allowing the user to easily
navigate to the previous menu.
To help the user create a mental map of the different menus and elements, the UI will also
state the level it is currently displaying and give feedback when successfully executing an
element. Furthermore, the UI can be customized to read out the selected element’s position on
a list, for example, number three of five.
Longer lists are displayed in the same way as regular lists, only with an added ribbon on the
screens right side, where an alphabetical list of letters is displayed. Figure 3 shows an
illustration of such a list. The letters refer to the initial letter of available elements, which
could be anything from applications to contacts. Dragging a finger across the ribbon causes
the screen reader to name the letters as the finger crosses them.
Figure 3 - List navigation in the UI
Dissertation Task 2
0834060
Page 26 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
In addition to improved accessibility on touch phones, the UI is intended to work as an
assistive aid that can provide useful information, such as time, date and the weather forecast.
The UI is also designed, to provide navigation and to analyze objects or text using the phone’s
camera; however, the features were not implemented in the current version.
The UI was tailored specifically for people with vision loss and it does not depend on existing
functionality or layout. This approach differs greatly from other solutions that typically rely
on a screen reader and the manufacturer’s UI implementation. By creating a new set of menu
elements, the project did not have to focus so much on compatibility issues and could instead
focus on creating new functionality. At the same time, this allowed freedom to customize the
UI and optimize solutions for the visually impaired.
Design features that were of particular importance in the development of the new UI included,
the reduction of required gestures, a minimal learning curve and no reliance on hardware
buttons. The use of gestures was decided to be reduced since they can be hard to master (Amy
K. Karlson et al. 2005; Shaun K. Kane et al. 2008). In addition, by organizing menu elements
in a vertical layout, the UI operation would be similar to that of the Nokia phones, common
among people with vision loss. Finally, the dependency on hardware buttons was
circumvented, as this could result in compatibility issues with certain phone models.
Figure 4 shows one of several virtual prototypes created. Developing a virtual prototype
turned out to be of great advantage, working as an aid in communicating the vision and as a
tool for developers in finalizing and trying out the product. The virtual prototype resided in a
web browser and was operated with a computer mouse. It behaved like the UI developed for
the mobile phone, with fully operating menus and sound. In addition to the virtual prototype,
figure 5 shows a flow map that was created to visualize the different elements and the
relations between menus.
Figure 4 - Conceptual UI prototype for people with vision loss
Dissertation Task 2
0834060
Page 27 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Figure 5 - Flow map for navigation in the UI
The Android OS was chosen as the developmental platform for the UI, a decision based on
several factors. The Android platform is adopted by several phone manufacturers and is
currently the fastest growing mobile OS in the market (The Nielsen Company, 2010; Gartner,
2010a; Comscore, 2010). Hence, products developed for the Android OS have the potential of
reaching out to a large customer base. The Android OS was also a natural choice for the
developers, since it allows anyone to create a new UI for the phone. Furthermore, it is
considered a very open and flexible OS for application development (Ableson, 2009; Google
Inc, 2010a; Google Inc, 2010b).
Figure 6 presents a conceptual overview of the application, developed in Java for Android,
with support for Android version 1.6 and onwards.
Application
UI - View
Base Activity
Code Behind
Modules
Language packs
English
Norwegian
Etc.
TTS Extended
Haptics
Activity 1
Activity 2
Activity 3
Activity X
OnTouchListener 1
OnTouchListener 2
OnTouchListener 3
OnTouchListener X
Figure 6 - Conceptual model of application
Dissertation Task 2
0834060
Page 28 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Base Activity contains standard functionality and provides communication with the external
modules TTS Extended (Eyes-Free Project, n.d.) and Kickback (Ganov, n.d.); both are
modules used for creating voice feedback (screen reader) and vibration (haptics). All feedback
to the user, menus, voice and haptics are provided through functions called Activities. Each
Activity has an OnTouchlistener, which measures where and how the user is tapping on the
screen. All menu elements reside in XML format, which can easily be translated to different
languages. The current version supports English and Norwegian, but other languages can be
added as appropriate.
4.2 Results in regards to testing
Two iterations of user testing were carried out. A total of four people participated in the first
iteration, three women and one man with an average age of 50 years; a total of five people
took part in the second iteration, the same four with an extra man, making the average age
49.4. As mentioned, statistics from World Health Organization (2009), show that women over
50 make up the largest share of the world’s blind population; thus the project’s sample is
representative of this population. Of the participants, three were blind, one was diagnosed
with very low vision, although her interaction could indicate complete vision loss, the final
participant had low vision and could see objects in very close proximity.
According to Nielsen and Landauer (1993), only a small number of people are required for
usability testing; in fact five people should be sufficient to obtain adequate results (Richtel,
1998). Nielsen (2000) states that such a small number of users will provide better results than
a larger number; largely due to limited project budgets, the advantage of running several
smaller compared to one large test. This notion is in accordance with Design research, which
recommends several iterations of user testing.
The user tests were planned according to usability guidelines from Nielsen (1993), with
usability measured relative to certain users and certain tasks, and where every test should
define a representative and measurable set of tasks relevant to the users. For consistent
measurements, a survey should be completed subsequently. The mean value of the measured
attributes should exceed a specific minimum; on a Likert scale ranging from 1 to 5, the mean
value should be at least 4 (Nielsen & Levy, 1994) and 50% of participants should provide the
score of 5 (Nielsen, 1993). With two iterations of user testing, the ratings from the two
surveys can be compared to evaluate whether the improvements affected usability ratings and
if further improvements are still required (Nielsen, 1993).
Survey questions were categorized to the features they were set to evaluate, these are listed in
Table 7. ―Menu system‖ and ―The solution‖ are considered the two most important categories,
as they measure how well the UI works and the success of the solution. The participants
received the same set of questions in both rounds.
Dissertation Task 2
0834060
Page 29 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Table 7 – Summary of survey categories
Figure 7 presents the results from round one and two, with an overview of the mean scores for
each functionality category. Several questions make up a category, thus the mean scores are
averaged across questions as well as participants.
Comparing components in the UI
Average score
5,0
4,0
3,0
2,0
1,0
Menu
system
Phone
Navigation
Round 1
3,9
4,4
4,1
4,0
4,3
2,3
Round 2
4,5
4,7
4,7
4,7
4,8
4,3
Applications Information The solution
Figure 7 - Graph displaying mean scores from the first and second round of testing
The difference between mean scores from round one and two clearly shows responses were
more positive in round two, where mean were higher than four for all categories. The two
categories of particular interest, ―Menu system‖ and ―The solution‖ both presented fairly poor
feedback in the first round, with initial mean scores as low as 2.3 for ―The solution‖ and 3.9
for ―Menu system‖. According to Nielsen and Levy's (1994) criteria, these low scores would
constitute a project failure. However, round two of testing provided a substantial increase in
positive feedback; thus, it can be concluded that the solution tested in round two is more
efficient and better received among the participants.
Dissertation Task 2
0834060
Page 30 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Figure 8 shows the results from the individual questions for the ―Menu system‖ category. The
mean scores illustrate the changes in the participants reaction between the first and second
iteration.
Average score
Menu system
5,0
4,0
3,0
2,0
1,0
The vibration
The
made it
categorizatio
easier to
n of subchange
menus were
between
logical
menus
The menu
system was
easy to use
The system
made the
touch phone
easier to use
The spoken
options were
easy to
understand
It was easy to
navigate
between
menus and
sub-menus
Round 1
4,0
3,7
4,3
2,5
4,3
4,5
Round 2
4,6
4,6
4,6
4,6
3,6
4,8
Figure 8 - Graph displaying a comparison between results from first and second round
of testing on the menu system
The results show an increase in scores for all but one question, indicating that the second
menu system received a better acceptance than the first version. The reduction in scores for
the questions relating to the vibration function was clarified through verbal feedback from
participants. In the first round of testing, a greater reliance on haptic feedback was required to
navigation; however, in the second round of testing, the improvements facilitated the auditory
feedback and participants chose to rely more on sound than touch. These results are consistent
with findings from Rassmus-Gröhn (2006), who found that people tend to rely more on the
sense they are accustomed to.
Dissertation Task 2
0834060
Page 31 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Figure 9 presents results from the individual questions for the solution category. The mean
scores portray participants acceptance of the solution for rounds one and two.
Average score
Acceptance of the solution
5,0
4,0
3,0
2,0
1,0
I personally felt that the
menu system enabled and
improved my use of the
mobile phone
I prefer this solution above
others*1
I would use this solution in
my daily life*2
Round 1
2,3
2,5
2,3
Round 2
4,6
4,0
4,3
*1 Three participants did not respond due to no prior experience with solutions for touch screens
*2 One participant did not respond due to no prior experience with touch screens to compare against
Figure 9 - Graph displaying a comparison between results from first and second round
of testing on the complete solution
The results show an increase in mean scores for all questions, indicating that the whole
solution received a better acceptance in the second round of testing. It should be noted that
some participants decided not to answer the second and third question, feeling that they
lacked the experience to give an informed response. However, all participants responded to
the most important question, ―I personally felt that the menu system enabled and improved
my use of the mobile phone‖, with a great increase in positive feedback.
While the Design Research method does not require statistical analyses, these were
nevertheless carried out to shed more light on the changes in scoring that were evident
between the two versions of the UI. Effect sizes and differences between means were
evaluated across the categories previously outlined. Due to the small sample size, a certain
measure of leniency with respect to level of significance was judged necessary; this was
therefore set to 0.1. Thus mean scores, available in figure 7, were found to be significantly
higher for the second round of testing, compared to the first round, for the navigation
functions (t(3) = 2.45, p>0.1), for the information functions (t(3) = 2.45, p>0.1), and for the
solution functions (t(3) = 5.44, p>0.05). Effect sizes were judged to be high for all three
functions (r = 0.41; r = 0.40; r = 0.89; respectively). Effect sizes were similarly high for the
menu functions (r = 0.37) and the application functions (r = 0.41), but the differences between
means were non-significant (t(3) = 1.47, ns; t(3) = 1.48, ns; respectively). The remainder of
the analyses is included in Appendix M.M.
Dissertation Task 2
0834060
Page 32 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Nielsen (1993) suggests that participants should be asked for their subjective opinions, to
better provide an understanding of their satisfaction. Participants were asked to state their
thoughts and suggestions to improvements, following each round this feedback was used to
improve the application further. Feedback from round one is available in Appendix M.A,
while a complete list of feedback from round two is available in Appendix M.F. The most
informative comments from round two are summarized in Table 8.
Table 8 - Table showing subjective feedback from round two
The positive feedback from participants shows how much they appreciated the second
iteration of the solution; this is consistent with the survey results. The negative feedback
mainly focuses on the new functionality introduced in the second iteration, indicating that the
issues encountered in the first iteration had been solved and that a third iteration should aim at
solving the new problems. Comments pointing to the inadequacy of the vibration result from
the over-all improvements to the solution causing participants to shift their attention to the
voice, where the participants paid more attention. Participants’ suggestions for improvements
are reasonable and well thought through and should certainly be considered in a third
iteration.
Dissertation Task 2
0834060
Page 33 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
CHAPTER 5: DISCUSSION
This chapter presents a critical discussion, comparing the findings from the literature review
with the results from the evaluation of the UI, as shown in the previous chapter. To evaluate
the collected result, the seven step model from Hevner et al. (2006) will guide the discussion
and evaluation of the outcome of the project. While the model recommends that a project
evaluation follows these steps, it also emphasizes that each project should make its own
judgment regarding the implementation.
5.1 Design as an Artifact
The first guideline in (Hevner et al.'s (2006) model is to create an artifact; this might involve
all models and applications developed throughout a project´s life cycle. Several artifacts were
created in this project; start with the virtual prototype. The virtual prototype served as a way
of communicating the vision to the stakeholders and developers and offered the advantage of
being able to easily create a working application to try out. The virtual prototype was updated
for each new version of the UI, to reflect and communicate changes. The importance of
developing a virtual prototype was clear from the beginning of the project, as experience
showed it to be an efficient means for clarifying ideas to stakeholders and developers.
In addition to the virtual prototype, other important artifacts include the documentation, the
manual, and the conceptual model of the UI. However, the most significant artifact was the UI
for touch-based mobile phones. A total of five versions were developed, three for internal
testing and two for external evaluation. As presented in the research results chapter, the UI
received positive feedback from the participants.
The development of the UI followed findings from the literature review, with a framework
that pointed out several factors for improvement and experience from previous solutions to
learn from.The decision to design the UI for the Android OS, was based on reports from The
Nielsen Company (2010) and Gartner (2010a), which indicated that the Android OS is the
fastest growing mobile OS. Key considerations for the new solution included minimal use of
gestures (Amy K. Karlson et al. 2005; Shaun K Kane et al. n.d.), replacement of the native UI,
providing independence from phone manufacturers (Amy K. Karlson et al. 2005; Amar et al.
2003; Strumillo et al. 2009; C. Chen & Raman, 2009), and no reliance on physical keys,
making the solution compatible to all Android based mobile phones.
Unlike the other implementations, the menu system was inspired by the layout of Nokia based
mobile phones with vertical navigation, in an attempt to smooth the transition for participants
currently using Nokia phones. Moreover, to improve navigation, a feature was implemented
to allow users to find available elements by tapping anywhere on the screen (Amar et al.
2003).
A potential weakness for the proposed solution is the fact that it only works as a UI. Although
the literature review indicated several factors that could improve the experience for people
with vision loss, the current prototype only provides a means for easy access to touch-based
mobile phones. However, the solution cannot be applied to text-writing or web-browsing.
Thus, the solution is just scratching the surface of assistive aid solutions. Furthermore,
applications launched by the UI will need to be coded correctly to work for people with vision
loss. The fact that the current solution replaces the phone’s factory UI, might make it
uninteresting for certain users, some may prefer to preserve the original UI and rather use a
dedicated screen reader.
Dissertation Task 2
0834060
Page 34 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
5.2 Problem relevance
The second guideline involves the development of a solution that solves a business problem.
After a thorough review of the mobile phone industry and currently available solutions for
people with vision loss, findings confirmed that touch-based mobile phones are not designed
for this group. With the majority of newly developed phones support touch capability
(Gartner, 2010b), a clear business opportunity has presented itself.
Solutions to make touch phones accessible are first and foremost screen readers and dedicated
UIs. However, as pointed out in the literature review, screen readers alone will not provide the
necessary support (Babinszki, 2010). Commercial screen readers are incompatible with both
the Android and the iPhone platform (Code Factory, n.d.). As mentioned, earlier solutions
exist only on a research level, with the exception of the open source initiative Eyes-Free Shell
(C. Chen & Raman, 2009) still; this solution has its limitations.
With regulations set in motion, manufacturers will soon be forced to create mobile phones
that are accessible for everyone (Wall, 2003; Steria, 2009). Thus the continued development
of the UI might prove to have commercial value.
5.3 Design evaluation
With the third guideline, artifacts should be evaluated using appropriate methodology and
relevant conclusions drawn from the findings. As previously mentioned, both internal and
external testing was conducted in order to measure the effectiveness of the artifacts.
Internal testing was performed over the course of three iterations, where each new version
was tested in an emulator, on a running device, and by the project team. Bugs and errors were
entered into a source tracking tool, which monitored all changes made to the code, as well as
added functionality introduced by the ever increasing literature review.
However, internal testing could not provide sufficient feedback on its own. Hence, two UI
versions were made for external users; the first was not considered adequate, but participants
indicated satisfaction with the second version. Both verbal feedback and survey results
suggested that participants would use such a solution. Yet, some negative feedback and
suggestions for improvements were recorded. Given that the UI is a prototype still under
development, this feedback will be used to further improve the solution and expand the
feature sets in coming iterations.
With only four participants in the first iteration, in contrast to the five recommended by
Nielsen and Landauer (1993), the number may have been too low to achieve significant
results. However, in order to follow the strict schedule set for the project, their feedback was
considered sufficient. Based on the feedback from round two of testing, where the participants
deemed the solution a success, the decision seems justified.
With the introduction of a fifth participant, not only did the project meet the recommended
number of participants, but the positive responses offered by the late-comer corresponded to
that of the first four. This would rule out the possibility that participants gave higher scores
because they had grown accustomed to the solution.
Another potential criticism is the use of older participants. However, the sample was
representative of the potential user group; according to WHO (2009), the majority of people
Dissertation Task 2
0834060
Page 35 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
with vision loss are at the age of 50 or older. Still, future versions of the UI should include a
younger sample to collect feedback from all potential users.
It was mentioned in the literature review that the screen size should be of adequate size (Plos
& Buisine, 2006; Smith-Jackson et al. 2003); however, actual size was not pointed out. The
phone used for testing (HTC, n.d.) had a screen size of 2,8‖, which should be sufficient for
most users, especially with larger font sizes. However, it would be interesting to investigate
whether a smaller or larger screen size would change the outcome of the study.
5.4 Research contributions
The literature review uncovered missing options for people with vision loss, in regards to the
use of mobile phones. Thus, the outcome of this project should be highly relevant in this area
of research. Based on existing knowledge, a new solution was developed to aid this user
group and the findings were evaluated based on subjective feedback. All results have been
documented, ensuring that future projects can leverage on current findings.
5.5 Research rigor
Comprehensive methodology is required both during and after the construction of artifacts to
verify results, a process ensured through the use of RUP. This framework was chosen based
on its guidelines and procedures that emphasize the importance of producing several iterations
of an artifact (Gornik, 2004), consistent with the practices from Design research (Vaishnavi &
Kuechler, 2007).
Careful consideration went into planning and designing the UI, with guidance from wellknown usability experts like Nielsen (1993) and Brooks (1995), along with a thorough
literature review.
5.6 Design as a Search progress
Desired results should be achieved through appropriate methods. Design research was applied
to the current project, following the model from Vaishnavi and Kuechler (2007). This model
puts emphasis on the process of defining a problem and searching for existing solutions;
furthermore, it recommends a continued search for literature as the artifacts are developed
through multiple iterations. The search for literature went through several sources, ranging
from academic papers and online news articles on the web to general resources regarding
vision loss.
The work of literature grew as the iterations progressed, ensuring an ever-expanding resource
to build future versions on. The search also uncovered new topics, revealing how touch-based
phones may also be used as assistive aids.
In addition to the literature review, the results from the user evaluations provided the
background for further improvements; this resulted in the second version of the UI for user
testing.
5.7 Communication of research
The last guideline emphasizes the importance of presenting the outcome in an efficient
manner, both to a technical and a management oriented audience. Hence, this dissertation is
written in a clear and consistent language, it explains technical terms for a management
audience, and provides useful information for a technical audience. Great care and attention to
detail has been put into documenting the results, as well as documenting and demonstrating
the UI, as shown with the virtual prototype. In addition, the report is submitted as part of a
Dissertation Task 2
0834060
Page 36 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Master’s degree, making it available through the university’s system.
5.8 Summary of discussion
The literature review concluded that today’s phones are not intended for people with vision loss,
due to their use of touch screens that require visual navigation. On button-operated phones, the
simplified menus allow screen readers to be enabled as alternative means of operation. However,
a touch screen operates with a more complicated menu and correct voice representation become
very challenging.
By leveraging on the methodology from Design research, an alternative UI was developed to
replace the phone’s own menu system, enabling the operation of touch-based phones for people
with vision loss. The development process started with a virtual prototype, which demonstrated
the finished product. A total of five iterations of development followed, where two were tested
on external participants.
Of the two versions tested, the first was considered a failure while the second was deemed a
success; users even commented that they would use the product if it was made commercially
available. The experience from the testing sessions emphasize the importance of receiving
external feedback, indicating that Design research is an efficient method for developing new
solutions.
Dissertation Task 2
0834060
Page 37 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
CHAPTER 6: CRITICAL EVALUATION OF RESEARCH
The chapter provides a critical evaluation of the aims, objectives and results presented in the
dissertation. These are presented in the overview in Table 9.
Table 9 - Overview on aims and objectives
The dissertation report was designed like a project, with two successful outcomes, the
dissertation with associated research, and the external development of the UI. In order to
complete the project in the limited time available, parallel processes were defined for each
project, including milestones and tasks. Due to the involvement of external resources, a
separate project was defined for their purpose; this tracked the progress of the development.
Project meetings, progress reports and a bug tracking system ensured that all parties involved
were kept up to date.
The aim of the project was to find a solution that enables people with vision loss to operate
mobile phones with touch screens, and create a new UI that simplifies such phones and make
them accessible for this group. This was accomplished through the development of five
versions, each an improvement on the previous.
Objective 1
The first objective was to perform a literature review. However, with no prior encounter with
people with vision loss, or any knowledge regarding assistive aids, a comprehensive literature
research was needed to better understand the needs of the visually impaired.
Throughout the research process, several areas were investigated, ranging from social aspects
to actual products; the resulting literature review covers the areas of most importance. The
author believes he has learnt a lot about life without vision, not only from reading articles, but
from talking to actual people with vision loss.
An investigation of the mobile industry was not grated high priority due to the author’s prior
experience from the telecom industry. For the past 11 years he has worked in a company on
the forefront in providing Norwegian companies with new technology.
Although the literature review is comprehensive, several of the sources are from online
articles. Most academic papers were not up to date in regards to mobile technology. This
aspect is important when determining the market’s current options and the rapid succession of
new phone models, but makes it impossible for academic journals to stay updated. In regards
Dissertation Task 2
0834060
Page 38 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
to assistive aid, several papers presented developed solutions, but usually referred to older
technology.
Objective 2
A framework was designed based on the literature findings, creating the basis for the
development of the UI. Originally, the intention was to create a solution that covered a much
larger area, not only for accessibility, but also as an assistive aid. Hence, the literature review
covers a broader area than the framework, which is designed according to the aim of the
project.
Objective 3
Five participants took part in the evaluation of the UI, which ran over two iterations. Based on
the feedback, the second version received a tremendous increase in positive feedback
compared to the first; the final version was therefore considered a success. Evaluation was
based on a survey, an informal interview, and on observation; this ensured a large set of data
to base the conclusions on.
Only four people were able to participate in the first version, while five participated in the
second. However, due to the time restrictions this was considered sufficient. Based on the
feedback from the second version, the decision seemed justified as the first round resulted in
an improved solution. It also ruled out the possibility of users voting in favor of the system, as
the new participant provided the same positive feedback as the rest. Future iterations should
also include a younger participant group, to obtain feedback from all potential users.
Objective 4
The last objective was to present a discussion on results, drawing on the literature and
assessing the UI and research results. The seven-step model from Hevner et al. (2006) a guide
specifically designed for design research projects was implemented, ensuring that relevant
aspects of the project were highlighted.
Dissertation Task 2
0834060
Page 39 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
CHAPTER 7: CONCLUSION
The final chapter concludes with a summary of the previous discussions, followed by an
overview of contributions to the existing research field, along with future research
suggestions.
7.1 Summary of the dissertation
This dissertation has investigated the issue of the inaccessibility of today’s modern mobile
phones for people with vision loss. Through an extensive literature review, an in-depth overview
of issues and rights facing people with vision loss has been presented. Furthermore, an
evaluation of the current mobile market and available solutions and technology followed. It was
found that neither the society, nor the manufacturers of products and services, is designing for
people with vision loss. Hence, this user group is denied the benefits these products offer.
The literature review pointed out that most modern mobile phones require visual navigation, to
operate the touch-based screens. Although mobile phones are accessible through the use of
applications called screen readers, those currently on the market are inefficient and difficult to
use with touch screens.
Hence, this project set out to find a new solution, aiming to make touch-based mobile phones
accessible for people with vision loss. With Design research used as methodology for the overall
project, a UI was created. It was designed to replace the phone’s own UI and to provide an easy
and intuitive way of operating a mobile phone. Design research also emphases the importance of
developing a solution over several iterations, and involving external participants for product
evaluation. By using voice and haptic feedback, and a menu system similar to most Nokia
phones, the proposed UI was evaluated to be an effective solution that most of the participants
would use if it became commercially available.
The ideas presented in this dissertation are not unique. Previous research projects have proposed
other solutions, ranging from gesture based navigation or mapping the phone keys to perform
other tasks, to creating a new UI for easier operation of the phone. However, what is unique for
the current proposal is the combination of other ideas put into a new and user-friendly UI. Thus
taking the best from previous research and presenting a solution that focuses on providing a
menu layout which is both easy and intuitive to operate, in addition to providing access to all
relevant applications and functions on the mobile phone.
In summary, the dissertation has covered the following topics:
Issues people with vision loss encounter on a daily basis.
An overview of the mobile market, what is available, the most popular mobile OS’s, and
a look at touch-based navigation.
Presentations of assistive aids and technologies available for people with vision loss,
such as; screen readers, input of text, haptics, compatibility issues, and how to provide a
better UI.
Creation of a framework, used for designing a new UI.
Design research as a methodology for developing applications, with demonstration of the
effectiveness of the method.
The processes involved in developing the UI, resulting in five iterations, each with a new
version.
Dissertation Task 2
0834060
Page 40 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Android OS was used as the development platform, currently the fastest growing mobile
OS on the market.
The UI was designed to be both intuitive and easy to use, with focus on keeping gestures
to a minimum and with a menu users can relate to.
No reliance on physical keys ensures that the UI is compatible with all mobile phones
running the Android OS.
Research findings from two of the iterations, evaluated by external participants. The first
iteration was considered a failure, while the second was considered a success, receiving
only positive scores and feedback.
Discussion covering the different aspects of the research findings.
In conclusion, the dissertation proposed a new UI for touch-based phones, providing an
easy and intuitive way of operating such phones.
7.2 Future research and development
Although the presented UI received only positive feedback and was judged a success, it is only a
prototype and by no means a finished product. The research results show that there are several
aspects which can be further investigated and improved.
Future development should take into consideration the comments and feedback reported during
the last iteration and should also include a younger user base, as this group will provide a broader
set of feedback. Moreover, attention should be given to technical users, since they might find the
current solution too simple. Added functionality should also be investigated, looking at
efficient means for writing text or surfing the web. To make further use of the potential of the
mobile phone, assistive aids, such as navigation from A to B and analysis of objects, could
provide great benefits for this user group.
Future research should look into how the mobile phone can be implemented for assistive living,
or leverage on augmented reality and GPS positions, to better present intelligible content and
information based on current location. Other uses for the UI would also be interesting to
explore; for instance, easier and safer operation of mobile phones while driving a car.
Dissertation Task 2
0834060
Page 41 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
REFERENCES
Abascal, J. & Civit, A., 2001. Universal access to mobile telephony as a way to enhance the
autonomy of elderly people. Workshop on Universal Accessibility of Ubiquitous
Computing Proceedings of the 2001 EC/NSF workshop on Universal accessibility of
ubiquitous computing: providing for the elderly, pp.93-99.
Ableson, F., 2009. Introduction to Android development. IBM. Available at:
http://www.ibm.com/developerworks/opensource/library/os-android-devel/ [Accessed
January 23, 2011].
AFB, a. American Foundation for the Blind - Home Page. Available at: http://afb.org/
[Accessed October 24, 2010].
AFB, b. Reading and Writing. American Foundation For The Blind. Available at:
http://afb.org/Section.asp?SectionID=40&TopicID=200 [Accessed August 15, 2010].
AFB, c. Speech Systems. American Foundation for the Blind. Available at:
http://www.afb.org/Section.asp?SectionID=4&TopicID=31&DocumentID=1284
[Accessed August 16, 2010].
AFB, d. Web-Braille from National Library Service. American Foundation for the Blind.
Available at:
http://afb.org/Section.asp?SectionID=40&TopicID=200&DocumentID=1695 [Accessed
August 15, 2010].
Amar, R. et al., 2003. Mobile ADVICE: an accessible device for visually impaired capability
enhancement. In CHIʼ03 extended abstracts on Human factors in computing systems.
ACM, p. 919.
American Printing House for the Blind, 2010. Hall of Fame: Father Thomas Carroll. Hall of
Fame Leaders and legends of the blindness field. Available at:
http://www.aph.org/hall_fame/bios/carroll.html [Accessed August 14, 2010].
Anon, BlindType - Touch typing the way it should be. Available at: http://blindtype.com/
[Accessed September 24, 2010].
Babinszki, T., 2010. How Do Blind People Use Mobile Phones. Even Grounds. Available at:
http://www.evengrounds.com/blog/how-do-blind-people-use-mobile-phones [Accessed
September 19, 2010].
Berge, A.R., 2007. Fra skole og studier til jobb eller uføretrygd?, Rehab-Nor.
Bigham, J.P., Prince, C.M. & Ladner, Richard E, 2008. WebAnywhere : Enabling a Screen
Reading Interface for the Web on Any Computer WebAnywhere System. In Proceedings
of the 2008 international cross-disciplinary workshop on Web accessibility (W4A) - W4A
’08. pp. 1159-1160.
Bojo AS, knfbReader. Available at: http://bojo.no/650001 [Accessed January 4, 2011].
Dissertation Task 2
0834060
Page 42 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Brooks, F.P., 1995. The Mythical Man-Month: Essays on Software Engineering Anniversar.,
Addison-Wesley Professional.
Brush, A. et al., others, 2010. User experiences with activity-based navigation on mobile
devices. In Proceedings of the 12th international conference on Human computer
interaction with mobile devices and services. ACM, p. 73–82.
Buxton, B. et al., 2008. Big data: the next Google. Interview by Duncan Graham-Rowe.
Nature, 455(7209), pp.8-9.
Calabrò, A., Contini, E. & Leporini, B., 2009. Book4All: A Tool to Make an e-Book More
Accessible to Students with Vision/Visual-Impairments. HCI and Usability for eInclusion, p.236–248.
Chen, C. & Ganov, S., 2009. TalkBack: An Open Source Screenreader For Android.
Available at: http://google-opensource.blogspot.com/2009/10/talkback-open-sourcescreenreader-for.html [Accessed January 4, 2011].
Chen, C. & Raman, T.V., 2009. Announcing Eyes-Free Shell For Android. Available at:
http://google-opensource.blogspot.com/2009/04/announcing-eyes-free-shell-forandroid.html [Accessed January 5, 2011].
Clark, A., 2007. Apple reaps reward for runaway success of iPhone. The Guardian. Available
at: http://www.guardian.co.uk/technology/2007/oct/23/apple.iphone/print [Accessed May
6, 2010].
Code Factory, Introducing Mobile Speak. Available at:
http://www.codefactory.es/en/products.asp?id=316 [Accessed August 27, 2010].
Colenbrander, A., 2002. Visual standards. Aspects and Ranges of Vison loss with Emphasis
on Population Surveys, Sydney.
Comscore, 2010. comScore Reports May 2010 U.S. Mobile Subscriber Market Share.
Available at: http://www.prnewswire.com/news-releases/comscore-reports-may-2010us-mobile-subscriber-market-share-98031904.html [Accessed August 7, 2010].
Coughlan, J. & Manduchi, R., 2009. Functional Assessment of a Camera Phone-Based
Wayfinding System Operated By Blind and Visually Impaired Users. International
journal of artificial intelligence tools : architectures, languages, algorithms, 18(3),
pp.379-397.
Darilek, N., 2010. Spiel: Features. Available at: http://spielproject.info/wiki?name=features
[Accessed January 4, 2011].
Darling, P., 2010. Intel and Nokia Create First Joint Laboratory. Available at:
http://newsroom.intel.com/community/intel_newsroom/blog/2010/08/23/intel-and-nokiacreate-first-joint-laboratory [Accessed January 4, 2011].
ECON, 2003. Funksjonshemmede og arbeid. En kartlegging av situasjonen for synshemmede,
hørselshemmede og rullestolbrukere, Econ Pöyry AS.
Dissertation Task 2
0834060
Page 43 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Eriksen, E., 2010. Windows phone 7: lek eller alvor? amobil.no. Available at:
http://www.amobil.no/artikler/windows_phone_7_lek_eller_alvor/78155 [Accessed
September 6, 2010].
Eyes-Free Project, Text-To-Speech Extended. Available at:
http://www.androlib.com/android.application.com-google-tts-iDB.aspx [Accessed
November 22, 2010].
Freedom Scientific, JAWS for Windows Screen Reading Software. Available at:
http://www.freedomscientific.com/products/fs/jaws-product-page.asp [Accessed January
6, 2011].
Fukuda, K. et al., 2005. Proposing new metrics to evaluate web usability for the blind. CHI
’05 extended abstracts on Human factors in computing systems - CHI ’05, pp.13871390.
Ganov, S., Kickback. Available at: http://www.androlib.com/android.application.com-googleandroid-marvin-kickback-FExn.aspx [Accessed November 22, 2010].
Gartner, 2010a. Gartner Says Android to Become No. 2 Worldwide Mobile Operating System
in 2010 and Challenge Symbian for No. 1 Position by 2014. Available at:
http://www.gartner.com/it/page.jsp?id=1434613 [Accessed January 5, 2011].
Gartner, 2010b. Gartner Says Worldwide Mobile Phone Sales Grew 17 Per Cent in First
Quarter 2010. Available at: http://www.gartner.com/it/page.jsp?id=1372013 [Accessed
August 10, 2010].
Gemperle, F., Ota, N. & Siewiorek, D., 2001. Design of a wearable tactile display.
Proceedings Fifth International Symposium on Wearable Computers, pp.5-12.
Gomnæs, S., 2005. Bruker ikke funksjonene. amobil.no. Available at:
http://www.amobil.no/artikler/bruker_ikke_funksjonene/16353 [Accessed September 5,
2010].
Google, Google Goggles for Android. Available at:
http://www.google.com/mobile/goggles/#text [Accessed August 29, 2010].
Google Inc, 2010a. Android User Interface Guidelines. Available at:
http://developer.android.com/guide/practices/ui_guidelines/index.html [Accessed August
29, 2010].
Google Inc, 2010b. The Developerʼs Guide | Android Developers. Available at:
http://developer.android.com/guide/index.html [Accessed November 21, 2010].
Gornik, D., 2004. IBM Rational Unified Process: Best practices for software development
teams. Rational Software White Paper TP026B, Rev.
Grossman, L., 2007. Invention Of the Year: The iPhone - The Best Inventions Of 2007. Time.
Available at:
Dissertation Task 2
0834060
Page 44 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
http://www.time.com/time/specials/2007/article/0,28804,1677329_1678542_1677891,00
.html [Accessed May 6, 2010].
Grønli, T.-M. & Bygstad, B., 2009. Innovation in Mobile Services - a Design Research
Approach. In S. Love, ed. Handbook of Mobile technology Research Methods. New
York: Nova Science Publishers, p. 176.
Helft, M., 2009. For the Blind, Technology Does What a Guide Dog Can’t. The New York
Times. Available at: http://www.nytimes.com/2009/01/04/business/04blind.html
[Accessed January 5, 2011].
Helland, R., 2003. Øyetelefon for blinde. NRK. Available at:
http://www.nrk.no/helse_forbruk_og_livsstil/1.1313559 [Accessed February 16, 2010].
Hevner, A.R. et al., 2006. Design science in information systems research.
Wirtschaftsinformatik, 11(4), pp.342-135.
Holzer, A. & Ondrus, J., 2010. Mobile application market: A developer’s perspective.
Telematics and Informatics, (2010), pp.1-10.
HTC, a. HTC Hero. Available at: http://www.htc.com/uk/product/hero/overview.html
[Accessed January 9, 2011].
HTC, b. HTC Sense. Available at:
http://www.htc.com/europe/press.aspx?id=127750&lang=1033 [Accessed August 16,
2010].
HumanWare, a. BrailleNote. Available at: http://www.humanware.com/eneurope/products/blindness/braillenotes [Accessed September 19, 2010].
HumanWare, b. Maestro handheld accessible computer. Available at:
http://www.humanware.com/eneurope/products/blindness/handheld_computers/_details/id_28/maestro.html [Accessed
September 19, 2010].
IDC, 2010. Worldwide Converged Mobile Device (Smartphone) Market Griws 56.7% Year
Over Year in First Quarter of 2010, Says IDC. Available at:
http://www.idc.com/getdoc.jsp?containerId=prUS22333410 [Accessed May 11, 2010].
International Agency for the Prevention of Blindness, 2010. International agency for the
prevention of blindness., London.
Joseph, C., 2009. Challenges of Being Blind. eHow. Available at:
http://www.ehow.com/about_5185162_challenges-being-blind.html [Accessed August
14, 2010].
Kane, S.K. et al., 2009. Freedom to roam: a study of mobile device adoption and accessibility
for people with visual and motor disabilities. In Proceeding of the eleventh international
ACM SIGACCESS conference on Computers and accessibility. ACM, p. 115–122.
Dissertation Task 2
0834060
Page 45 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Kane, Shaun K et al., Freedom to Roam : Mobile Device Opportunities and Challenges for
People with Visual and Motor Impairments. Challenges.
Kane, Shaun K., Bigham, J.P. & Wobbrock, Jacob O., 2008. Slide rule. Proceedings of the
10th international ACM SIGACCESS conference on Computers and accessibility - Assets
’08, p.73.
Karampelas, P. & Akoumianakis, D., C, 2003. User interface design for PDAs: Lessons and
experience with the WARD-IN-HAND prototype. , Practice, and Experience, pp.474485.
Karlson, Amy K., Bederson, B.B. & SanGiovanni, J., 2005. AppLens and launchTile.
Proceedings of the SIGCHI conference on Human factors in computing systems - CHI
’05, p.201.
Kelly, K., 2010. The Master Planner. Wired Magazine, iPad edition, 8(18).
Kharif, O., 2010. Qualcomm, AT&T Move in on ―M-Health.‖ Bloomberg Businessweek.
Available at:
http://www.businessweek.com/technology/content/aug2010/tc20100823_511801.htm?lin
k_position=link1 [Accessed August 27, 2010].
Loftås, B.E., 2010. Google Scribe. Dinside.no. Available at:
http://m.dinside.no/php/art.php?id=853173 [Accessed January 4, 2011].
LookTel, What is LookTel? Available at: http://www.looktel.com/ [Accessed August 29,
2010].
Maines, S., 2008. White Cane Walk makes visible the daily challenges of blindness. The
Lawrence Journal-World. Available at:
http://www2.ljworld.com/news/2008/oct/19/white_cane_walk_makes_visible_daily_chal
lenges_bli/ [Accessed August 14, 2010].
Malinowski, E., 2010. For blind soccer stars, field of vision is overrated. Wired. Available at:
http://www.wired.com/playbook/2010/08/blind-soccer/ [Accessed August 27, 2010].
March, S.T. & Smith, G., 1995. Design and natural science research on information
technology. Decision Support Systems, 15, pp.251-266.
Meijer, P.B.L., The vOICe for Android - Augmented Reality for the Blind. Available at:
http://www.seeingwithsound.com/android.htm [Accessed August 29, 2010].
Meyers, M., 2008. Target settles with blind patrons over site accessibility. CNET News.
Available at: http://news.cnet.com/8301-1023_3-10028109-93.html [Accessed January 5,
2011].
Microsoft Corportation, 2009. Expression Blend 4.
Dissertation Task 2
0834060
Page 46 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Mlauf, 2010. Serotek Corporation Announces the Release of DocuScan Plus. SeroTalk.
Available at: http://www.serotalk.com/2010/11/24/serotek-corporation-announces-therelease-of-docuscan-plus/ [Accessed January 4, 2011].
NABP, a. English info — Forside. Available at:
https://www.blindeforbundet.no/internett/english-info [Accessed October 24, 2010].
NABP, b. Hjelpemidler. Available at:
https://www.blindeforbundet.no/internett/tilrettelegging-i-samfunnet/hjelpemidler
[Accessed August 15, 2010].
NABP, c. Tilgjengelige websider for synshemmede. Available at:
https://www.blindeforbundet.no/internett/tilgjengelighet/internett-for-brukere [Accessed
January 4, 2011].
Neset, T., 2010. Mobil har gått forbi PC. ITavisen. Available at:
http://www.itavisen.no/852360/mobil-har-gaatt-forbi-pc [Accessed October 24, 2010].
Nielsen, J., 1993. Usability engineering 1st ed., Morgan Kaufmann.
Nielsen, J., 2000. Usability Testing with 5 Users (Jakob Nielsenʼs Alertbox). Jakob Nielsenʼs
Website. Available at: http://www.useit.com/alertbox/20000319.html [Accessed
December 16, 2010].
Nielsen, J. & Landauer, T.K., 1993. A mathematical model of the finding of usability
problems. In Proceedings of the INTERACT93 and CHI93 conference on Human factors
in computing systems. ACM, pp. 206-213.
Nielsen, J. & Levy, J., 1994. Measuring usability: preference vs. performance.
Communications of the ACM, 37(4), pp.66-75.
Noyes, K., 2010. Googleʼs Blind Type Buy Will Benefit Android Users. PCWorld. Available
at:
http://www.pcworld.com/businesscenter/article/206892/googles_blind_type_buy_will_b
enefit_android_users.html [Accessed January 4, 2011].
Nusca, A., 2010. Smartphone vs. feature phone arms race heats up; which did you buy?
Available at: http://www.zdnet.com/blog/gadgetreviews/smartphone-vs-feature-phonearms-race-heats-up-which-did-you-buy/6836 [Accessed August 8, 2010].
Peffers, K. et al., 2006. The design science research process: A model for producing and
presenting information systems research. In Proceedings of the First International
Conference on Design Science Research in Information Systems and Technology
(DESRIST 2006). p. 83–106.
Perea, G., Usero, M. & Angel, J., 2006. Strategies for tailoring web contents for specific
devices: the case of usable and accessible contents for assistive technologies of web
mobile devices. Annals of Physics, 54(July), pp.1-5.
Dissertation Task 2
0834060
Page 47 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Picard, K., 2010. Minibanker med touch screen. Dinside.no. Available at:
http://www.dinside.no/851363/minibanker-med-touch-screen [Accessed January 4,
2011].
Plos, O. & Buisine, S., 2006. Universal design for mobile phones: a case study. CHI 2006,
pp.1229-1234.
Pollice, G., 2002. Using the Rational Unified Process for Small Projects: Expanding Upon
eXtreme Programming. Rational Software White Paper.
Raman, T.V. & Chen, C.L., 2008. Eyes-Free User Interfaces. Computer, 41(10), pp.100-101.
Rassmus-Gröhn, K., 2006. Enabling Audio-Haptics. Licentiate Thesis,Certec, Department of
Design Sciences, pp.1-126.
Redmine, Redmine. Available at: http://www.redmine.org/ [Accessed November 19, 2010].
Richtel, M., 1998. Making Web Sites More ―Usable‖ Is Former Sun Engineerʼs Goal. The
New York Times. Available at:
http://www.nytimes.com/library/tech/98/07/cyber/articles/13usability.html [Accessed
December 16, 2010].
Rossen, E., 2011. Blinde tyr til tjenesters mobile utgaver. Digi.no. Available at:
http://www.digi.no/859569/blinde-tyr-til-tjenesters-�mobile�-utgaver [Accessed
January 5, 2011].
Scott, R.A., 1995. The Making of Blind Men. In Deviance: A Symbolic Interactionist
Approach. Boston: General Hall, pp. 236-241.
Sendero Group LLC, Sendero Group Home Page, GPS for the Blind. Available at:
http://www.senderogroup.com/ [Accessed January 4, 2011].
Smith, K. & Sanders, D., 2007. Device Description Repository Requirements 1.0. W3C.
Available at: http://www.w3.org/TR/2007/NOTE-DDR-requirements-20071217/#secrequirements [Accessed August 27, 2010].
Smith-Jackson, T., Nussbaum, M. & Mooney, A., 2003. Accessible cell phone design:
development and application of a needs analysis framework. Disability and
rehabilitation, 25(10), pp.549-60.
Sorrel, C., 2010a. Swype: Text Input From the Inventor of T9. Wired.com. Available at:
http://www.wired.com/gadgetlab/2008/09/swype-text-inpu/ [Accessed January 4, 2011].
Sorrel, C., 2010b. Word Lens: Augmented Reality App Translates Street Signs Instantly.
Wired.com. Available at: http://www.wired.com/gadgetlab/2010/12/word-lensaugmented-reality-app-translates-street-signs-instantly/ [Accessed January 4, 2011].
Statped, statped.no - Om Statped. Available at:
http://statped.no/moduler/templates/Module_Overview.aspx?id=13539&epslanguage=N
O [Accessed January 3, 2011].
Dissertation Task 2
0834060
Page 48 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Steria, 2009. Slik lykkes du med universell utforming. Available at:
http://www.steria.no/2007/05/3-minutters-guide-slik-lykkes-du-med-universellutforming [Accessed September 15, 2010].
Strumillo, P., Skulimowski, P. & Polanczyk, M., 2009. Programming Symbian Smartphones
for the Blind and Visually Impaired. In Computers in Medical Activity. Berlin: SpringerVerlag Berlin and Heidelberg GmbH & Co. KG, pp. 129-136.
The Independent, 2010. Augmented Reality smartphone application helps visually impaired,
elderly to see. The Independent. Available at: http://www.independent.co.uk/lifestyle/health-and-families/augmented-reality-smartphone-application-helps-visuallyimpaired-elderly-to-see-1928269.html [Accessed August 29, 2010].
The National Federation of the Blind of Connecticut, The Courtesy Rules of Blindness.
Available at: http://www.nfbct.org/html/courtesy.htm [Accessed August 14, 2010].
The Nielsen Company, 2010. Android Soars, but iPhone Still Most Desired as Smartphones
Grab 25% of U.S. Mobile Market. Available at:
http://blog.nielsen.com/nielsenwire/online_mobile/android-soars-but-iphone-still-mostdesired-as-smartphones-grab-25-of-u-s-mobile-market/ [Accessed August 7, 2010].
Theofanos, M. & Redish, J., 2003. Bridging the gap: between accessibility and usability.
interactions, pp.36-51.
Tjan, B.S. et al., 2005. Digital Sign System for Indoor Wayfinding for the Visually Impaired.
2005 IEEE Computer Society Conference on Computer Vision and Pattern Recognition
(CVPRʼ05) - Workshops, pp.30-30.
Tollefsen, M. et al., 2011. På nett! Et notat om funksjonshemmede og bruk av sosiale medier,
Topolsky, J., 2008. Samsungʼs new TouchWiz UI gets previewed on video. Engadget.
Available at: http://www.engadget.com/2008/02/15/samsungs-new-touchwiz-ui-getspreviewed-on-video [Accessed August 16, 2010].
TouchType, 2010. SwiftKey - Revolutionary text prediction for Android smartphones.
Available at: http://www.swiftkey.net/ [Accessed September 24, 2010].
Vaishnavi, V. & Kuechler, W., 2007. Design Science Research Methods and Patterns:
Innovating Information and Communication Technology New Editio., Taylor & Francis,
Inc.
Vaishnavi, V. & Kuechler, W., 2008. The emergence of design research in information
systems in North America. Journal of Design Research, 7(1), p.1–16.
Virki, T., 2010. Nokia to use Linux for flagship N-series phones. Reuters. Available at:
http://www.reuters.com/article/idUSLDE65N14720100624 [Accessed September 5,
2010].
Dissertation Task 2
0834060
Page 49 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Vision 2020, 2009. How Does VISION 2020 Work? Available at:
http://www.vision2020.org/main.cfm?type=HOWDOESVIS2020WORK [Accessed
October 23, 2010].
Vogelstein, F., 2008. The untold story: How the iPhone blew up the wireless industry. Wired
Magazine, (16.02). Available at: http://www.wired.com/gadgets/wireless/magazine/1602/ff_iphone [Accessed May 14, 2010].
W3C, 2008. Web Content Accessibility Guidelines (WCAG) Overview. Available at:
http://www.w3.org/WAI/intro/wcag.php [Accessed January 4, 2011].
Wall, S.J., 2003. Supporting Vision 2020 : The right to sight. Community Eye Health, 16(45),
pp.1-2.
Wells, A., 2010a. SlideIT Keyboard. Android Tapp. Available at:
http://www.androidtapp.com/slideit-keyboard/ [Accessed September 19, 2010].
Wells, A., 2010b. ThickButtons Keyboard. Android Tapp. Available at:
http://www.androidtapp.com/thickbuttons-keyboard/ [Accessed September 19, 2010].
West, J. & Mace, M., 2010. Browsing as the killer app: Explaining the rapid success of
Appleʼs iPhone. Telecommunications Policy, 34(5-6), pp.270-286.
Wikipedia, 2010a. Capacitive sensing. Wikipedia. Available at:
http://en.wikipedia.org/wiki/Capacitive_sensing.
Wikipedia, 2010b. Feature phone. Wikipedia. Available at:
http://en.wikipedia.org/wiki/Feature_phone [Accessed August 7, 2010].
Wikipedia, 2010c. Resistive touchscreen. Wikipedia. Available at:
http://en.wikipedia.org/wiki/Resistive_touchscreen [Accessed September 19, 2010].
Wikipedia, 2010d. Screen reader. Wikipedia. Available at:
http://en.wikipedia.org/wiki/Screen_reader [Accessed May 7, 2010].
Wikipedia, 2010e. Smartphone. Wikipedia. Available at:
http://en.wikipedia.org/wiki/Smartphone [Accessed August 7, 2010].
Wikipedia, 2010f. T9 (predictive text). Wikipedia. Available at:
http://en.wikipedia.org/wiki/T9_(predictive_text) [Accessed September 18, 2010].
World Blind union, Main page UMC/WBU. Available at:
http://www.worldblindunion.org/en/home.html [Accessed October 24, 2010].
World Health Organization, 2009. Visual impairment and blindness. Available at:
http://www.who.int/mediacentre/factsheets/fs282/en/index.html [Accessed October 23,
2010].
Yfantidis, G. & Evreinov, G., 2005. Adaptive blind interaction technique for touchscreens.
Universal Access in the Information Society, 4(4), pp.328-337.
Dissertation Task 2
0834060
Page 50 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Yu, W. & Brewster, S., 2003. Evaluation of multimodal graphs for blind people. Universal
Access in the Information Society, 2(2), pp.105-124.
Dissertation Task 2
0834060
Page 51 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
APPENDIX A: ETHICAL APPROVAL
Dissertation Task 2
0834060
Page 52 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
APPENDIX B: ABOUT THE AUTHOR
The author of this dissertation has been working in the telecom industry since 1999; initially
as a sales associate of mobile phones, followed by employment within one of Norway’s
largest distributor of mobiles from 2004. Onwards he played a key role in launching the first
Windows Mobile based phones in Norway. Subsequently, he started working in a subsidiary
of the distributor company, focusing on providing mobile solutions for businesses. The
solutions ranged from providing wireless e-mail access on mobile phones, before it became a
standard. Later, mobile device management solutions were directed at ensuring
implementation of correct security measures, as well as providing remote management of
applications and support on mobile phones. Lately, the author has been working on providing
new applications and solutions to companies. For instance a solution for automatic
configuration of mobile phones, which ensures that the phone is set up with a company image
and a solution to replace the mobile phone´s own Graphical User Interface with a simpler one,
thus providing access only to the applications and services that the user needs.
Dissertation Task 2
0834060
Page 53 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
APPENDIX C: THE MOBILE MARKET
The mobile phone market enjoys increased popularity, with market shares expanding every
day (IDC, 2010); it is now considered larger than the PC market (Neset, 2010). The mobile
market consists mainly of two types of mobile phones; feature phones and smartphones.
Where feature phones are considered low-end phones, with limited features and computer
power (Nusca, 2010; Wikipedia, 2010b), smartphones offer more advanced computing power
and operating systems, as well as greater connectivity; they are essentially small mobile
computers (Wikipedia, 2010e).
During the first quarter of 2010, a total of 314.7 million mobile phones were sold to end users
worldwide, with smartphones making up 54.3 million of the sales (Gartner, 2010b); this is an
increase of 17% compared to the same period in 2009. Although, feature phones are still
considered the platform with the largest sales volume, smartphones have had a positive
increase and sales are expected to increase further in the coming years (IDC, 2010).
Looking at the US alone, patterns are the same. Of the 234 million mobile phones that were in
use between March and May 2010, 49.1 million were smartphones (Comscore, 2010). Similar
numbers have been found by The Nielsen Company (2010), who report that smartphones now
hold 25% of the market, an increase from 23% in 2009. Recent trends suggest that
smartphones will surpass feature phones in 2011.
According to Gartner (2010) the top five OS for smartphones are; Symbian (44,3%),
Blackberry (19.4%), Apple iOS (15.4%), Google Android (9.6%) and Windows Phone
(6.8%). In the US, the chart is slightly different; Blackberry (35%), Apple iOS (28%),
Windows Phone (15%), Google Android (13%) and Palm OS (3%) (Comscore, 2010);
moreover, Apple iOS and Google Android are currently the fastest growing (The Nielsen
Company, 2010). Gartner estimates that the Android OS will be the second largest OS
worldwide in 2010 and it will challenge Symbian’s top ranking position in 2014 (Gartner,
2010a). The numbers show that smartphones sales are increasing, suggesting that the market
wants more advanced phones, with more functionality and better connectivity.
To meet the increased demand for smartphones, Nokia has announced that they will
discontinue the Symbian OS on their popular N-series phones and instead focus on a new
system called Meego (Virki, 2010). Microsoft, on the other hand has already released their
new Windows Phone 7 OS, which will replace the outdated Windows Phone range (Eriksen,
2010).
Appendix C.A - The new players
New actors like Apple and Google have in many ways changed the mobile market, enabling
people to use and operate mobile phones in a different way. With the introduction of the
iPhone, consumers no longer need multiple devices. Instead of using separate devices for
making phone calls, sending e-mails and listening to music, the iPhone introduced one device
for all functionalities, which can be further expanded through downloadable applications
(Vogelstein, 2008).
The possibility to download new applications, and thereby extend the phone’s capabilities and
functionalities, is probably the largest contributor to the iPhone’s success. Not only does it
enable the user to personalize the phone, but it also changes the mobile market; where the
handset manufacturer is in control and not the mobile operator (Holzer & Ondrus, 2010; West
& Mace, 2010). Other manufacturers have followed the same path and Google experiences a
Dissertation Task 2
0834060
Page 54 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
similar success; in fact, the Android platform is currently outselling the iPhone in the US
(Comscore, 2010; The Nielsen Company, 2010). The mobile application market will most
likely continue to increase the demand for smartphones, thus ensuring market growth.
Although it was by no means a pioneer, the iPhone also changed the market by replacing
buttons with a touch screen. Furthermore its sleek design and easy access landed it the Times
Magazine’s award ―Innovation of the year‖ in 2007 (Clark, 2007; Grossman, 2007). What
separates the iPhone’s touch screen from others was its implementation, which made users
prefer it above regular keyboard navigation. Today, most smartphones have a touch screen.
APPENDIX D: USING THE MOBILE PHONE FOR ASSITIVE AID
Products and services directed at assisting users with visual impairments are no longer restricted
to government organizations and non-profit communities. Several companies are moving into the
mobile care market with profit in mind; developing applications and wireless devices that
provide health-related services. In the US, sales are expected to expand to $600 million in 2010
and $1.3 billion in 2011. Qualcomm, AT&T, IBM and Best Buy are just a few of the companies
that are planning to release new services in the area. While most of the applications are intended
for the regular consumers who desire health and fitness applications, more specialized solutions
are also in progress. One such solution is designed to streamline information accessibility for
hospitals and doctors, and make it easier to monitor patients regardless of their location (Kharif,
2010).
Appendix D.A - Object recognition
Defining what is in front of one is not always an easy task for someone with vision loss;
hence, by pointing a mobile phones camera on an object, the application will analyze and present
the result to the user through text or voice (The Independent, 2010).
DocuScan and knfbReader are applications using the mobile phones camera to scan and
convert printed text into digital text, for then to have it read out through the use of a screen
reader (Mlauf, 2010; Bojo AS, n.d.). Two other applications are Look Tel (LookTel, n.d.) and
Google Goggles (Google n.d.) that analyzes objects and presents the result in text or voice.
World Lens is an application using the phones inbuilt camera to instantly translate text from
one language to another. The result is displayed on the mobile screen, in the same place as the
original text. Although, intended for a sighted person, the technology demonstrates how the
camera can be used as an aid in communicating information to the user, even when it is in
foreign language (Sorrel, 2010b)
Appendix D.B - Navigation
In a controlled environment, a blind person can familiarize himself with the surroundings,
being able to navigate around without any help. However, this picture is quite different when
moving to an uncontrolled area, like the grocery store or the shopping mall. The guide dog
and the long are cane is indispensable, but these aids cannot tell your exact location or how to
navigate from A to B in new surroundings. Special GPS units for people with vision loss can
aid in this matter (HumanWare, n.d.; Sendero Group LLC, n.d.), but they do not work in
indoor environments.
Tjan et al (2005) has presented a digital sign system, where a handheld camera can detect
Dissertation Task 2
0834060
Page 55 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
special retro-reflective tags, informing the user of their current location. Coughlan and
Manduchi (2009) have presented a similar solution, but instead of a separate camera, a mobile
phone with an inbuilt camera was used to read colored signs.
Brush et al. (2010) created an activity-based application, allowing a user to travel to a location
by essentially following breadcrumbs being displayed on the mobile phone. What
differentiates this solution from other GPS based solutions is that it is not relying on accurate
position, but instead uses the phones activity to remember where it has been. Examples are
changes in the phones accelerometer or lost connection with the Bluetooth in the car stereo.
Another example is a project aiming at enabling blind people to travel alone, and perform the
same tasks as a sighted person. When roaming in known vicinity; a blind person will normally
use a guide dog for assistance, but when encountered with unfamiliar surroundings the
reliance of a real person is often needed. The project aims at developing a mobile solution,
where the user carries a camera that wirelessly transmits information to a help center, where
an operator can instruct the user and provide guidance (Helland, 2003).
Augmented reality can also be used for aiding blind people. A project called ―The voice for
Android‖, developed for mobile phones running Android OS, provides an augmented reality
experience without relying on vision. Sound and voice is used to guide the user around in the
surrounding environment, by leveraging on the phones inbuilt camera. The application can
analyze photo snapshots and provide feedback trough sound, on distance and height of objects,
much like the way sonars operate. In addition, the user can also be informed of compass
direction and colors (Meijer, n.d.).
Dissertation Task 2
0834060
Page 56 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
APPENDIX E: INTERVIEW WITH TOR ULLAND AT HUSEBY (STATPED)
Tor Ulland is as senior advisor at Huseby Resource Centre for the blind, a division of Statped,
were he has been working since 1994. He provides training and guidance to people with
vision loss, with a special focus on assistive aids for computer related equipment, cell phones,
GPS and Daisy audio book players.
What kind of training is provided to people who are blind?
That is a good question. If you are born blind, you get regular school education and learn how
to perform daily activities; such as making food. In addition, you learn Braille, use of
computer aids and the white cane.
For adults experiencing vision loss, there are rehabilitation courses which they can undertake;
both from The Norwegian Association of the Blind and partially sighted and Huseby
(Statped). In addition, The Norwegian Association of the Blind and partially sighted have
several courses called "Adaptation Courses"; guiding an individual through the new life as a
blind. The courses consist of an introductory course followed by three courses; each lasting
fourteen days. Huseby offer is of a more personal character, where each course is tailored for
the participant. It starts with two to three days of a surveying, followed by several courses
lasting one to two weeks each; depending on the specific needs of the participant. Most last
for six weeks, thought in some cases it can last for several years.
It is also possible to receive some extra training if you are using assistive aids; normally from
The Norwegian Labour and Welfare Administration, but may also be from the municipality.
The offer varies from municipality to municipality, depending on available funds and
expertise.
Is it tougher to train someone who has lost sight during adult life?
An individual who experiences vision loss at adulthood will never be any good in Braille.
However, people who are born blind may have greater difficulty understanding concepts such
as space and direction, compared to people who have seen and know these concepts. This is
an oversimplification, but it explains some of the issues which might be a problem.
What kinds of assistive aids are available for people with vision loss?
There are several aids available. On computers, aids can consisting of; synthetic speech,
refreshable Braille displays to read the content of a PC screen, and scanner programs for
optical scanning of text (OCR).
In addition, you also have regular aids like the white cane or the guide dog. But you also have
applications like; watches with Braille marking, clocks that talk, color indicators and speaking
weights.
The Norwegian Association of the Blind and Partially Sighted have a subsidiary called
Adaptor; providing a variety of variety of tools to aid centers and are also available from
www.hjelpemiddelkatalogen.no.
Are there any particular challenges you see in the use of electronic products? Such as
mobile phones, radio, TV, touch screens, ATMs, etc. And would you say that such items
are accessible to those who are visually impaired?
No, they are not good enough. Radio and TVs have become more and more of a problem.
Dissertation Task 2
0834060
Page 57 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
With so many menus where you can define settings, it is impossible to keep track of every
option or setting. In the old days there were buttons, but now everything must be done
through a menu system displayed on the screen. If you would like to set up a channel, it is
often necessary to open a specific menu; which is impossible when cannot see the screen and
receive appropriate feedback
On my home stereo, I could set up 20 radio channels on the remote control. To find out which
channel I was setting up, I would listen a little too each station and program the remote
accordingly. I would then remember the order of each channel, on the remote.
However, I remember one time when I was spending hours setting this up. By accident I
pressed the wrong button and everything got deleted. I had to start all over again. In
retrospective, this is just one of many examples of how bad products are designed for the
blind.
It is even worse on products which remember the last menu you exited. As opposed to always
start in a set place, it is impossible to know where you are in a menu which constantly
changes, since you cannot write it down and memorize what and where to press.
How would you say it is to use public services?
I would say that it is not easy, since many of these systems not available for the partially
sighted. Systems such as Flexus, machines to buy train tickets from, most ATMs and several
other systems are not designed for this user group. The same applies for public transportation
system information; knowing which metro line or bus is coming next.
Would you recon that manufacturers do not include people who are visually impaired
when designing products?
That is correct. They do not think about this group until afterwards and then it is often too
late. It has been said that it would be much cheaper to let all the blind travels in Oslo travel for
free, than instead of changing the system to be compatible.
You have already mentioned that one can learn the order of things, when operating
electronic products, but does this apply to types of equipment, like the oven or stove at
home?
You have to know which button is for function. With older stoves this was easy, but with
newer is increasingly more difficult as most have menu to operate. For instance, my old
washing machine has a button that regulates the temperature. Standing in a right position
equals to 30 degrees, down 60 degrees and to the left is 90 degrees. For 40 degrees I can then
calculate my way around. This is impossible with modern machines.
Do you have any thoughts regarding how the society organizes itself to include people
with vision loss?
Most places or services are not accessible, but I hope that things will get better with the new
anti-discrimination law here in Norway. It came in 2009; require manufacturer to design their
products to be accessible for all user groups. Right now I think that it will take a while before
we will see a change, unless larger markets implement the same rules.
However, USA has adopted new rules, stating that mobile phones should more accessible. If
these rules are extended to the rest of the market, I think that manufacturers will start to
design their products accordingly.
Dissertation Task 2
0834060
Page 58 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Could you name some of the organizations in Norway offering support and assistance to
people who are visually impaired?
Certainly, here is a small sample; The Norwegian Association of the Blind and Partially
Sighted, Association Interest Group for the Visually Impaired Computer users, visually
impaired Scholars Association (intended for people with higher education), Christian work
among the blind and visually impaired (provides books and text), Norwegian sound and Blind
Library (Produces books in Braille and voice, making both fiction and science to higher
education, Statped (Huseby) and Tamatun (work in relation to schools and training).
Dissertation Task 2
0834060
Page 59 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
APPENDIX F: PROJECT PLAN
Dissertation Task 2
0834060
Page 60 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
APPENDIX G: PROJECT MEETING REPORTS
The following appendix contains meeting reports documenting the project meetings held during
the project. The meeting reports consist of initial meetings, before the development process
started and reports documenting each of the iteration versions.
Appendix G.A - Initial project workshop meeting, June 14, 2010
Attendants:
Magne Gabrielsen
Alexander Dreyer Johnsen
Agenda:
Produce an initial list of functionality which the application will support. The list will
at a later meeting be presented to the developers for feedback regarding functionality
and what will be possible to implement in the prototype.
Application requirements:
Platform
o Due to easy access, broad support of mobile phones and easy development, the
solution should be developed for the Android mobile operating system
The User interface (UI)
o The application needs to be built around an easy and light weighted user interface.
All options needs to be concise and provide the same means of performing actions
and navigating through the menus.
o The menus should be in contrast colors, black and orange/brown. All text should be
in a large and bold font, to make reading easier.
Feedback
o Correct orientation
Use the mobile phone’s inbuilt gyro to inform the user if the phone is facing
upwards (correct way), or downwards (wrong way).
o Physical feedback
Use the vibration engine in the phone, to provide feedback when the user
changes/moves the finger between menus. Also called haptics.
o Sound
Sound /voices to be played when user selects an option
Sounds/voices to be played when information are provided to the user
It should not be possible for the user to set the volume below a default “low
level” value. This to prevent the user from turning off sound and not being
able to turn it on again.
Will use Google Voice or another sound library to create computerized voice
messages
o Notifications
Dissertation Task 2
0834060
Page 61 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
The phones own notification messages will have to be suppressed, as they
are designed for visual notification. The system will have to provide its own
set of notifications. Ex. Vibrate three times when running low on battery.
Setup
o When the application launches for the first time, it will prompt the user if it is
intended for a user who is blind or have lowered vision.
o Settings will be set in XML files.
o It is possible to provision new settings through the use of a mobile device
management (MDM) system. An MDM system can provision a new XML file to the
phone, which will automatically change settings without the user getting involved.
o The system should be extended to a web-portal were an administrator easily can
send out new settings
Functionality
o Navigation
Navigation from A to B
Leverage on functionality from Google Maps
Information on current location
o Analyze
The phone’s camera can be used to automatically recognize objects in front
of the camera, for then to provide feedback to the user.
o Remote assistance
It should be possible for the user to request assistance. Through an option in
the menu, the user can select to receive assistance.
The phone will make a connection to a support desk application, were an
operator can accept the request. Once accepted, the operator will be able to
see through the phone’s internal camera and locate the user by the
assistance of the phone’s internal GPS unit.
o Phone calls
It should be possible to perform phone calls
The prototype will only provide a list of pre-set phone numbers which the
user can call.
The defined numbers can be changed in the XML file.
Dissertation Task 2
0834060
Page 62 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix G.B - Approval of functionality, June 25, 2010
Attendants:
Magne Gabrielsen
Alexander Dreyer Johnsen
Espen Snilsberg Richardsen
Kim Ruben Teigen
Agenda:
Present the application, it uses and the proposed list of functionalities for the
prototype. The developers will provide feedback and the meeting will conclude with a
confirmed set of functionality to be implemented.
Application requirements:
Platform
o It was decided that the Android OS was the platform to develop the solution on.
The User interface (UI)
o A visual prototype was presented to the developers, which showed the proposed
idea for how the menu and navigation should look. It was decided that the first
version should be similar to the visual prototype.
o The menus should be in contrast colors, black and orange/brown. All text should be
in a large and bold font, to make reading easier.
o If the setup is designed to be used by blind users, the mobile phones backlight will be
turned off to consume battery.
o It was decided to use the full power of the Android OS, which enables a developer to
create their own UI without having to rely on the one shipped with the OS. The
project will therefor create an entirely new UI, to minimize the risk of messages or
feedback not suited for navigation from a blind or lowered vision user.
Feedback
o Correct orientation
The developers thought it would be possible to use the mobile phones inbuilt gyro to tell whether the phone is facing upwards (correct way), or
downwards (wrong way). However, this might be phone model dependent,
as not every phone comes with a gyro or can tell if which direction it is being
held.
o Physical feedback
It was decided to use the vibration engine in the phone to provide feedback
when the user changes/moves the finger between menus.
o Sound
To create computerized voice messages, a library called TTS Service
Extended will be used. It provides an API which enables developers to create
text messages, which the library plays as a computerized voice. Some
showcases were presented in the meeting, and it was decided that the
output should be satisfactory. However, there might be a problem with the
Dissertation Task 2
0834060
Page 63 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
o
library only supporting English for the moment. For a production system, this
will limit the number of potential users, but for the prototype it was deemed
satisfactory.
Sound /voices will be played when user selects an option
Sounds/voices will be played when information are provided to the user
The user will not be able to set the volume below a default “low level” value.
This to prevent the user from turning off sound and not being able to turn it
on again.
Notifications
The phones own notification messages will be suppressed to best extend.
Creating a new UI will also help on this, since the project will not have to rely
on the same information generated.
The system will provide its own set of notifications. Ex. Vibrate three times
when running low on battery.
Setup
o When the application launches for the first time, it will prompt the user if it is
intended for a user who is blind or have lowered vision.
o Settings will be set in XML files.
o It is possible to provision new settings through the use of a mobile device
management (MDM) system. An MDM system can provision a new XML file to the
phone, which will automatically change settings without the user getting involved.
o The system should be extended to a web-portal were an administrator easily can
send out new settings. This functionality will be developed, but the UI will be created
for test purposes and not production.
Functionality
o Navigation
Google Maps will be used for Navigation.
A pre-defined list of destinations will be entered in the system, which the
user can choose from. Google maps will then generate a route from current
location to the selected destination.
TTS Service Extended will be used to read out the list to the user.
Information on current location will be available
o Remote assistance
It will be possible for the user to request assistance. Through an option in the
menu, the user can select to receive assistance.
For the prototype, the phone will make a connection to a web service and
automatically start sending pictures/video from the phone’s internal camera
and location provided from the internal GPS unit.
o Analyze
It was intended to use Google Goggles for analyzing object. Google Goggles
can automatically recognize text and numbers and should therefore be
sufficient for this purpose. However, the current version of Google Goggles
does not provide an API; hence it cannot be implemented in another
Dissertation Task 2
0834060
Page 64 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
o
application. Because of this limitation, the UI will only link to the Google
Goggles application.
Phone calls
The prototype will provide a list of 5 pre-set phone numbers which the user
can call.
The defined numbers can be changed in the XML file.
Dissertation Task 2
0834060
Page 65 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix G.C - Layout of UI, August 30, 2010
1. Information
a. Time
i. Say: The current time is ”CURRENT TIME”
b. Date
i. Say: Today’s date is
c. Today’s weather
i. Say: The weather at your current location in Oslo is 23 degrees and sunny.
d. Back
2. Phone
a. Contact book
i. Alexander: +47 977 65 888
ii. Home:
iii. Work:
iv. Opplysningen: 1881
v. Back
b. Keypad
i. Is this possible?
ii. Back
c. Back
3. Navigation
a. Current location
i. Say: Your current location is….
b. Compass
i. Display compass
ii. Back
c. Navigate to
i. Home
1. Say: This is just a simulation. Please go back
ii. Work
1. Say: This is just a simulation. Please go back
iii. Grocery store
1. Say: This is just a simulation. Please go back
iv. Bank
1. Say: This is just a simulation. Please go back
v. Back
d. Back
4. Analyze
a. Launch Google Goggles
5. Applications
a. Web browser
b. Facebook
c. Mail
d. Text messages
Dissertation Task 2
0834060
Page 66 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
e. Back
Dissertation Task 2
0834060
Page 67 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix G.D - Layout of UI, September 13, 2010
The application should inform the user of successful opening of a sub-menu, in addition of
informing the user when returning to the main menu.
The menu will also have to be translated to Norwegian, as the participants testing the UI are
from Norway.
1. Information
Say: Opening Information menu
a. Time
i. Say: The current time is ”CURRENT TIME”
b. Date
i. Say: Today’s date is ”CURRENT DATE”
c. Today’s weather
i. Say: The weather at your current location in Oslo is 23 degrees and sunny.
d. Back
2. Phone
Say: Opening Phone menu
a. Contact book
i. Home:
1. Say: Calling Home. HOLD. This is a test of the user interface. Calling
Home will not be provided in this test. Please choose another option.
ii. Work:
1. Say: Calling Work. HOLD. This is a test of the user interface. Calling
Work will not be provided in this test. Please choose another option.
iii. Alexander: +47 977 65 888
1. Say: Calling Alexander
2. Perform call
iv. Taxi
1. Say: Calling Taxi. HOLD. This is a test of the user interface. Calling
Taxi will not be provided in this test. Please choose another option.
v. Back
b. Keypad
i. This is a test of the user interface. Entering numbers will not be provided in
this test. Please choose another option.
ii. Back
c. Back
3. Navigation
Say: Opening Navigation menu
a. Current location
i. Say: Your current location is….
b. Compass
i. Display compass
ii. Back
c. Navigate to
i. Home
Dissertation Task 2
0834060
Page 68 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
ii.
iii.
iv.
1. Say: Navigating to Home. HOLD. This is a test of the user interface.
Navigation will not be provided in this test. Please choose another
option.
Work
1. Navigating to Work. HOLD. This is a test of the user interface.
Navigation will not be provided in this test. Please choose another
option.
Grocery store
1. Navigating to Grocery store. HOLD. This is a test of the user
interface. Navigation will not be provided in this test. Please choose
another option.
Bank
1. Navigating to Bank. HOLD. This is a test of the user interface.
Navigation will not be provided in this test. Please choose another
option.
Back
v.
d. Back
4. Analyze
Say: Opening Analyze menu
a. Launch Google Goggles
b. Back
5. Applications
Say: Opening applications menu
a. Web browser
i. Say: Opening Web browser. HOLD. This is a test of the user interface. The
application will not be opened in this test. Please choose another option.
b. Facebook
i. Say: Opening Facebook. HOLD. This is a test of the user interface. The
application will not be opened in this test. Please choose another option.
c. Mail
i. Say: Opening Mail. HOLD. This is a test of the user interface. The application
will not be opened in this test. Please choose another option.
d. Text messages
i. Say: Opening Text messages. HOLD. This is a test of the user interface. The
application will not be opened in this test. Please choose another option.
e. Back
Dissertation Task 2
0834060
Page 69 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix G.E - Layout of UI, October 10, 2010
The application should inform the user of successful opening of a sub-menu, in addition of
informing the user when returning to the main menu. A problem was discovered in the first
round of testing, where text being read out is canceled if another selection is made. A solution
to this issue is to have the system prioritize menu and sub-menu messages, allowing them to
finish playing before stating elements. Individual elements should still be canceled by other
elements selected.
The operation of elements should to be changed to improve navigation of the UI. Instead of
first tapping once to have an option read out and then tap one more time to select it, a gesture
should to be introduced to improve the selection of elements.
With the introduction of a gesture; menu options are still read out with a single tap, while
opening elements are performed trough holding the finger on the option and slide right to
open. This should make it easier to select elements, as well as improve on incorrectly opening
wrong elements since the finger never leaves the screen.
Second round of testing should also implement list navigation in Contact book, Applications
and Navigate to. Please referrer to visual design for implementation. The UI should pre-load
all applications and contacts, and only display navigation letters matching applications and
contacts. Ex. B should only be displayed if an application begins with B.
1. Information
Say: Opening Information menu
a. Time
i. Say: The current time is ”CURRENT TIME”
b. Date
i. Say: Today’s date is ”CURRENT DATE”
c. Today’s weather
i. Say: The weather at your current location in Oslo is 23 degrees and sunny.
d. Back
2. Phone
Say: Opening Phone menu
a. Contact book
Say: Opening Contact book
i. Home:
1. Say: Calling Home will not be provided in this test. Please choose
another option.
ii. Work:
1. Say: Calling Work will not be provided in this test. Please choose
another option.
iii. Alexander: +47 977 65 888
1. Say: Calling Alexander
2. Perform call
iv. Taxi
1. Say: Calling Taxi will not be provided in this test. Please choose
another option.
Dissertation Task 2
0834060
Page 70 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
v. Back
b. Dial a number
i. Dialing numbers will not be provided in this test. Please choose another
option.
ii. Back
c. Back
3. Navigation
Say: Opening Navigation menu
a. Current location
i. Say: Your current location is….
b. Compass
i. Display compass
ii. Back
c. Navigate to
Say: Opening Navigate to
i. Home
1. Say: Navigating to Home will not be provided in this test. Please
choose another option.
ii. Work
1. Say: Navigating to Work will not be provided in this test. Please
choose another option.
iii. Grocery store
1. Say: Navigating to Grocery store will not be provided in this test.
Please choose another option.
iv. Bank
1. Say: Navigating to Bank will not be provided in this test. Please
choose another option.
v. Back
d. Back
4. Analyze
Say: Opening Analyze menu
a. Launch Google Goggles
b. Back
5. Applications
Say: Opening applications menu
a. Web browser
i. Say: The web browser application will not be opened in this test. Please
choose another option.
b. Facebook
i. Say: The Facebook application will not be opened in this test. Please choose
another option.
c. Mail
i. Say: The mail application will not be opened in this test. Please choose
another option.
d. Text messages
Dissertation Task 2
0834060
Page 71 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
i. Say: The text messages application will not be opened in this test. Please
choose another option.
e. Back
Dissertation Task 2
0834060
Page 72 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix G.F - Layout of UI, October 13, 2010
The application should inform the user of successful opening of a sub-menu, in addition of
informing the user when returning to the main menu. A problem was discovered in the first
round of testing, where text being read out is canceled if another selection is made. A solution
to this issue is to have the system prioritize menu and sub-menu messages, allowing them to
finish playing before stating elements. Individual elements should still be canceled by other
elements selected.
The operation of elements should to be changed to improve navigation of the UI. Instead of
first tapping once to have an option read out and then tap one more time to select it, a gesture
should to be introduced to improve the selection of elements.
With the introduction of a gesture; menu options are still read out with a single tap, while
opening elements are performed trough holding the finger on the option and slide right to
open. This should make it easier to select elements, as well as improve on incorrectly opening
wrong elements since the finger never leaves the screen.
All menu elements should state elements number and total number of elements in the current
list. Example: 1 of 4 Facebook, 2 of 4 Mail etc. This applies for all menus, including main
menu.
To improve navigation, a shortcut to the top-main menu should be introduced. The option
―Home‖, should be at the top of every menu, except for the main menu‖ and take up half the
size of a normal menu option.
Second round of testing should also implement list navigation in Contact book, Applications
and Travel to. Please referrer to visual design for implementation. The UI should pre-load all
applications and contacts, and only display navigation letters matching applications and
contacts. Ex. B should only be displayed if an application begins with B.
1. Information
Say: Opening Information menu
a. Time
i. Say: The current time is ”CURRENT TIME”
b. Date
i. Say: Today’s date is ”CURRENT DATE”
c. Today’s weather
i. Say: The weather at your current location in Oslo is 23 degrees and sunny.
d. Back
2. Phone
Say: Opening Phone menu
a. Contact book
Say: Opening Contact book
i. Home:
1. Say: Calling Home will not be provided in this test. Please choose
another option.
ii. Work:
Dissertation Task 2
0834060
Page 73 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
1. Say: Calling Work will not be provided in this test. Please choose
another option.
iii. Alexander: +47 977 65 888
1. Say: Calling Alexander
2. Perform call
iv. Taxi
1. Say: Calling Taxi will not be provided in this test. Please choose
another option.
v. Back
b. Dial a number
i. Dialing numbers will not be provided in this test. Please choose another
option.
c. Back
3. Navigation
Say: Opening Navigation menu
a. Your location
i. Say: Your current location is….
b. Compass
i. Display compass
c. Travel to
Say: Opening Travel to
i. Home
1. Say: Traveling to Home will not be provided in this test. Please
choose another option.
ii. Work
1. Say: Traveling to Work will not be provided in this test. Please
choose another option.
iii. Grocery store
1. Say: Traveling to Grocery store will not be provided in this test.
Please choose another option.
iv. Bank
1. Say: Traveling to Bank will not be provided in this test. Please choose
another option.
v. Back
d. Back
4. Analyze
Say: Opening Analyze menu
a. Launch Google Goggles
b. Back
5. Applications
Say: Opening applications menu
a. Web browser
i. Say: The web browser application will not be opened in this test. Please
choose another option.
b. Facebook
Dissertation Task 2
0834060
Page 74 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
i. Say: The Facebook application will not be opened in this test. Please choose
another option.
c. Mail
i. Say: The mail application will not be opened in this test. Please choose
another option.
d. Text messages
i. Say: The text messages application will not be opened in this test. Please
choose another option.
e. Back
Dissertation Task 2
0834060
Page 75 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
APPENDIX H: DOCUMENTATION OF UI
The following appendix contains documentation of the UI used during the development. G.A
presents documentation of the UI as it stands in iteration 5. G.B to G.F presents the virtual
models; created in Microsoft Expression Blend 4 with SketchFlow (Microsoft Corportation
2009), a tool allowing non-developers to create working virtual applications of the final
product. The following documentation is the printout of the working applications.
Appendix H.A – Documentation of UI, version 0.0.5
The following document presents the UI prototype at the current stage of development;
version 0.0.5.
Operation of the UI is operated through sound and tactile feedback. A single tap on the screen
will make the UI talk, and state the function of the selected element, while the gesture ―tap
and dragging the finger to the right‖ will execute the element. Dragging the finger across the
screen will make the UI read out functions as the finger approaches and at the same time
make the phone vibrate to indicate that a new item is available. A back element is placed at
the bottom of every screen, except for the top main menu, allowing the user to easily navigate
to the previous menu.
To help the user build a virtual map of the different menus and elements, the UI will state
which level it is displaying and when successfully executing an element. The UI can also be
customized to state the total numbered elements for each view, where current selected
element place number is stated followed by total elements available in the current list.
All screenshots are actual shots of how the application looks on the mobile phone. The
following section will provide screenshots of each sub menu available for the user.
Information
The main menu is the start
page, providing access to
sub menus and functions.
Selecting Information will
present the following menu.
Dissertation Task 2
Time, Date and Todays
weather is available. Each
function will state different
information depending on
selected function.
0834060
Page 76 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Phone menu
The main menu is the
start page, providing
access to sub menus
and functions.
Selecting Phone menu
will present the
following menu.
Phone menu starts
with a sub-menu,
providing access to
Contact book and Dial
a number.
Selecting Contact
book will bring up a
list of available predefined contacts.
Selecting Dial a
number will enable the
user to dial a number
manually through
Enter number.
Navigation
The main menu is the start
page, providing access to
sub menus and functions.
Selecting Navigation will
present the following
menu.
Dissertation Task 2
Navigation starts with a submenu, providing access to
Current location, Compass
and Travel to. Selecting
Current location will state
the phones current location.
Compass will start a third
party application displaying a
compass, while Travel to will
take the user to a new menu.
Travel to allow the user
to navigate through large
lists of data. On the right
side is an alphabetical
list, which will update the
list on the left according
to the selected letter. I
0834060
Page 77 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Analyze
The main menu is the start
page, providing access to
sub menus and functions.
Selecting Analyze will
present the following menu.
The Analyze menu allows
the user to launch an OCR
application. Google
Goggles is used in this
example.
Applications
The main menu is the start
page, providing access to
sub menus and functions.
Selecting Applications will
present the following menu.
Dissertation Task 2
Applications provide a list
of applications which the
user can launch. In this
example Web browser,
Facebook, Mail and Text
messages are available.
0834060
Page 78 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix H.B – Documentation of Conceptual Design
The following document is a general overview on how the intended application will operate
and its functions with a short description. The functions listed are not necessarily the final
one, and should be considered as a work in progress. This can for example change trough the
feedback received from the interviews performed on the test participants.
The document lists an iPhone as the phone of use. This is done for visual representation.
Through the development project, decision during development platform and supported
mobile phones will be made. The only requirement set out by the project is that the phone is
easily available through the general commercial market; have an open operating system
enabling the use of third party developed applications, touch screen, GPS, compass, level
meter and a camera.
Prototype Map
The following map, displays the flow of the virtual prototype application. When starting the
application, the user will begin at ―Start‖ and then navigate to appropriate sub-menus.
Figure 1: SketchFlow Map
Navigation Screens
The following slides display the intended navigation of the program. Although the screens
display text, the navigation is not intended to be used by visual navigation, although it
supports it, but through the use of sound played through the mobile phone’s attached hands
free/headphone. When hovering with the finger over an item, a sound will play stating the
name of the current selected alternative. Tapping with the finger on the same place, will open
the selected alternative.
Dissertation Task 2
0834060
Page 79 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Start
When starting the program, the user will be presented with the following screen. This is the
main menu of the application, and will guide the user to all functions of the application.
Figure 2: Start
Analyze
This tool will use the mobile phones internal camera to automatically recognize elements in
front of the camera. Items that can be detected are pre-configured. If the user holds a NOK
100,- bill in front of the camera, the application will play a sound telling the user that it can
see a ―NOK 100,- bill‖.
It is also intended that the application will include a list of traffic lights and positions of
placement. The first version will start out small, focusing on smaller parts of Oslo, Norway,
but it is intended that the application shall include a list of all traffic lights for supported
countries. For easier navigation, the list will (if possible) include the latitude for the traffic
light as well so that the application can guide the user in pointing the mobile phone’s camera
in the right direction and angle. The application will then detect the color of the light on the
traffic light.
Items that can be detected, in addition to updated traffic light information can be wirelessly
transferred to the mobile phone from the support center.
Dissertation Task 2
0834060
Page 80 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Figure 3: Analyze
Assistance
This function will automatically place a phone call between the user’s phone and the support
center. An internet connection will be established, enabling the support center to remotely see
through the mobile phone’s internal camera. The support center can also re-program the
phone’s pre-defined lists, in case the user wishes to travel to a location not stored on the
mobile phone.
Figure 4: Assistance
Dissertation Task 2
0834060
Page 81 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Local weather
This function will automatically go online and download the latest weather report for the
current location, for then to play the report through the hands free/head phones.
Figure 5: Local weather
Locate me
This function will automatically locate were the user is located and play the position through the
hands free/head phones.
Figure 6: Locate me
Travel
This function includes a pre-defined list of locations, were the user can get travel assistance from
the mobile phone. The first version will include up to four pre-defined locations. If the user would
like to travel to a destination not on the list or would like to have the list updated, the user can use
the Assistance function, to have the support center update the list of pre-defined locations.
Dissertation Task 2
0834060
Page 82 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Figure 7: Travel
Navigate
After proper selection is made, from the previous pre-defined location screen, the user will be
presented with the travel route through the hands free/head phones.
Figure 8: Navigate
Dissertation Task 2
0834060
Page 83 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix H.C – Documentation of Second Prototype, round 1 of testing
SketchFlow Map
Figure 1: SketchFlow Map
Navigation Screens
Start
Figure 2: Start
Analyze
Figure 3: Analyze
Dissertation Task 2
0834060
Page 84 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Applications
Figure 4: Applications
Contact book
Figure 5: Contact book
Information
Figure 6: Information
Dissertation Task 2
0834060
Page 85 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Navigate
Figure 8: Navigate
Navigate to
Figure 9: Navigate to
Phone
Figure 10: Phone
Dissertation Task 2
0834060
Page 86 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix H.D – Documentation of Third Prototype, round 2 of testing
SketchFlow Map
Figure 1: SketchFlow Map
Navigation Screens
Start
Figure 2: Start
Analyze
Figure 3: Analyze
Dissertation Task 2
0834060
Page 87 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Applications
Figure 4: Applications
Contact book
Figure 5: Contact book
Information
Figure 6: Information
Dissertation Task 2
0834060
Page 88 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Navigate
Figure 7: Navigate
Navigate to
Figure 8: Navigate to
Phone
Figure 9: Phone
Dissertation Task 2
0834060
Page 89 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
APPENDIX I: DEVELOPMENT AND ACTIVITY LOG
The following log documents all activities and reported bugs during the development
process of the UI. All documentation was documented in a separate reporting tool
called Redmine (n.d.).
04/11/2010
10:02
Bug #142: New list view, bottom element does not play
A bug has been discovered in the new list view function, where lists containing 2 or 4
elements will not play the bottom element when pressed. Applies only when tapping
individual elements, dragging the finger across the screen works as intended. Alexander
Dreyer Johnsen
03/11/2010
11:57
UIBLV.apk
For public test. Kim Ruben Teigen
11:56
Revision 24: Version for next public test.
Version for next public test. Kim Ruben Teigen
11:55
Revision 23: Fixes issues #130, #139 and #140.
Fixes issues #130, #139 and #140. Kim Ruben Teigen
Feature request #130 (Fixed): State elements number and total number of
elements in the current list
11:55
Kim Ruben Teigen
11:33
Bug #140 (Fixed): Possible dead space below back
Kim Ruben Teigen
11:32
Bug #139 (Fixed): Selecting an item, releasing screen and gesturing to right will
not open element
Kim Ruben Teigen
09:38
UIBLV.apk
Changes after first usertests. Kim Ruben Teigen
09:37
Revision 22: Tag for version 0.0.4.
Tag for version 0.0.4. Kim Ruben Teigen
01/11/2010
11:02
Feature request #130: State elements number and total number of elements in
the current list
Menu elements under applications should state elements number and total number of
elements in the current list. Example: 1 of 4 Facebook, 2 of 4 Mail etc. Alexander Dreyer
Johnsen
11:01
Bug #140: Possible dead space below back
There seems to be dead space/empty pixels below the back button on certain menus. Has
been confirmed on the Navigation screen. Alexander Dreyer Johnsen
Bug #139: Selecting an item, releasing screen and gesturing to right will not
open element
10:59
Certain menus are not responding correctly when opening sub-elements. It should be
possible to tap an element, release the screen for then to be able to select the same area and
gesture to right to open the element. This is workign correctly o... Alexander Dreyer Johnsen
Dissertation Task 2
0834060
Page 90 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
09:30
Feature request #132 (Fixed): Implement list navigation in Contact book,
Applications and Travel to
Applied in changeset r21. Kim Ruben Teigen
09:29
Revision 21: Made the List Activity complete. Every control works with touch.
Fixes #132.
Made the List Activity complete. Every control works with touch. Fixes #132. Kim Ruben
Teigen
28/10/2010
14:03
Revision 20: A basic list is implemented. ListView with touch functionality. An
alphabeth list on...
A basic list is implemented. ListView with touch functionality. An alphabeth list on the right to
help navigating. Kim Ruben Teigen
14:01
Feature request #132: Implement list navigation in Contact book, Applications
and Travel to
Almost done. Only need to add touch functionality to the Back button in the list. Kim Ruben
Teigen
27/10/2010
11:19
Feature request #131 (Ignored): Add "Home" functionality
Kim Ruben Teigen
10:15
Feature request #131 (On hold): Add "Home" functionality
There are some problems with the main menu top bar. The best way to implement this would
perhaps be to just add an text element at the top instead of a whole new element. Need to
discuss this with Alexander. Kim Ruben Teigen
26/10/2010
15:03
Feature request #129 (Fixed): Change the way elements are selected
Applied in changeset r19. Kim Ruben Teigen
Revision 19: Implemented methods to navigate by sliding towards the right
after the menu item is ...
15:03
Implemented methods to navigate by sliding towards the right after the menu item is chosen.
Fixes #129. Kim Ruben Teigen
Feature request #130 (On hold): State elements number and total number of
elements in the current...
12:24
Kim Ruben Teigen
11:59
Change request #136 (Ignored): Change Applications menu
Kim Ruben Teigen
11:38
Change request #135 (Fixed): Change Navigation menu
Applied in changeset r18. Kim Ruben Teigen
11:38
Revision 18: Changed some text basicly. Fixes #135.
Changed some text basicly. Fixes #135. Kim Ruben Teigen
10:54
Change request #134 (Fixed): Change of Phone menu
Applied in changeset r17. Kim Ruben Teigen
Revision 17: Changed some strings for the contact book and the phone menu.
Fixes #134.
10:54
Dissertation Task 2
0834060
Page 91 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Changed some strings for the contact book and the phone menu. Fixes #134. Kim Ruben
Teigen
10:04
Change request #134: Change of Phone menu
Due to time restrictions we will only implement simple "not implemented" feedback and not a
detailed information as wanted. Kim Ruben Teigen
09:48
Change request #133 (Fixed): Change of information menu
Applied in changeset r16. Kim Ruben Teigen
09:48
Revision 16: Added some pre text for time and date. Changed how the delay
should work with items ...
Added some pre text for time and date. Changed how the delay should work with items that
only speaks when selected. Fixes #133. Kim Ruben Teigen
09:23
Change request #137 (Closed): Documentation for version 0.0.4
Kim Ruben Teigen
Bug #128 (Fixed): The application should always inform the user of successful
opening of a sub-menu
09:21
Applied in changeset r15. Kim Ruben Teigen
Revision 15: All activities will now implement the BaseActivity and also the delay
to prevent tou...
09:21
All activities will now implement the BaseActivity and also the delay to prevent touch events.
Fixes #128. Kim Ruben Teigen
25/10/2010
Revision 14: Started to move some shared Activity values and logic into a
BaseActivity class. Add...
15:34
Started to move some shared Activity values and logic into a BaseActivity class. Added logic
to delay touch events OnResume. Kim Ruben Teigen
13/10/2010
16:13
Layout_of_UI_13102010.docx
Alexander Dreyer Johnsen
16:13
Document: Documentation for 0.0.4
Alexander Dreyer Johnsen
16:12
Change request #137: Documentation for version 0.0.4
A visual model of version 0.0.4 can be accessed from http://www.adj.no/master/v4 The
attached document provides a complete overview of all functions and layout Alexander
Dreyer Johnsen
16:10
Change request #136: Change Applications menu
Applications menu should be changed to Applications Say: Opening applications menu Web
browser Say: The web browser application will not be opened in this test. Please choose
another option. Facebook Say: The Facebook application will ... Alexander Dreyer Johnsen
16:09
Change request #135: Change Navigation menu
Navigation Say: Opening Navigation menu Your location Say: Your current location is….
Compass Display compass Travel to (Changed from Navigate to) Say: Opening Travel to
(opening sub-menu) * Home Say: Traveling to Home will not b... Alexander Dreyer Johnsen
16:06
Change request #134: Change of Phone menu
The phone menu should be changed to the following Phone Say: Opening Phone menu
Contact book Say: Opening Contact book (start of sub-menu) * * Home: Say: Calling Home
will not be provided in this test. Please choose another option. ... Alexander Dreyer Johnsen
Dissertation Task 2
0834060
Page 92 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
16:02
Change request #133: Change of information menu
Change the information menu to the following Information * Say: Opening Information menu
Time * Say: The current time is ”CURRENT TIME” Date * Say: Today’s date is ”CURRENT
DATE” Today’s weather * Say: The weather at your current ... Alexander Dreyer Johnsen
Feature request #132: Implement list navigation in Contact book, Applications
and Travel to
16:00
Implement list navigation in Contact book, Applications and Travel to. Please referrer to
visual design for implementation (http://www.adj.no/master/v3). The UI should pre-load all
applications and contacts, and only display navigation letters mat... Alexander Dreyer
Johnsen
15:58
Feature request #131: Add "Home" functionality
To improve navigation, a shortcut to the top-main menu should be introduced. The option
“Home”, should be at the top of every menu, except for the main menu” and take up half the
size of a normal menu option. Alexander Dreyer Johnsen
15:56
Feature request #130: State elements number and total number of elements in
the current list
All menu elements should state elements number and total number of elements in the
current list. Example: 1 of 4 Facebook, 2 of 4 Mail etc. This applies for all menus, including
main menu. Alexander Dreyer Johnsen
15:55
Feature request #129: Change the way elements are selected
The operation of elements should to be changed to improve navigation of the UI. Instead of
first tapping once to have an option read out and then tap one more time to select it, a
gesture should to be introduced to improve the selection of element... Alexander Dreyer
Johnsen
Bug #128: The application should always inform the user of successful opening
of a sub-menu
15:53
The application should inform the user of successful opening of a sub-menu, in addition of
informing the user when returning to the main menu. A problem was discovered in the first
round of testing, where text being read out is canceled if another... Alexander Dreyer
Johnsen
06/10/2010
08:44
Revision 13
Kim Ruben Teigen
08:43
UIBLV.apk
This was sent to test outside the house. Kim Ruben Teigen
28/09/2010
11:41
Bug #125 (Fixed): Opening string must remove colon
Applied in changeset r12. Kim Ruben Teigen
11:41
Revision 12: Fixes #125. Removed ":" from the strings.xml.
Fixes #125. Removed ":" from the strings.xml. Kim Ruben Teigen
27/09/2010
14:53
Revision 11: Alpha 2 version
Alpha 2 version Kim Ruben Teigen
14:42
Bug #125: Opening string must remove colon
When accessing one of the sub-meuns, and going back to the main menu; the voice feedback
pronounces the :. This applieas for all sub-menues except Analyze. Alexander Dreyer Johnsen
22/09/2010
Dissertation Task 2
0834060
Page 93 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
09:56
UIBLV.apk
Android install package Kim Ruben Teigen
15/09/2010
15:02
Revision 10: Added opening strings to all menues that should have them.
Added opening strings to all menues that should have them. Kim Ruben Teigen
14:02
Change request #105 (Fixed): Change several menu actions
Kim Ruben Teigen
Revision 9: Fixes #103. Added values-nb folder to hold norwegian language
strings.
14:01
Fixes #103. Added values-nb folder to hold norwegian language strings. Kim Ruben Teigen
14:00
Feature request #103 (Fixed): Norwegian language support
Kim Ruben Teigen
13:19
Revision 8: This fixes #104. Added 3 lvl menues and fixed all navigation.
This fixes #104. Added 3 lvl menues and fixed all navigation. Kim Ruben Teigen
13:18
Change request #104 (Fixed): 3 level menu system
Kim Ruben Teigen
09:30
Change request #105: Change several menu actions
Several of the menu actions should not start external applications anymore. Thay should
instead inform the user that the action is not yet implemented. Kim Ruben Teigen
09:25
Change request #104: 3 level menu system
There should be three levels of menues. This is specifically for the Phone Menu. Kim Ruben
Teigen
09:19
Feature request #103: Norwegian language support
The application should have support for Norwegian language. This is due to the fact that most
users will be Norwegians. Kim Ruben Teigen
07:39
Revision 7: Tag for versrion 0.0.1, First Alpha.
Tag for versrion 0.0.1, First Alpha. Kim Ruben Teigen
07:30
Layout_of_UI_13092010.docx
New UI description from Alexander Kim Ruben Teigen
07:30
Layout_of_UI_30082010.docx
UI description from Alexander Kim Ruben Teigen
07:29
UIBLV.apk
Android install file Kim Ruben Teigen
31/08/2010
14:52
Revision 6: Initial version done with english language as default.
Initial version done with english language as default. Kim Ruben Teigen
30/08/2010
15:44
Revision 5: Most of the menus are added. Information is finished.
Most of the menus are added. Information is finished. Kim Ruben Teigen
Dissertation Task 2
0834060
Page 94 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
27/08/2010
15:20
Revision 4: First simple menu test.
First simple menu test. Kim Ruben Teigen
23/08/2010
11:42
Revision 3: More initial import.
More initial import. Kim Ruben Teigen
11:40
Revision 2: Initial import.
Initial import. Kim Ruben Teigen
11:13
Wiki edit: Info (#1)
Kim Ruben Teigen
09:48
Revision 1: Skeleton created
Skeleton created root
Dissertation Task 2
0834060
Page 95 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
APPENDIX J: INFORMATION TO PROJECT PARTICIPANTS
The following information was provided to all participants taking part in the study.
Dissertation Task 2
0834060
Page 96 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
APPENDIX K: CONSENT FORM
All participants in the study accepted and filled out the following consent form.
Dissertation Task 2
0834060
Page 97 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
APPENDIX L: PARTICIPANT SURVEY
The following survey questionnaires were used in the first round of testing. Due to the
fact that the people participating in the study had vision loss, the questions and
responses were provided verbally and written down by the author of this report.
Appendix L.A: participant survey, round 1
Date:
Personal information
Sex
Male
Age
Type of vision
Full
If vision is low or blind, indicate how long
Born this way
Do you use a mobile phone today?
Buttons
Yes
If yes, is it operated trough
Female
Low
Blind
Since the age of ____
No
Touch screen
If no, why do you not use a mobile phone?
Rate your general technical knowledge
1 = “Not very knowledgeable”, 5 = “Very
knowledgeable”
Survey on UI
On a scale from 1 to 5, where 1 is ―strongly disagree‖ and 5 is ―strongly agree‖ please mark the
following statements
1 = “strongly disagree”, 5 = “strongly agree”
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between
menus/options
The categorization of sub-menus were logical
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
1 = “strongly disagree”, 5 = “strongly agree”
Navigation
It was easy to locate the navigation option
It was easy to locate the ―Locate me‖ option
It was easy to select one of the available pre-defined
locations
1 = “strongly disagree”, 5 = “strongly agree”
Dissertation Task 2
0834060
Page 98 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Applications
It was easy to locate the applications option
It was easy to find available applications
It was easy to launch an application
1 = ―strongly disagree‖, 5 = ―strongly agree‖
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
1 = ―strongly disagree‖, 5 = ―strongly agree‖
The solution/product
I personally felt that the menu system was limiting my
use of the mobile phone (Note: All features have not been
1 = ―strongly disagree‖, 5 = ―strongly agree
implemented in this prototype)
I prefer this solution above others
I would use this solution in my daily life
Please provide suggestions to improvements
Dissertation Task 2
0834060
Page 99 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix L.B: Participant survey, round 2
Date:
Personal information
Sex
Male
Female
Age
Type of vision
Full
If vision is low or blind, indicate how long
Born this way
Do you use a mobile phone today?
Buttons
Yes
If yes, is it operated trough
Low
Blind
Since the age of ____
No
Touch screen
If no, why do you not use a mobile phone?
Rate your general technical knowledge
1 = “Not very knowledgeable”, 5 = “Very
knowledgeable”
Survey on UI
On a scale from 1 to 5, where 1 is ―strongly disagree‖ and 5 is ―strongly agree‖ please mark the
following statements
1 = ―strongly disagree‖, 5 = ―strongly agree
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between
menus/options
The categorization of sub-menus were logical
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
1 = ―strongly disagree‖, 5 = ―strongly agree
Navigation
It was easy to locate the navigation option
It was easy to locate the ―Locate me‖ option
It was easy to select one of the available pre-defined
locations
1 = ―strongly disagree‖, 5 = ―strongly agree
Applications
It was easy to locate the applications option
It was easy to find available applications
1 = ―strongly disagree‖, 5 = ―strongly agree
Dissertation Task 2
0834060
Page 100 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
It was easy to launch an application
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
1 = ―strongly disagree‖, 5 = ―strongly agree
New select view (Travel to)
It was easy to browse through the list view letters
It was easy to locate items available in the list
It was easy to execute an item
1 = ―strongly disagree‖, 5 = ―strongly agree
Numbers in front of list elements
It makes it easier to navigate when numbers are in front
of list elements
1 = ―strongly disagree‖, 5 = ―strongly agree
The solution/product
I personally felt that the menu system was enabling and
improved my use the mobile phone (Note: All features
1 = ―strongly disagree‖, 5 = ―strongly agree
have not been implemented in this prototype)
I prefer this solution above others
I would use this solution in my daily life
Please provide suggestions to improvements
Dissertation Task 2
0834060
Page 101 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
APPENDIX M: RESSULTS FROM USER TESTING
The following appendix provides all of the results from the user testing. Round 1 is first summarized, followed by the individual data from
that round. Round 2 then follows, with a summary and individual data. The appendix concludes with a comparison of results from round 1
and round 2.
Appendix M.A: Results from round 1, Overview of all responses
Participant 1 Participant 2 Participant 3 Participant 4 Statistics
Personal Information
Sex
Age
Type of vision
Been blind since
Use mobile phones
Operated trough
Technical knowledge
SURVEY of UI
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between menus/options
The categorization of sub-menus were logical
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
Dissertation Task 2
Female
46
Low
Birth
Yes
Buttons
3
3
2
4
2
5
5
5
4
Female
50
Very low
Age 13
Yes
Buttons
2
4
4
4
2
3
3
4
4
Female
54
Blind
Birth
Yes
Buttons
3
4
N/A
5
2
4
5
4
4
Male
50
Blind
Birth
Yes
Buttons
4
Female
50,0
Split
Birth
Yes
Buttons
3,0
5
5
4
4
5
5
Score
4,0
3,7
4,3
2,5
4,3
4,5
5
5
Score
4,5
4,3
0834060
Page 102 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Navigation
It was easy to locate the navigation option
It was easy to locate the "Locate me" option
It was easy to select one of the available pre-defined locations
Applications
It was easy to locate the applications option
It was easy to find available applications
It was easy to launch an application
4
4
4
3
4
4
5
5
2
4
4
4
4
4
4
4
4
1
5
5
5
Score
4,0
4,3
4,3
5
5
5
Score
4,5
4,5
3,0
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
4
4
5
5
5
3
3
3
4
4
4
4
5
5
5
5
Score
4,5
4,0
4,3
4,3
The solution/product
I personally felt that the menu system was limiting my use of the mobile phone
I prefer this solution above others
I would use this solution in my daily life
3
1
1
2
N/A
2
2
N/A
3
2
4
3
Score
2,3
2,5
2,3
COMMON FEEDBACK & OBSERVATIONS
Negative
It is too easy to cancel what is being said by taping somewhere else
Had to remember were elements were located
Audible feedback is a little hard to understand
Dissertation Task 2
Count
4
3
3
0834060
Page 103 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Too easy to select an item
Having to lift the finger to make a selection, makes it hard to select
Skeptical to how it will be to navigate through several contacts (more than 5)
The phone is “nagging”
Felt not having control
Positive
Voice feedback
Easier to deal with text than icons
The text is bright and clear, easy to read
Liked that the number of elements were limited
Preferred list view instead of grid view
Liked the way menus were organized
It was nice to be able to use a touch phone
Practice makes you better
2
2
2
1
1
Count
3
1
1
1
1
1
1
1
1
Would have used the solution, as long as it provides access to useful
applications and features
Observations
User regularly presses to fast, hence stopping the messages from being read
The back key is not always working
The "this is a test message" is too long
If an option is pressed more than once, it will play messages the number of times
the option is pressed
The "Locate me" option is hard to locate
The options should be presented in the users native language
The feedback from this user might suggest that people with low vision
prefers grid view while blind people prefer list view
Dissertation Task 2
Count
4
1
1
3
1
1
1
0834060
Page 104 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
1
The user tried to press the screen between elements, hence not being able
to select any element
Uses the index finger to navigate
The phone can be a little slow at times
Holds the phone in the right hand, and uses the left to select
(two hand operation)
Does not read back each time it is pressed
The technical knowledge can turn out to be a challenge
Suggestions
It is easier to drag the finger left and release, than double tap to select an
element
Items could be opened by selecting/holding for a couple of seconds
It would be better to perform selections with another finger, instead of having
to tap on the same area
Should be possible to choose if text should be read out or not
Prefers the way the iPhone operates, although it can only display icons and it
is not possible to both enlarge the text and have spoken feedback
The knowledge of sales people selling mobile phones, is to low when it comes
to people with vision loss
User-friendliness is important
The phone should vibrate when the finger is on an element
It can be a good idea to define different level of information provided
to the user
Dissertation Task 2
1
1
1
1
1
Count
1
1
1
1
1
1
1
1
1
0834060
Page 105 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.B: Results from round 1, Participant 1
Test performed
29.09.2010
Personal Information
Sex
Age
Type of vision
Been blind since
Use mobile phones
Operated trough
Technical knowledge
Statistics
Female
Low
Birth
Yes
Buttons
3
SURVEY of UI
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between menus/options
The categorization of sub-menus were logical
Score
3
2
4
2
5
5
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
Score
5
4
Navigation
It was easy to locate the navigation option
It was easy to locate the "Locate me" option
It was easy to select one of the available pre-defined locations
Score
4
4
4
Applications
It was easy to locate the applications option
It was easy to find available applications
It was easy to launch an application
Score
5
5
2
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
Score
4
4
5
5
The solution/product
I personally felt that the menu system was limiting my use of the mobile phone
I prefer this solution above others
I would use this solution in my daily life
Score
3
1
1
Dissertation Task 2
0834060
Page 106 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
FEEDBACK & OBSERVATIONS
Negative
Prefers to navigate in grid view compared to list view
Too easy to hit an item
Having to lift the finger to make a selection, makes it hard to select
Positive
Voice feedback
Easier to deal with text than icons
The text is bright and clear, easy to read
Observations
User regularly presses to fast, hence stopping the messages from being read
The back key is not always working
The "this is a test message" is to long
If an option is pressed more than once, it will play messages the number of times the
option is pressed
The "Locate me" option is hard to locate
The options should be presented in the users native language
The feedback from this user might suggest that people with low vision prefers grid
view while blind people prefer list view
Suggestions
Items could be opened by selecting/holding for a couple of seconds
Should be possible to choose if text should be read out or not
Prefers the way the iPhone operates, although it can only display icons and it is not
possible to both enlarge the text and have spoken feedback
The knowledge of sales people selling mobile phones, is to low when it comes to
people with vision loss
User-friendliness is important
Dissertation Task 2
0834060
Page 107 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.C: Results from round 1, Participant 2
Test performed
STATISTICS
Personal Information
Sex
Age
Type of vision
Been blind since
Use mobile phones
Operated trough
Technical knowledge
29.09.2010
Statistics
Female
50
Low
Age 13
Yes
Buttons
2
SURVEY of UI
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between menus/options
The categorization of sub-menus were logical
Score
4
4
4
2
3
3
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
Score
4
4
Navigation
It was easy to locate the navigation option
It was easy to locate the "Locate me" option
It was easy to select one of the available pre-defined locations
Score
3
4
4
Applications
It was easy to locate the applications option
It was easy to find available applications
It was easy to launch an application
Score
4
4
4
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
Score
5
3
3
3
The solution/product
I personally felt that the menu system was limiting my use of the mobile phone
I prefer this solution above others
I would use this solution in my daily life
Score
2
N/A
2
Dissertation Task 2
0834060
Page 108 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
FEEDBACK & OBSERVATIONS
Negative
The logical placement of elements was a little hard, but can be learnt
Had to remember were elements were located
Audible feedback is a little hard to understand (Norwegian voice)
Positive
Liked that the number of elements were limited
Preferred list view instead of grid view
Liked the way menus were organized
Although the users’ vision is low, she preferred to use the audible feedback
It was nice to be able to use a touch phone
Screen reader
Observations
If you press a new element too quickly, it will overwrite the audible feedback
from the previous element
The user tried to press the screen between elements, hence not being able to
select any element
If you press an element several times, the feedback will be announced the
number of times the element was pressed
Suggestions
The phone should vibrate when the finger is on an element
Dissertation Task 2
0834060
Page 109 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.D: Results from round 1, Participant 3
Test performed
STATISTICS
Personal Information
Sex
Age
Type of vision
Been blind since
Use mobile phones
Operated trough
Technical knowledge
30.09.2010
Statistics
Female
54
Blind
Birth
Yes
Buttons
3
SURVEY of UI
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between menus/options
The categorization of sub-menus were logical
Score
4
N/A
5
2
4
5
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
Score
4
4
Navigation
It was easy to locate the navigation option
It was easy to locate the "Locate me" option
It was easy to select one of the available pre-defined locations
Score
4
4
4
Applications
It was easy to locate the applications option
It was easy to find available applications
It was easy to launch an application
Score
4
4
1
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
Score
4
4
4
4
The solution/product
I personally felt that the menu system was limiting my use of the mobile phone
I prefer this solution above others
I would use this solution in my daily life
Score
2
N/A
3
Dissertation Task 2
0834060
Page 110 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
FEEDBACK & OBSERVATIONS
Negative
It is hard to tap at the same place
Audible feedback is a little hard to understand (Norwegian voice)
The phone is “nagging”
She felt she did not have control
It is too easy to double tap
Messages are read a little slow
Does not state the current level adequately
Positive
Preferred a smaller phone, 3,2” screen
Practice makes you better
Observations
If you press a new element too quickly, it will overwrite the audible feedback
from the previous element
Uses the index finger to navigate
If you press an element several times, the feedback will be announced the
number of times the element was pressed
The phone can be a little slow at times
Holds the phone in the right hand, and uses the left to select (two hand operation)
Does not read back each time it is pressed
The technical knowledge can turn out to be a challenge
Suggestions
It can be a good idea to define different level of information provided to the user
It is easier to drag the finger left and release, than double tap to select an element
Dissertation Task 2
0834060
Page 111 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.E: Results from round 1, Participant 4
Test performed
STATISTICS
Personal Information
Sex
Age
Type of vision
Been blind since
Use mobile phones
Operated trough
Technical knowledge
30.09.2010
Statistics
Male
50
Blind
Birth
Yes
Buttons
4
SURVEY of UI
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between menus/options
The categorization of sub-menus were logical
Score
5
5
4
4
5
5
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
Score
5
5
Navigation
It was easy to locate the navigation option
It was easy to locate the "Locate me" option
It was easy to select one of the available pre-defined locations
Score
5
5
5
Applications
It was easy to locate the applications option
It was easy to find available applications
It was easy to launch an application
Score
5
5
5
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
Score
5
5
5
5
The solution/product
I personally felt that the menu system was limiting my use of the mobile phone
I prefer this solution above others
I would use this solution in my daily life
Score
2
4
3
Dissertation Task 2
0834060
Page 112 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
FEEDBACK & OBSERVATIONS
Negative
It is too easy to cancel what is being said by taping somewhere else
Skeptical to how it will be to navigate through several contacts (more than 5)
Skeptical to how it will be to navigate through several applications (more than 5)
Positive
Would have used the solution, as long as it provides access to useful applications
and features
Observations
If you press a new element too quickly, it will overwrite the audible feedback
from the previous element
Suggestions
It would be better to perform selections with another finger, instead of having to
tap on the same area
Dissertation Task 2
0834060
Page 113 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.F: Results from round 2, Overview of all responses
Participant 1 Participant 2 Participant 3 Participant 4 Participant 5 Statistics
Personal Information
Sex
Age
Type of vision
Been blind since
Use mobile phones
Operated trough
Technical knowledge
SURVEY of UI
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between
menus/options
The categorization of sub-menus were logical
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
Dissertation Task 2
Male
Female
50
Blind
Birth
Yes
Buttons
Female
54
Blind
Birth
Yes
Buttons
5
Female
46
Low
Birth
Yes
Buttons
3
Male
50
Very low
5
47
Blind
13
Yes
Buttons
3
Female
49,4
Blind
Birth
Yes
Buttons
3,6
30
Yes
Buttons
2
5
5
5
5
4
4
4
4
4
3
5
5
5
5
5
4
4
4
4
2
5
5
5
5
4
Score
4,6
4,6
4,6
4,6
3,6
5
5
5
4
5
4,8
5
5
Score
4,8
4,6
5
5
5
5
5
5
4
3
0834060
Page 114 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Navigation
It was easy to locate the navigation option
It was easy to locate the "Locate me" option
5
5
5
4
5
5
4
4
5
5
Score
4,8
4,6
Applications
It was easy to locate the applications option
It was easy to find available applications
It was easy to launch an application
5
5
5
5
5
4
5
5
4
4
4
4
5
5
5
Score
4,8
4,8
4,4
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
5
5
5
5
5
5
5
5
5
5
5
5
4
4
4
4
5
5
5
5
Score
4,8
4,8
4,8
4,8
New select view (Travel to)
It was easy to browse through the list view letters
It was easy to locate items available in the list
It was easy to execute an item
Numbers in front of list elements
It makes it easier to navigate when numbers are in front of list
elements
4
5
5
3
5
2
3
5
5
3
3
4
5
5
5
Score
3,6
4,6
4,2
4
5
2
3
5
Score
3,8
4
5
5
4
5
Score
4,6
The solution/product
I personally felt that the menu system was enabling and
improving my use of the mobile phone
Dissertation Task 2
0834060
Page 115 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
I prefer this solution above others
I would use this solution in my daily life
COMMON FEEDBACK & OBSERVATIONS
Negative
List view has too small letters
List view is too sensitive on selecting letters
4 N/A
4 N/A
Dissertation Task 2
N/A
4
5
4,0
4,3
Count
4
4
1
"Opening main menu" may seem like it is loading the menu,
and not finished opening
Wonders if elements needs to be closed
(time/date/weather)
Did not like having numbers in front of elements
The vibration is a little short
Dragging the finger sloping downward open elements
Positive
It is a good thing to have numbers in front of elements
The voice feedback is good
It is a good thing to open elements with the gesture of
dragging the finger to the right
Appreciated that feedback from the first round was
encountered for in this version
Likes that it is a list
Everything works much better now!
The whole application feels different
Has a more positive view on touch phones with this solution!
Likes that it is only displaying a window/menu at the time
It is fun to use a touch phone
4 N/A
4
1
1
1
1
Count
2
2
1
1
1
1
1
1
1
1
0834060
Page 116 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Observations
Sometimes tries to make a selection between elements
Let's go of the finger a little late on the right side
Participant normally navigates only through speech
Count
2
1
1
1
Tries to select items too fast at times, resulting in the phone
not responding fast enough
Did not consider the vibration, was listening to the voice instead
Vibration was not needed
Suggestions
Should be possible to turn numbering elements on or off
Should be possible to define the amount of text being read
The user should be able to define the necessary settings
Vibration should be stronger
Should be possible to turn vibration on or off
It should be possible to search in a list, not just selecting the
first letter
Numbers are good on larger lists, but not on smaller lists
Instead of having an element called back, introduce a gesture
were dragging the finger to the left will go back one menu
An individual not used to syntactical voice would soon get
tired of it
Element number should be read after the element name,
not in front
Dissertation Task 2
1
1
Count
4
2
2
1
1
1
1
1
1
1
0834060
Page 117 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.G: Results from round 2, Participant 1
Test performed
04.11.2010
Personal Information
Sex
Age
Type of vision
Been blind since
Use mobile phones
Operated trough
Technical knowledge
Statistics
Male
50
Blind
Birth
Yes
Buttons
5
SURVEY of UI
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between menus/options
The categorization of sub-menus were logical
Score
5
5
5
5
4
5
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
Score
5
5
Navigation
It was easy to locate the navigation option
It was easy to locate the "Locate me" option
Score
5
5
Applications
It was easy to locate the applications option
It was easy to find available applications
It was easy to launch an application
Score
5
5
5
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
Score
5
5
5
5
New select view (Travel to)
It was easy to browse through the list view letters
It was easy to locate items available in the list
It was easy to execute an item
Score
4
5
5
Dissertation Task 2
0834060
Page 118 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Numbers in front of list elements
It makes it easier to navigate when numbers are in front of list elements
Score
4
The solution/product
I personally felt that the menu system was enabling and improving my use of the
mobile phone
I prefer this solution above others
I would use this solution in my daily life
Score
4
4
4
FEEDBACK & OBSERVATIONS
Negative
List view has too small letters
List view is too sensitive on selecting letters
"Opening main menu" may seem like it is loading the menu, and not finished opening
Positive
It is a good thing to have numbers in front of elements
Observations
Suggestions
It should be possible to turn off numbering elements
Should be possible to define the amount of text being read
Dissertation Task 2
0834060
Page 119 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.H: Results from round 2, Participant 2
Test performed
04.11.2010
Personal Information
Sex
Age
Type of vision
Been blind since
Use mobile phones
Operated trough
Technical knowledge
Statistics
Female
54
Blind
Birth
Yes
Buttons
3
SURVEY of UI
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between menus/options
The categorization of sub-menus were logical
Score
4
4
4
4
3
5
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
Score
5
5
Navigation
It was easy to locate the navigation option
It was easy to locate the "Locate me" option
Score
5
4
Applications
It was easy to locate the applications option
It was easy to find available applications
It was easy to launch an application
Score
5
5
4
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
Score
5
5
5
5
New select view (Travel to)
It was easy to browse through the list view letters
It was easy to locate items available in the list
It was easy to execute an item
Score
3
5
2
Dissertation Task 2
0834060
Page 120 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Numbers in front of list elements
It makes it easier to navigate when numbers are in front of list elements
Score
5
The solution/product
I personally felt that the menu system was enabling and improving my use of the
mobile phone
I prefer this solution above others
I would use this solution in my daily life
Score
5
N/A
N/A
FEEDBACK & OBSERVATIONS
Negative
Wonders if elements needs to be closed (time/date/weather)
List view is too sensitive on selecting letters
List view has too small letters
Positive
It is a good thing to have numbers in front of elements
It is a good thing to open elements with the gesture of dragging the finger to the right
Appreciated that feedback from the first round was encountered for in this version
Observations
Let's go of the finger a little late on the right side
Sometimes tries to make a selection between elements
Suggestions
It should be possible to turn off numbering elements
Should be possible to define the amount of text being read
The user should be able to define the necessary settings
Vibration should be stronger
Dissertation Task 2
0834060
Page 121 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.I: Results from round 2, Participant 3
Test performed
05.11.2010
Personal Information
Sex
Age
Type of vision
Been blind since
Use mobile phones
Operated trough
Technical knowledge
Statistics
Female
46
Low
Birth
Yes
Buttons
3
SURVEY of UI
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between menus/options
The categorization of sub-menus were logical
Score
5
5
5
5
5
5
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
Score
5
5
Navigation
It was easy to locate the navigation option
It was easy to locate the "Locate me" option
Score
5
5
Applications
It was easy to locate the applications option
It was easy to find available applications
It was easy to launch an application
Score
5
5
4
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
Score
5
5
5
5
New select view (Travel to)
It was easy to browse through the list view letters
It was easy to locate items available in the list
It was easy to execute an item
Score
3
5
5
Dissertation Task 2
0834060
Page 122 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Numbers in front of list elements
It makes it easier to navigate when numbers are in front of list elements
Score
2
The solution/product
I personally felt that the menu system was enabling and improving my use of the
mobile phone
I prefer this solution above others
I would use this solution in my daily life
Score
5
4
4
FEEDBACK & OBSERVATIONS
Negative
Did not like having numbers in front of elements
The vibration is a little short
The voice feedback is good
List view is too sensitive on selecting letters
List view has too small letters
Positive
Likes that it is a list
Everything works much better now!
The whole application feels different
Observations
Normally navigates only trough speech
Sometimes tries to make a selection between elements
Tries to select items too fast at times, resulting in the phone not responding fast enough
Suggestions
Should be possible to turn numbers off
Should be possible to define settings
Dissertation Task 2
0834060
Page 123 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.J: Results from round 2, Participant 4
Test performed
05.11.2010
Personal Information
Sex
Age
Type of vision
Been blind since
Use mobile phones
Operated trough
Technical knowledge
Statistics
Female
50
Very low
13
Yes
Buttons
2
SURVEY of UI
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between menus/options
The categorization of sub-menus were logical
Score
4
4
4
4
2
4
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
Score
4
3
Navigation
It was easy to locate the navigation option
It was easy to locate the "Locate me" option
Score
4
4
Applications
It was easy to locate the applications option
It was easy to find available applications
It was easy to launch an application
Score
4
4
4
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
Score
4
4
4
4
New select view (Travel to)
It was easy to browse through the list view letters
It was easy to locate items available in the list
It was easy to execute an item
Score
3
3
4
Dissertation Task 2
0834060
Page 124 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Numbers in front of list elements
It makes it easier to navigate when numbers are in front of list elements
Score
3
The solution/product
I personally felt that the menu system was enabling and improving my use of the
mobile phone
I prefer this solution above others
I would use this solution in my daily life
Score
4
N/A
4
FEEDBACK & OBSERVATIONS
Negative
Dragging the finger sloping downward open elements
List view is too sensitive on selecting letters
List view has too small letters
Positive
Has a more positive view on touch phones with this solution!
Observations
Did not consider the vibration, was listening to the voice instead
Suggestions
It should be possible to search in a list, not just selecting the first letter
Numbers are good on larger lists, but not on smaller lists
Dissertation Task 2
0834060
Page 125 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.K: Results from round 2, Participant 5
Test performed
Personal Information
Sex
Age
Type of vision
Been blind since
Use mobile phones
Operated trough
Technical knowledge
20.11.2010
Statistics
Male
47
Blind
30
Yes
Buttons
5
SURVEY of UI
Menu system
The menu system was easy to use
The menu system made the touch phone easier to use
The options spoken was easy to understand
It was easy to navigate between menus and sub-menus
The vibration made it easier to change between menus/options
The categorization of sub-menus were logical
Score
5
5
5
5
4
5
Phone
It was easy to locate the phone option
It was easy to navigate through phone contacts
Score
5
5
Navigation
It was easy to locate the navigation option
It was easy to locate the "Locate me" option
Score
5
5
Applications
It was easy to locate the applications option
It was easy to find available applications
It was easy to launch an application
Score
5
5
5
Information
It was easy to locate the information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays weather is
Score
5
5
5
5
New select view (Travel to)
It was easy to browse through the list view letters
It was easy to locate items available in the list
It was easy to execute an item
Score
5
5
5
Dissertation Task 2
0834060
Page 126 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Numbers in front of list elements
It makes it easier to navigate when numbers are in front of list elements
Score
5
The solution/product
I personally felt that the menu system was limiting my use of the mobile phone
I prefer this solution above others
I would use this solution in my daily life
Score
5
N/A
5
FEEDBACK & OBSERVATIONS
Negative
Positive
Likes that it is only displaying a window/menu at the time
Likes the voice feedback
It is fun to use a touch phone
Observations
Vibration was not needed
Suggestions
Instead of having an element called back, introduce a gesture were dragging the
finger to the left will go back one menu
An individual not used to syntactical voice would soon get tired of it
Should be possible to turn vibration on or off
Should be possible to turn numbering elements on or off
Element number should be read after the element name, not in front
Dissertation Task 2
0834060
Page 127 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.L: Results from round 1 and round 2 compared against each other
Part. 1
STATISTICS
Personal Information
Sex
Age
Type of vision
Been blind since
Use mobile phones
Operated trough
Technical knowledge
SURVEY of UI
Menu system
The menu system was easy to use
The menu system made the touch
phone easier to use
Part. 2
Part. 3
Part. 4
Round 1 Part. 1
Female Female Female Male Female Male
46
50
54
50
50,0
50
Low Very low Blind
Blind
Split Blind
Birth
13
Birth
Birth
Birth Birth
Yes
Yes
Yes
Yes
Yes
Yes
Buttons Buttons Buttons Buttons Buttons Buttons
3
2
3
4
3,0
5
Round 2 Change
Part. 2
Part. 3
Part. 4
Part. 5
Female
54
Blind
Birth
Yes
Buttons
3
Female
46
Low
Birth
Yes
Buttons
3
Female
50
Very low
13
Yes
Buttons
2
Male
Female Female
47
49,4
49,3
Blind
Blind
Blind
30
Birth
Birth
Yes
Yes
Yes
Buttons Buttons Buttons
5
3,6
0,6
3
2
4
4
4
N/A
5
5
4,0
3,7
5
5
4
4
5
5
4
4
5
5
4,6
4,6
0,6
0,9
The options spoken was easy to
understand
4
4
5
4
4,3
5
4
5
4
5
4,6
0,4
It was easy to navigate between
menus and sub-menus
2
2
2
4
2,5
5
4
5
4
5
4,6
2,1
The vibration made it easier to
change between menus/options
5
3
4
5
4,3
4
3
5
2
4
3,6
-0,7
The categorization of sub-menus
were logical
Average
5
3
5
5
4,5
5
5
5
4
5
4,8
0,3
Dissertation Task 2
3,9
4,5
0,6
0834060
Page 128 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Phone
It was easy to locate the phone
option
5
4
4
5
4,5
5
5
5
4
5
4,8
0,3
It was easy to navigate through
phone contacts
Average
4
4
4
5
4,3
5
5
5
3
5
4,6
0,4
Navigation
It was easy to locate the navigation
option
It was easy to locate the "Locate
me" option
It was easy to select one of the
available pre-defined locations
Average
Applications
It was easy to locate the
applications option
It was easy to find available
applications
It was easy to launch an application
Average
Dissertation Task 2
4,4
4,7
0,3
4
3
4
5
4,0
5
5
5
4
5
4,8
0,8
4
4
4
5
4,3
5
4
5
4
5
4,6
0,4
4
4
4
5
4,3
4,3
4,1
4,7
0,6
5
4
4
5
4,5
5
5
5
4
5
4,8
0,3
5
4
4
5
4,5
5
5
5
4
5
4,8
0,3
2
4
1
5
3,0
5
4
4
4
5
4,4
1,4
4,0
4,7
0,7
0834060
Page 129 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Information
It was easy to locate the
information option
It was easy to tell the time
It was easy to tell todays date
It was easy to find out what todays
weather is
Average
New select view (Travel to)
It was easy to browse through the
list view letters
It was easy to locate items available
in the list
It was easy to execute an item
Average
4
5
4
5
4,5
5
5
5
4
5
4,8
0,3
4
5
5
3
3
3
4
4
4
5
5
5
4,0
4,3
4,3
5
5
5
5
5
5
5
5
5
4
4
4
5
5
5
4,8
4,8
4,8
0,8
0,6
0,6
4,3
4,8
0,6
4
3
3
3
5
3,6
3,6
5
5
5
3
5
4,6
4,6
5
2
5
4
5
4,2
4,2
4,1
Numbers in front of list elements
It makes it easier to navigate when
numbers are in front of list
elements
Average
Dissertation Task 2
4
5
2
3
5
3,8
3,8
3,8
0834060
Page 130 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
The solution/product
I personally felt that the menu
system was enabling and improving
my use of the mobile phone
I prefer this solution above others
I would use this solution in my daily
life
Average
Dissertation Task 2
3
2
2
2
2,3
4
5
5
4
5
4,6
2,4
1
1
N/A
2
N/A
3
4
3
2,5
2,3
4
4
N/A
N/A
4
4
N/A
4
N/A
5
4,0
4,3
1,5
2,0
2,3
4,3
2,0
0834060
Page 131 of 132
MAKING TOUCH-BASED MOBILE PHONES ACCESSIBLE FOR THE VISUALLY IMPAIRED
Appendix M.M: T-Test and Effect sizes
While the Design Research method does not require statistical analyses, these were
nevertheless carried out to shed more light on the changes in scoring that were evident
between the two versions of the UI. Effect sizes and differences between means were
evaluated across the categories previously outlined. Due to the small sample size, a
certain measure of leniency with respect to level of significance was judged
necessary; this was therefore set to 0.1. Thus mean scores, available in figure 7, were
found to be significantly higher for the second round of testing, compared to the first
round, for the navigation functions (t(3) = 2.45, p>0.1), for the information functions
(t(3) = 2.45, p>0.1), and for the solution functions (t(3) = 5.44, p>0.05). Effect sizes
were judged to be high for all three functions (r = 0.41; r = 0.40; r = 0.89;
respectively). Effect sizes were similarly high for the menu functions (r = 0.37) and
the application functions (r = 0.41), but the differences between means were nonsignificant (t(3) = 1.47, ns; t(3) = 1.48, ns; respectively).
Paired Samples Test
Paired Differences
Std. Error 95% Confidence Inter.
Mean
Std. Dev.
Mean
Lower
Upper
t
df
Sig.
Pair 1 Menu_1 - Menu_2
-.50000
.68041
.34021
-1.58269
.58269
-1.470
3
.238
Pair 2 Phone_1 - Phone_2
-.25000
.64550
.32275
-1.27713
.77713
-.775
3
.495
Pair 3 Nav_1 - Nav_2
-.50000
.40825
.20412
-1.14961
.14961
-2.449
3
.092
Pair 4 App_1 - App_2
-.58333
.78764
.39382
-1.83664
.66997
-1.481
3
.235
Pair 5 Info_1 - Info_2
-.50000
.40825
.20412
-1.14961
.14961
-2.449
3
.092
Pair 6 Solu_1 - Solu_2
-2.04167
.75000
.37500
-3.23508
-.84825
-5.444
3
.012
* Contrast marked in green is significant to the 0.05 level
(0.05 is standard: 95% chance that the difference is not due to coincidence)
* Contrast marked in blue is significant to the 0.10 level
(0.10 is less used, but can be justified due to the low number of participants:
90% chance that the difference is not due to coincidence)
Effect sizes
d
r
r2
Pair 1
Menu_1 - Menu_2
0.80418
0.37306
0.13917
Pair 2
Phone_1 - Phone_2
0.39736
0.19487
0.03797
Pair 3
Nav_1 - Nav_2
0.89443
0.40825
0.16667
Pair 4
App_1 - App_2
0.89866
0.40986
0.16798
Pair 5
Info_1 - Info_2
0.86602
0.39736
0.15789
Pair 6
Solu_1 - Solu_2
3.84971
0.88739
0.78746
Dissertation Task 2
0834060
Page 132 of 132
