Download - 3 Use Cases towards All Inclusive Mainstream ICT

FOSS-AMASatellite event

Maria Gemou Centre for Research and Technology Hellas/Hellenic Institute of Transport

Greece

27-28 March 2010, Paphos, Cyprus


ÆGIS FP7 project (Open Accessibility Everywhere: Groundwork, Infrastructure, Standards; http://www.aegis-project.eu)◦ Seeks to determine whether 3rd generation access techniques will provide a more

accessible, more exploitable and deeply embeddable approach in mainstream Information and Communication Technologies (ICT) .

◦ This approach is developed and explored with the Open Accessibility Framework (OAF) through which aspects of the design, development and deployment of accessible mainstream ICT are addressed. The OAF provides embedded and built-in accessibility solutions, as well as toolkits for

developers, for “engraving” accessibility in existing and emerging mass-market ICT-based products, thus making accessibility open, plug & play, personalised & configurable, realistic & applicable in various contexts.

◦ In this way, ÆGIS is placing users and their needs at the centre of all ICT developments.



OAF is a comprehensive, holistic approach to programmatic support for assistive technologies.

This is in stark contrast to the 2nd generation approach to accessibility via assistive technologies on the proprietary Windows platform.

Building on the pioneering 3rd generation of the SoA Open Desktop in UNIX and GNU/Linux systems, OAF extends the concepts of programmatic accessibility in two directions: ◦ “upstream” into the developer tools for creating accessible

applications, and◦ “downstream” into further use and deployment – into

Internet technologies and mobile devices.



One of the key challenges addressed by ÆGIS is to provide appropriate design solutions that will contribute to reducing the 30% of the European population currently not using ICT.

In order to address this issue effectively, ÆGIS is committed to develop solutions that will receive wide acceptance from intended users.

For this purpose, the project has defined and is going to follow an appropriate user-centered development process, in which needs, wants, and limitations of the end user are given extensive attention at each stage of the development process.

The ÆGIS approach requires designers to analyse and foresee how users are likely to use a design solution, as well as to test the validity of their assumptions with regards to user behaviour in real world tests with actual users.



Based on a holistic User Centred Approach (UCD), ÆGIS identifies user needs and interaction models for several user groups (users with visual, hearing, motion, speech and cognitive impairments as well as application developers) and develops open source based generalised accessibility support into mainstream ICT devices/applications:◦ desktop,◦ rich web applications, and,◦ Java-based mobile devices.



Based on the findings of user needs and adopting a UCD approach, ÆGIS had, first of all, to develop a series of Use Cases and basic application scenarios for the targeted application areas and user groups, in order to support all coming phases of the project (design, development and evaluation).

Subsequently, it had to map the Use Cases with Personas and feed conceptual models.



ÆGIS Personas

ÆGIS Conceptual Models ÆGIS Major Application Scenarios

(on the basis of the Use Cases)

…on the basis of ÆGIS UCD & Definition of

users and stakeholders…

Understanding the user needs

(through field studies and workshops, local and Pan-European)

….taking into account the

definition/description of ÆGIS prototypes…

(WP1.5-ID1.5.2)

ÆGIS Use Cases

(covering desktop, mobile and RIA areas)

Iterative and interactive development and revision



DESKTOP USE CASES

1.Screen magnification for the GNOME Desktop (and Sun Ray system).

2.Windows screen reader for Java (“Java Access Bridge”).3.Printing Braille in OpenOffice.org.4.Accessibility Checking for ODF.5.Full DAISY book creation in OpenOffice.org .6.Comprehensible multi-lingual documents through a screen

reader.7.Open interface to Assistive Technologies. 8.Gesture switch.9.Gaze tracker- “send e-mail with your eyes”.10.Graphic Symbol Support for facilitated text comprehension

and production in OpenOffice.org.11.Integration of open real-time into audio, video, and text-

chat desktop applications.12.Generating accessible PDF from OpenOffice.org.



RIA USE CASES

1.Web developer developing accessible DHTML RIA application.2.Web developer developing accessible Java-based RIA application.3.Visually impaired user using Java-based RIA application.4.Creating an accessible internet map.5.Using an Internet map: orientation, manipulation and walking directions.6.Using an internet map: visual adaptation.7.Accessible Rich Internet map Applications using the OCR and VRML technology.8.ARIA support in browser.9.Applying WAI-ARIA to open-source CMS widgets.



MOBILE USE CASES

1.Accessible Mobile Phone for the blind.2.Mobile as an Augmentative and Alternative Communication (AAC) device for severe motor and/or speech impairments. 3.Symbol-based Augmentative and Alternative Communication (AAC) system for mobile devices for direct person-to-person (face-to-face) communication.4.Augmentative and Alternative Communication (AAC) for instant and text messaging (IM/SMS) on mobile devices.5.Onscreen keyboard for motor impaired operation of a mobile.6.Rapid text entry into a mobile device.7.Captions for the deaf display in mobile video.8.Audio description for the blind/low-vision played in mobile video.9.Real-Timer Text for mobile devices.10.Accessible messengering application for mobile devices.11.Accessible phone dialer and contact manager for mobile devices.12.Assistive technologies for mobile devices toolkit.13.Accessible applications for mobile devices toolkit.14.Mobile application developer developing accessible Java FX applications for mobile devices. 15.Developing accessible mobile s/w.



All Use Cases are accompanied by UML diagrams. Link to Personas (17 in total) has been established for

each of them. Priority level has been also established for each of them,

namely: “Essential”, “Secondary”, “Supportive”. ◦ Only 4 of them are considered “supportive”, whereas the rest of them

are all considered “essential” for the project.

3 major combination application scenarios are provided on the basis of the Use Cases envisaged.

Finally, based on the above, conceptual models have been produced.



Title Windows screen reader for Java (“Java Access Bridge”)

Context of use (aim) The aim is to ensure that Java applications running within Windows environments are as or more accessible by Windows screen readers as native Windows applications.

Primary actor 1.b Blind (without useful residual vision)

Secondary actor(s) -

Connected UCs -Screen magnification for the GNOME Desktop (and Sun Ray system)-Visually impaired user using Java-based RIA application

Priority Level Essential

Scenario(s) A blind user using a system that is able to pass accessibility information (e.g. name, role, state) from Java applications running in the Java Runtime Environment (JRE) on Windows on to screen reader applications running on Windows.




System output Passing information from the Java Runtime Environment (JRE) to the Windows accessibility architecture(s).

Preconditions User will need the required version of Windows.User will need the required version of JRE.User will need a screen reader using Iaccessible2.

Relevant ÆGIS WP WP2.2

Relevant ÆGIS Activity A2.2.2

Services involved Iaccessible, Iaccessible2, JDK

Application Area Desktop

Devices and restrictions It is intended that the solution will be robust enough to be applicable across whatever device makes use of the Gnome desktop.

Critical success parameters

The users [blind users using screen readers (JAWS, NVDA)] are not able to distinguish defects in their experience between using equivalent Java-based and native Windows applications on the Windows platform. The ability of Java applications to be usable with the scripting capabilities of scriptable Windows screen readers (e.g., JAWS, NVDA).




Environmental restrictions

WindowsXP, Windows Vista

Interaction level Step 1: The user opens a Java based application on WindowsStep 2: The system continuously passes accessibility information from the Java Accessibility API in the JRE to the Windows accessibility architecture, where it is usable by Windows screen readers.

Alternative Paths -

Important accessibility attributes

Many assistive technologies exist for the Windows platform, but these do not have access to information and controls within Java applications running inside the JRE without a “bridge”. The current Java Access Bridge enables some access, but requires assistive technologies to develop specifically for the bridge. By bridging to MSAA and Iaccessible2, the new bridge will leverage the standard accessibility APIs for the Windows platform that most assistive technology developers are using.




Background info/reason on selection and on assigning the priority level

Fully blind users using screen readers (JAWS, NVDA) should not able to distinguish defects in their experience between using equivalent Java-based and native Windows applications on the Windows platform.

Relevant PERSONAS - Gert Van Dijk (partly blurred vision) - Nitesh Sarin (dyslexic and colour blind)

References -

Comments The “Java Access Bridge” is a process-to-process communication system and does not include any direct user interface per se.



Profile: ◦ John, suffering from Usher syndrome, affecting both hearing and especially vision (retinitis

pigmentosa).◦ Famous writer of travel guides for people with vision impairments.◦ So far, due to lack of accessible map websites and support, it has been difficult to organise his life

independently (i.e. organising a trip on his own). ◦ Now, ÆGIS desktop, RIA and smartphone services make this much easier...

Scenario: ◦ Through ÆGIS enabled accessible internet maps, John is able to plan his trips ahead of schedule.

He is also able to explore new cities he visits. In that case: ◦ He first finds walking directions from a selected point A (often his hotel) to point B (an accessible

touristic site). ◦ He accesses the map and direction application using the screen magnifier with an increased screen

contrast, that also features speech synthesis (various languages are enabled allowing tours in a variety of foreign to him countries).

◦ He detects any accessible interesting sites nearby his walking route and as soon as he selects, he uploads all needed information on his smartphone.



The accessible RIA, where he has indicated his POI's and final destination is accessible for John via the phone browser and the integrated TTS.

Thus, at any point in time, while John is being guided through the streets of a city, he can benefit from the supporting tools on his mobile, just like he would have done at home using his desktop:

When extra information is provided in the form of a captioned video, the TTS screen reader functionality embedded in the smartphone, does allow John to follow the video.

And if he needs more details, he activates through his voice the audio description channel being able to visualise how a scene looks like.

And all the above without having to pay anything extra, except buying the standard devices and subscribe to the required services, just like everybody else!



Personas are fictitious archetypes of real users. They do not correspond to particular users, but they do represent real people.

Whereas user profiles cover a range of characteristics, personas use specific characteristics.

In fact, the more specific a persona is, the more effective it is as a design tool.



Using personas during the design process can help achieving following goals:◦ As personas have a proper name and often include visually rich

information such as their picture, they put a name, a face, and real-life characteristics on users, and, as such, give the designers a very concrete item to work with. Concrete person is easier to focus on than more abstract user profiles or

just “all the available information about the users”. By focusing on personas, designer gains a (realistic) insight into the users.

◦ Personas form an ideal means of communication between the members of a project team. They assure that everyone involved in creating a new application has a reference to the same user.



ÆGIS Personas

ÆGIS targeted end-user group Relevant Personas

Visual impairments Gert, Märta, Nitesh, Paulina

Motor impairments Caroline, Jane, Mikel, Peter, Ramin

Cognitive impairments or learning difficulties

Adam, Peter, Wayne

Hearing impairments Edward, Emma, Tomasa

Speech/communication impairments Carlos, Emma, Jane, Wayne

Experts Benoit

Developers Clyde



ÆGIS Persona Addressed Use Cases

Adam Ljung (learning disability)

Graphic Symbol Support for facilitated text comprehension and production in OpenOffice.org(based on Concept Coding Framework (CCF) technology, also used in A4.6.3).

Mobile as an Augmentative and Alternative Communication (AAC) device for severe motor and/or speech impairments .

Symbol-based Augmentative and Alternative Communication (AAC) system for mobile devices for direct person-to-person (face-to-face) communication.

Augmentative and Alternative Communication (AAC) for instant and text messaging (IM/SMS) on mobile devices.

Accessible messengering applications for mobile devices. Accessible phone dialer and contact manager for mobile

devices.

Benoit Dupré (expert) Accessibility Checking for ODF Full DAISY book creation in OpenOffice.org. Accessible Mobile Phone for the blind. Mobile as an Augmentative and Alternative Communication

(AAC) device for severe motor and/or speech impairments. Generating Accessible PDF from OpenOffice.org.



Use Cases are expected to constitute the main guide for the project phases to follow;design and development and finally evaluation phases.

The Use Cases will be further elaborated to specific application scenarios that will orient the evaluation to take place in ÆGIS in three iterative phases and across 4 Pilot sites (Belgium, Spain, Sweden and in the UK).

All aforementioned core elements are public and can be downloaded from the project web site (http://www.aegis-project.eu), while are all considered working documents that may undergo several updates and revisions, following the progress of the project as well as the evolution noticed in the open source accessibility community.

Download - 3 Use Cases towards All Inclusive Mainstream ICT

Top Related