Difference between revisions of "Mobile/smart devices"

Jump to: navigation , search
Line 51: Line 51:
 
==Approaches to implement eAccessibiltiy for mobile devices==
 
==Approaches to implement eAccessibiltiy for mobile devices==
 
===Justifying adoption of eAccessibility===
 
===Justifying adoption of eAccessibility===
Besides [[Legislation]] and general facts advocating for [[eAccessibility]] the following resources help to justify why mobile accessibility is crucial in the information society.  
+
Besides [http://hub.eaccessplus.eu/wiki/Mobile/smart_devices#Legislation Legislation] and general facts advocating for [[eAccessibility]] the following resources help to justify why mobile accessibility is crucial in the information society.  
 
* Current studies show that an increasing number of users access the internet using their smart phone. “The Importance of Mobile Device Accessibility” provides an extended statistics where and how mobile devices are used  
 
* Current studies show that an increasing number of users access the internet using their smart phone. “The Importance of Mobile Device Accessibility” provides an extended statistics where and how mobile devices are used  
 
* Numerous users suffering from different kinds of disabilities now use smartphones to achieve the same goals, like receiving emails using navigation and of course accessing the web. “Smartphone technology as an accessibility platform” offers an overview of nowadays development progress in the field of accessibility for smartphones initially provided by the producers: [http://www.guardian.co.uk/smart-accessibility/smartphone-technology-as-an-accessibility-platform The Guardian: Smartphone technology as an accessibility platform]
 
* Numerous users suffering from different kinds of disabilities now use smartphones to achieve the same goals, like receiving emails using navigation and of course accessing the web. “Smartphone technology as an accessibility platform” offers an overview of nowadays development progress in the field of accessibility for smartphones initially provided by the producers: [http://www.guardian.co.uk/smart-accessibility/smartphone-technology-as-an-accessibility-platform The Guardian: Smartphone technology as an accessibility platform]

Revision as of 14:40, 19 June 2012


Mobile devices have become everyday companions to almost any people. People are even expected to use them and to stay connected when they are moving, be it on the job, due to security or health reasons or due to private reasons. Many applications support daily activities such as

  • Communication via audio, video, text or haptic channel
  • Web Surfing
  • Navigation
  • Office (writing, note taking, pictures, drawing)
  • Calendar
  • Games
  • Media players (Audio, audio books, video)
  • Cameras
  • Sensors and monitoring applications

Such applications are running on different types of mobile devices suitable for one or a number of applications:

Taking the [statistics of older adults and people with disabilities] into account and also considering the manifold situations where standard interaction modes fail, mobile device accessibility becomes an indispensible requirement. Important aspects of mobile devices include:

  • Small display
  • Lack of pointing possibilities
  • Small keyboards
  • Low text input rate
  • Low bandwith
  • Impact on Accessibility
    • Lack of context
    • Information overload
    • No visual alternatives
    • Color coding

This section of the eAccess+ HUB provides information on Mobile Devices Accessibility linking into the most relevant resources coming from hardware, software and web accessibility as well as design, development and management support. Read more on Approaches to implementing eAccessibility for mobile devices: an organised list of resources providing general advice on proposing, defining and implementing an eAccessibility strategy. Standards and Guidelines: an index of relevant formal documents guiding the process of commissioning and implementing accessible ICTs. Legislation: links to relevant legislation from EU member states that organisations working in the cultural heritage domain should be aware of when implementing an eAccessibility strategy. Case Studies: examples of best practice that can provide inspiration and reference.

Contents

Approaches to implement eAccessibiltiy for mobile devices

Justifying adoption of eAccessibility

Besides Legislation (external) and general facts advocating for eAccessibility the following resources help to justify why mobile accessibility is crucial in the information society.

  • Current studies show that an increasing number of users access the internet using their smart phone. “The Importance of Mobile Device Accessibility” provides an extended statistics where and how mobile devices are used
  • Numerous users suffering from different kinds of disabilities now use smartphones to achieve the same goals, like receiving emails using navigation and of course accessing the web. “Smartphone technology as an accessibility platform” offers an overview of nowadays development progress in the field of accessibility for smartphones initially provided by the producers: The Guardian: Smartphone technology as an accessibility platform (external)
  • Although not every smartphone provides the same amount of mobility features, the techniques and technology are evolving. Nevertheless, web site designers and providers (see WAI W3 (external)) and developers of mobile application have to consider this issue as well to make use of the accessibility features provided by smartphones (see Apple guideline for iOS development (external) and Android guideline for app development (external))

Beneficiaries of eAccessibilty

Web sites, application and devices considering the issue of accessibilty are beneficial for a broad user group. Modern smartphones can provide lots of helpful services to older people, people with disablility as well as people dealing with situation which cause a temporariy disability whten they are on the move. This means, that web sites should be adapted to fit the requirements of smartphone user in general. In addition, an accessible application can be still useable each if the user cannot have a lock at it since he or she is tied up with other tasks. This user group is growing and will probably be an important portion of the whole number of users. The following resources give reason for that:

  • An overview and a report of the growing number of older smartphone users [1] (external)
  • A report of how many people from the UK access the internet and also how many of them are disabled and older [2] (external)
  • A proper concept of operation including an accessible and hands-free user interface would prevent a lot of accidents caused by drivers using cell phones. This is resource provides statistics about using cell phones and driving accidents [3] (external)

Managing implementation of eAccessibility

Successfully designing and implementing accessible Apps depends on multiple factors. Well-trained software developers who have the knowledge about what accessibility means, and who have a basic understanding of how people with disabilities use their mobnile devices. Another important step is to follow the development guidelines listed in the coresponding section of this document. This documents describe the technical needs that are necessary to create accessible mobile apps.

The following links give you some hints on how to effectively create mobile applications.

Designing for Accessibility or mobile devices

Today's common smart phone operating systems like iOS, Android or WindowsPhone provide sufficient means to make an application accessible. Developers can rely on predefined GUI widgets that allow them to build stable, easy to understand and predictable user interfaces. Those operating systems offer display themes that feature higher contrast and larger fonts for visually impaired people. For blind people each operating system has its own accessibility API that provides screenreaders and other assistive technology with the required information. However programmers need to ensure that their application and the used widgets implement those accessibility interfaces.

Native code that uses native widgets normally implements those interfaces by nature. However Runtimes likeJava ME (external) or Adobee Air (external) and their user interface widgets may not implement those accessibility API's. In this case it is not possible to create an application based on such a runtime that isaccessible for blind people. To make such an application accessible the source of the runtime itself had to be changed which is not possible in most cases.

Most operating systems provide guidelines and tools that provide effective approaches for the design and development of accessible ICTs:

Standards and guidelines

Mobile Device Accessibility is closely related to web accessibility and general software accessibility. The following guidelines are therefore relevant for mobile devices:

Case studies

During the last years the number of used mobile devices rapidly increased. As a consequence also solutions to make mobile devices accessibility for people with special needs have been developed.

Legislation

There is no legislation in Europe ruling the way a mobile App must be designed to meet accessibility standards yet. However, guidelines for accessible web content are also applicable for mobile applications, especcially those which operate with web content.

A comprehensive list of links to relevant documents can be found here (external)

Other issues

  • Mobile Device Security