AMAyA Java ME accessibility API

The Product/Outcome
Exploitation Plans
Intellectual Property Rights
Technical & Socioeconomic considerations/challenges and impact
Collaborators and Future Work

The Product/Outcome
  1. Title of (final) product/outcome: Java ME accessibility API
  2. Developer (AEGIS beneficiary): Oracle
  3. Co-developers (AEGIS beneficiary): CERTH/HIT
  4. Purpose/main functionality & intended use: Definition of the Java ME accessibility API, implemented (in other activities) for LCDUI and LWUIT and AWT; utilized in the developer tools of NetBeans and the LWUIT Resource Editor. The intended use of AMAyA is to make JavaME devices – particularly feature phones – accessible to people with disabilities through its implementation for LWUIT, LCDUI, and AWT. See more in D4.2.1a and b (downloadable here)
  5. Platforms/Operating Systems/Devices:
  6. Main innovation and comparison to the State of the Art: Defining a full accessibility API for Java ME devices that can be used by assistive technologies on the one hand, and implemented for a range of Java ME UI component sets / toolkits. The key innovations of AMAyA lie in the following: (1) implementable via brokers so as to not require significant changes in the Java mobile UI toolkits (LWUIT, LCDUI, AWT), (2) lightweight, requiring little memory footprint or processor demands, (3) implementable on low-end feature phones that are very inexpensive. Compared to the state of the art on iPhone and Android, the two key improvements in AMAyA are (1) that it fully implements the AEGIS OAF and specifically the accessibility API requirements contained in the OAF and also in ISO 13066-1, and (2) that it can be implemented on low-end feature phones that have far less memory or processor requirements as compared to iPhone and Android.
  7. Maturity level/Stage: Laboratory prototype. AMAyA is not yet mature, but is rather under active development – being implemented and proven on LWUIT, LCDUI, and AWT.
  8. Open Source (Yes/No): Not at present, but Oracle has released the Java ME platform under the GPL v2 license and has released the LWUIT libraries under the LGPL license.
  9. End-user documentation: As AMAyA is for developers, there will be no end user training. Developer material will be published by final release and will be made available via the usual Oracle Java channels for Java ME information.
  10. Contact details (of the principal developer): Kostas Kalogirou ( This e-mail address is being protected from spambots. You need JavaScript enabled to view it ) (Oracle's developers contact details are not publishable according to Oracle's policy).
Exploitation Plans
  1. Uptake by Open Source community: Uptake has not yet happened by open source community yet– AMAyA is not yet part of a shipping LWUIT
  2. Proprietary exploitation:
    • Time to market (since when): Within 2013
    • Anticipated target price/annual sales: LWUIT itself is free; Java ME licensing details are not public
    • Exploitation role and rights (of main and co-developers/integrators): It is anticipated that this will be folded into the Java ME platform, and included in various Java ME libraries such as LWUIT. Copyright of the source code belongs to CERTH/HIT and Oracle. External contributors retain copyright of their submission. This development is under the OCA agreement.
Intellectual Property Rights
  1. Intellectual property rights: As per the AEGIS Consortium IP agreement, CERTH executed the Oracle Contributor Agreement for this co-developed IP.
Technical & Socioeconomic considerations/challenges and impact
  1. Possible market applications – further research: Expected use by anyone creating mobile ICT who wants to take advantage of the various value propositions of the Java Mobile platform and also be accessible. This includes every market sector: government, industry, education, etc.
  2. Marketability: Java ME is already very marketable, having been implemented more than 1 billion mobile phones. With the passage of the 21st Century Communication and Video Accessibility Act in the U.S., and widespread adoption of the UN Convention on the Rights of Persons with Disabilities, accessibility in JavaME should also be very marketable.
  3. Deployment (so far or near future): AMAyA still needs to be proven before it will be ready for sale.
  4. Expected impact: We anticipate that the expected impact is quite significant, given the more than 1 billion mobile phones that run JavaME today.
  5. Customers: Developers of mobile applications, and handset manufacturers.
  6. "Go-to-market approach": Available worldwide as part of LWUIT and JavaME. The key dissemination action for AMAyA has been the yearly JavaOne conference, along with regional JavaOne events worldwide, the CSUN conferences as well as the AEGIS events and exhibitions.
    Also, the Java Mobile edition platform, which Oracle licenses to hardware manufacturers of mobile phones, PDAs, eReaders, etc. anticipates to include a number of AEGIS mobile developments including AMAyA Java Mobile accessibility API and implementation of AMAyA for LWUIT.
    Also, in December 2011, CERTH/HIT presented its mobile work in the business event in Thessaloniki, where it had the opportunity to come into contact with vendors and have discussions for future exploitation in the context of integrated services.
  7. Commercialisation barriers: Performance on low-end devices; support in the Java Mobile runtime as implemented by various Java ME licensees on their devices (e.g. Nokia Series 40)
Collaborators & Future Work
  1. Collaborations: Technical collaboration with Code Factory, investigating exposing AMAyA outside of the Java ME runtime to enable Mobile Speak to be the AT re-presenting the Java mobile application in an accessible modality.
  2. Further research and development steps-future collaboration: More development would be tied to market interest. The relevant know-how will be transferred by CERTH/HIT in the context of Cloud4all IP initiative, on auto-configuration aspects