1. The AEGIS story: building an
accessible application
Peter Korn, Accessibility Principal
AEGIS Workshop and International Conference, Brussels

2. OAF reference diagram
Creation
Define Accessible Stock Elements Developer Tools
AMAyA accessibility API LWUIT UI components LWUIT Resource Editor
- Defines what is needed - Implement AMAyA (via - Dev. Tool to design apps
by AT LWUIT Broker) - Integrates LWUIT
Java Mobile
- For LWUIT, LCDUI, AWT - Support themeing components
LWUIT keyboard operation - Integrates high contrast
- Defined for all elements LCDUI custom components themes
LWUIT themeing - Implement AMAyA (via
- CSS based theme engine LCDUI Broker) Accessibility Adviser
- Support themeing
LCDUI keyboard operation AMAyA-based tools
AWT keyboard operation AWT components - Ferret & Monkey
- Implement AMAyA (via
AWT Broker)
Android accessibility support Android custom components DroidDraw
Android
- Define new services for - New containers that allow - Drag & drop UI designer
custom features labeling of components - Uses ÆGIS components
- Define relationships - Accessibility aids
between UI components - Supports keyboard use
AEGIS Workshop and International Conference, Brussels 2

3. OAF reference diagram
Use
Platform Support The App Itself Assistive Technology
Legacy Java CLDC env. LWUIT applications AMAyA-based ATs
- Uses Symbian Series 60 - Locate accessible mobile - Screen Reader
and multi-tasking JVM - Contact Manager
Java Mobile
- Works with LWUIT, LCDUI - Messengering RTT application
- Cloud-based TTS
- eSpeak TTS engine LCDUI applications
- Contact Manager
Oracle Java Wireless Client - Messengering
- Supports loading of AT
- Optional TTS engine AWT application
- Works with LWUIT, LCDUI - Sample test app
Android Application Android ATs
Android & iOS
- Contact Manager - Tecla Access
- Dasher alternate text entry
- CCF communication
iOS ATs
- Dasher alternate text entry
AEGIS Workshop and International Conference, Brussels 3

4. Our protagonist
● Rakel Johannesson lives in
Gothenburg, Sweden
● Employed for four years as a
senior developer at a Ozeanus
Mobile Solutions IT
● Ozeanus develops mass market
apps as well as enterprise
solutions
● New project: develop an
accessible app that presents a
catalog of mobile devices for an
important mobile operator
● Must run on Java Mobile devices
AEGIS Workshop and International Conference, Brussels 4

5. Mrs. Johannesson's work environment
● Rakel uses many tools in her work:
● NetBeans for desktop & mobile apps
● LWUIT resource editor for LWUIT mobile apps
● Eclipse for BlackBerry and Android apps
● Xcode for iPhone apps
● Visual Studio for Symbian apps
● She does not have a disability
● She makes heavy use of open source tools and
components
AEGIS Workshop and International Conference, Brussels 5

6. Create an accessible catalog app
● Combination of corporate responsibility on the part of
the mobile operator – along with compliance with EU
and US laws – led to decision: make an accessible
catalog app
● Mobile market is very fragmented: many different
platforms – led to decision: use Java, which is on the
greatest number of phones
● Mobile operator has used Ozeanus Mobile Solutions in
the past for other apps, trusts them to do this new job
● Rakel Johannesson is a senior engineer at Ozeanus,
and so is given this new assignment
AEGIS Workshop and International Conference, Brussels 6

7. Mrs. Johannesson's research
● Methodology: Search the web for tools, resources, guidance in creating
accessible apps for the Java mobile platform
● Search results: Mobile UI components (LWUIT), developer tools,
simulation tools, and assistive technologies to test with & for users
● Relevant material for LWUIT developed in AEGIS:
● The LWUIT accessibility API has been defined to provide the information
needed to ATs [OAF step 1: “Define Accessible”]
● The LWUIT UI stock components implementing the accessibility API and
accessible high contrast themes [OAF step 2: “Stock Elements”]
● LWUIT's Resource Editor that incorporates accessible UI component sets and
accessible themes. The accessibility aids will be incorporated in year 4 of the
project [OAF step 3: “Developer Tool”]
● ACCESSIBLE project DIAS disability simulation tool for Java mobile apps
● Java mobile ATs (screen reader and monkey) that allow to validate the
accessibility of the application [OAF step 6: “Assistive Technology”]
AEGIS Workshop and International Conference, Brussels 7

8. Define end users, accessibility env.
● Use the Accessibility Adviser
● To understand the end user of their application and
their major barriers and limitations
● It will specify a set of recommendations that to
develop the application, as well as the
recommended technologies that can be used
● Select target peronas
● Low vision: Gert Van Dijk
● Blindness: Paulina Reyes
AEGIS Workshop and International Conference, Brussels 8

9. Design app w/accessibility support
● Development phase of application with first
accessibility tests:
● Use the resource editor to drag and drop accessible
LWUIT UI components [OAF step 2: “Stock Elements”]
● The accessibility support
checks that every component
is correctly labeled and shows
the relationship of the UI
components [OAF step 3:
“Developer Tool”]
● Generate a NetBeans project
AEGIS Workshop and International Conference, Brussels 9

10. Develop app w/accessibility support
● The developer continues working with the
NetBeans IDE [OAF step 5: “The app itself”]
● Makes use of tools to ensure the accessibility
quality of the application [OAF step 6: “AT”]
● Mobile Ferret
● Mobile Monkey
AEGIS Workshop and International Conference, Brussels 10

11. Accessibility simulation
● Simulation phase of development
● Uses ACCESSIBLE's DIAS (Disability Impairment
Approximation Simulator) tool for Java Mobile
● A better contrast is required for the end users
● She downloads a high contrast theme
AEGIS Workshop and International Conference, Brussels 11

12. User evaluation
● Testing with end users using
● Java Mobile screen reader [OAF step 6: “AT”]
● High contrast and large print themes [OAF step 2:
“Stock Elements”]
AEGIS Workshop and International Conference, Brussels 12

13. Release!
● Release of the application
● Finally the application is released and uploaded to
the app store
AEGIS Workshop and International Conference, Brussels 13

14. Summary
● Tools & components used to build the app:
● Accessibility Advisor [OAF step 3: “Developer Tool”]
● LWUIT's Resource Editor that incorporates accessible UI component sets
and accessible themes & NetBeans IDE [OAF step 3: “Developer
Tool”]
● LWUIT UI stock components implementing the accessibility API and
accessible high contrast themes [OAF step 2: “Stock Elements”]
● LWUIT accessibility API [OAF step 1: “Define Accessible”]
● Design the app w/accessibility support [OAF step 3, 5]
● Develop the application with accessibility support [OAF step 5, 6]
● Accessibility simulation with the ACCESSIBLE DIAS [OAF step 3]
● User evaluation [OAF step 4, 5, 6]
● Release!
AEGIS Workshop and International Conference, Brussels 14