Developer’s tool for LWUIT based on Resource Editor

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

The Product/Outcome
  1. Title of (final) product/outcome: Developer's tool for LWUIT based on Resource Editor
  2. Developer (AEGIS beneficiary): CTU (responsible for Accessibility support for LWUIT Resource editor)
  3. Co-developers (AEGIS beneficiary): Oracle (for the main Resource Editor application itself, along with collaboration within AEGIS with CTU)
  4. Purpose/main functionality & intended use: Accessibility support for LWUIT Resource Editor provides accessible development enhancement of standard Resource Editor. It is including features like checking of accessibility issues or Interface for easy connecting of labels with UI components. Accessibility support for LWUIT Resource Editor is intended to be used by mobile application developers (mainly LWUIT developers) to develop accessible LWUIT applications. See more in D4.4.1b, D4.4.1c and D1.4.3 (downloadable here)
  5. Platforms/Operating Systems/Devices: Java Platforms
  6. Main innovation and comparison to the State of the Art: The LWUIT Resource Editor allows developers and designers to create application UIs, localisation files, and themes without having to write LWUIT code (rather, it creates resources that are then mated with code to create the actual application). The main innovation of this solution is to enhance the Resource Editor to actively help developers and designers to create accessible LWUIT applications. This enhanced Resource Editor helps developers and designers annotate their components with critical accessibility metadata (ALT text for images, linking labels with the items they label), and flags places where such metadata is missing.
    There is no competitor, that we are aware of in the mobile space, nor really for UI programming in general – save our own work within AEGIS and the Accessibility Helper tool within Microsoft Office 2010 specifically for metadata and structure needed within Word documents.
  7. Maturity level/Stage: The Resource Editor is shipping. Our modifications to the Resource Editor is at the prototype level and it is fully dependent on the LWUIT Resource Editor.
  8. Open Source (Yes/No): It is anticipated to be open source
  9. End-user documentation: Accessibility support for LWUIT Resource Editor will be supported in AEGIS training platform.
  10. Contact details (of the principal developer):
Exploitation Plans
  1. Uptake by Open Source community:
    • Since when: Not released yet
Intellectual Property Rights
  1. Intellectual property rights: Copyright of the source code belongs to CTU and Oracle. External contributors retain copyright of their submission. This development is under the OCA agreement.
Technical & Socioeconomic considerations/challenges and impact
  1. Possible market applications – further research: The Resource Editor is already available and in use by mobile developers using LWUIT. We expect this would be the same market for our enhanced Resource Editor.
  2. Marketability: Accessibility support for LWUIT Resource Editor is not marketable as it is not a standalone application - it is fully dependent on open source Resource Editor.
  3. Deployment (so far or near future): Accessibility support for LWUIT Resource Editor is not intended for sale as it is fully dependent on open source Resource Editor, distributed for free.
  4. Expected impact: We expect this will have a very significant impact on LWUIT developers who care about accessibility.
  5. Customers: Mobile applications developers.
  6. "Go-to-market approach": There is no country/continent basis to our approach; they will simply be published on our website for anyone in the world to use.
    Prague ACM SIGCHI workshop focused on presentation of AEGIS tools to the local developer community, Prague, Czech Republic, May 2012. Accessibility support for LWUIT Resource Editor has been presented as a work in progress on conference Accessibility Reaching Everywhere - AEGIS Workshop and 2nd International Conference, 2011, Brussels, Belgium.
    CSUN - 27th Annual International Technology and Persons with Disabilities Conference / February 27 – March 3, 2012. Both the LWUIT high contrast themes, the AMAyA Broker for LWUIT, and the Screen Reader for Java Mobile were demonstrated in the talk “Using the AEGIS OAF: Making Java Mobile Apps”.
  7. Commercialisation barriers: The application can be used in any device with a Java Virtual Machine (MIDP 2.0 and later) and LWUIT support.
Collaborators & Future Work
  1. Collaborations: Nokia has adopted LWUIT 1.5 as part of the developer SDK for the Asha line of feature phones, which includes the Resource Editor. We anticipate Nokia will take up any future releases of the Resource Editor and LWUIT which contain this work.
  2. Further research and development steps-future collaboration: No further collaboration (beyond Nokia) has been announced.
Success stories
  • LWUIT Resource Editor Accessibility Features is not marketable as it is not a standalone application - it is fully dependent on the open source Resource Editor.
  • It is not intended to be sold as it is fully dependent on the open source Resource Editor, which is distributed for free.

FAQ

Q: How can I check the accessibility of my interfaces?
A: The developer can check the accessibility by pressing the wheelchair icon in the toolbar. This icon can be toggled on or off.

Q: How can I see if some components are not accessible?
A: When the developer toggles the accessibility checker ON, all of the non-accessible items in the interface will show a red wheelchair icon.

Q: Why is my component not accessible?
A: The developer can find out why the components are not accessible by looking for the error in the properties table of the component, shown in the right part of the Resource editor (Image 18).

Q: How can I solve this accessibility issue?
A: Usually, the error will be when a Label is not properly associated with a Component, so the developer must create a Label with the description of the component and associate it.