Veritas D2.4.1

Accessible and Assistive ICT
VERITAS
Virtual and Augmented Environments and Realistic User Interactions To achieve

Embedded Accessibility DesignS
247765
Simulation models for the workplace design

scenario
Deliverable No. D2.4.1

SubProject No. SP2 SubProject Title Innovative VR models,
tools and simulation
environments
Workpackage W2.4 Workpackage Title Workplace and
No. Collaborative Tools
Activity No. A2.4.2 Activity Title Generation of simulation
models for workplace
design
Authors Hypertech, Byte
Status F (Final)
Dissemination Level Pu (Public)
File Name: VERITAS_D2.4.1_final-alt text
Project start date and duration 01 January 2010, 48 Months
VERITAS D2.4.1 PU Grant Agreement # 247765
Version History table

Version Dates and comments
no.
1.0 November 2011: First draft version produced (Hypertech)
1.1 November 2011: Collaborative Tools sections included (Byte)
1.2 December 2011: Revision and improvements performed; Document

sent for peer review (Hypertech)
2.0 December 2011: Final version taking into account peer review report
(Hypertech)
December 2011 3 Hypertech

Table of Contents
Version History table ............................................................................................... 3
Table of Contents ..................................................................................................... 4
List of Figures .......................................................................................................... 9
List of Tables .......................................................................................................... 10
Abbreviations list ................................................................................................... 11
Executive Summary ............................................................................................... 12
1 Introduction ..................................................................................................... 13
2 UCD, Guidelines and Requirements in the Workplace industry ................. 14
2.1 Overview ............................................................................................... 14
2.2 UCD in Workplace Design .................................................................... 14
2.2.1 Lighting and Sound ........................................................................................................ 15
2.2.2 Furniture and Storage .................................................................................................... 16
2.2.3 Visual Display Unit (VDU).............................................................................................. 16
2.2.4 Document Holders ......................................................................................................... 17
2.2.5 Keyboards...................................................................................................................... 17
2.2.6 Mouse Controls ............................................................................................................. 18
2.2.7 Chairs ............................................................................................................................ 18
2.2.8 Desks ............................................................................................................................. 19
2.2.9 Equipment positioning on desktop ................................................................................ 19
2.2.10 Phones........................................................................................................................... 20
2.2.11 Office Accessories and Non Routine Processes ........................................................... 20
2.3 UCD in Collaborative tools .................................................................... 21
2.3.1 A survey of preferences among office workers with disabilities .................................... 22
2.4 Buildings accessibility guidelines / standards ....................................... 25
2.4.1 Horizontal circulation ..................................................................................................... 26
2.4.2 Vertical circulation ......................................................................................................... 29
2.4.3 Doors ............................................................................................................................. 31
2.4.4 Devices and controls ..................................................................................................... 33
2.4.5 Reach ranges ................................................................................................................ 34
2.5 Guidelines and standards for software accessibility.............................. 36
2.5.1 The Trace Research & Development Center guidelines ............................................... 36
2.5.2 The Section 508 standards............................................................................................ 39
2.6 Design guidelines for collaborative tools ............................................... 40
2.7 Accessibility guidelines for collaborative tools ...................................... 41
2.7.1 Guidelines for Developing Accessible Asynchronous Communication and Collaboration
Tools 41
2.7.2 Guidelines for Developing Accessible Synchronous Communication and Collaboration
Tools 43
3 Use case analysis ........................................................................................... 45
3.1 Workplace Design Use Case Scenarios ............................................... 45
3.2 Collaborative Tools Use Case Scenarios.............................................. 47
4 Simulation models .......................................................................................... 49
4.1 General approach ................................................................................. 49
4.1.1 Definition of task. ........................................................................................................... 50

4.1.2 Definition of subtask. ..................................................................................................... 50

4.1.3 Definition of Primitive task. ............................................................................................ 51
4.2 Workplace Design applications ............................................................. 54
4.2.1 Overall simulation task table.......................................................................................... 54
4.2.2 Identification of object parameters ................................................................................ 60
4.2.3 Definition of success criteria for each task .................................................................... 63
4.2.4 Generation of UsiXML files ............................................................................................ 71
4.3 Collaborative Tools applications ........................................................... 76
4.3.1 Overall simulation task table.......................................................................................... 76
4.3.2 Identification of object parameters ................................................................................ 84
4.3.3 Definition of success criteria for each task .................................................................... 90
4.3.4 Generation of UsiXML files .......................................................................................... 101
4.4 Integration of VERITAS tools .............................................................. 104
4.4.1 VERITAS tools for Workplace Design ......................................................................... 104
4.4.2 VERITAS tools for Collaborative Tools ....................................................................... 105
5 Conclusions................................................................................................... 108
6 References ..................................................................................................... 109
7 ANNEX Simulation/Task/Multimodal Interaction models in UsiXML ........ 111
7.1 Workplace Design Simulation Models................................................. 111
7.1.1 Locate and enter main entrance .................................................................................. 111
7.1.2 Using office Equipment................................................................................................ 112
7.1.3 Print a document and classify it in a dossier on the closet .......................................... 113
7.2 Workplace Design Task Models ......................................................... 114
7.2.1 Locate and enter main entrance .................................................................................. 114
7.2.2 Locate and approach lift .............................................................................................. 115
7.2.3 Locate and push call button......................................................................................... 115
7.2.4 Get aware of open doors and enter lift ........................................................................ 116
nd
7.2.5 Locate and push 2 floor button ................................................................................. 116
7.2.6 Get aware of open doors and exit lift ........................................................................... 117
7.2.7 Locate and enter office ................................................................................................ 118
7.2.8 Locate and walk to office chair .................................................................................... 119
7.2.9 Adjust and sit on chair ................................................................................................. 119
7.2.10 Opening drawer ........................................................................................................... 120
7.2.11 Locate power button and turn on PC ........................................................................... 121
7.2.12 Activating computer screen ......................................................................................... 122
7.2.13 Using devices .............................................................................................................. 123
7.2.14 Go to storage area ....................................................................................................... 124
7.2.15 Get paper ..................................................................................................................... 124
7.2.16 Feed paper into printing tray ....................................................................................... 125
7.2.17 Get printed document from printer .............................................................................. 126
7.2.18 Get a dossier from shelf .............................................................................................. 126
7.2.19 Classify document in dossier ....................................................................................... 127
7.2.20 Store dossier on shelf .................................................................................................. 127
7.3 Workplace Design Multimodal Interaction Models .............................. 128
7.3.1 Locate main entrance .................................................................................................. 128
7.3.2 Walk to main entrance ................................................................................................. 128
7.3.3 Locate door handle ...................................................................................................... 129
7.3.4 Reach door handle ...................................................................................................... 129
7.3.5 Grasp door handle ....................................................................................................... 130
7.3.6 Push door handle ........................................................................................................ 130
7.3.7 Push door .................................................................................................................... 131
7.3.8 Release door handle ................................................................................................... 131
7.3.9 Locate lift doors ........................................................................................................... 132
7.3.10 Walk to lift doors .......................................................................................................... 132

7.3.11 Locate call button ........................................................................................................ 133

7.3.12 Reach call button ......................................................................................................... 133
7.3.13 Push call button ........................................................................................................... 134
7.3.14 Locate open lift doors .................................................................................................. 134
7.3.15 Locate open lift doors .................................................................................................. 135
7.3.16 Walk inside lift .............................................................................................................. 135
nd
7.3.17 Locate 2 floor button ................................................................................................. 136
nd
7.3.18 Reach 2 floor button .................................................................................................. 136
nd
7.3.19 Push 2 floor button .................................................................................................... 137
7.3.20 Walk outside lift ........................................................................................................... 137
7.3.21 Locate office door ........................................................................................................ 138
7.3.22 Walk to office door ....................................................................................................... 138
7.3.23 Locate door handle ...................................................................................................... 139
7.3.24 Reach door handle ...................................................................................................... 139
7.3.27 Push door handle ........................................................................................................ 141
7.3.28 Push door .................................................................................................................... 141
7.3.29 Release door handle ................................................................................................... 141
7.3.30 Locate chair ................................................................................................................. 142
7.3.31 Walk to chair ................................................................................................................ 142
7.3.32 Reach chair ................................................................................................................. 143
7.3.33 Push chair .................................................................................................................... 143
7.3.34 Sit on chair ................................................................................................................... 144
7.3.35 Locate drawer .............................................................................................................. 144
7.3.36 Reach drawer .............................................................................................................. 145
7.3.37 Grasp drawer handle ................................................................................................... 145
7.3.38 Pull drawer handle ....................................................................................................... 146
7.3.39 Locate power button .................................................................................................... 146
7.3.40 Reach power button .................................................................................................... 147
7.3.41 Push power button ....................................................................................................... 147
7.3.42 Locate computer screen .............................................................................................. 148
7.3.43 Reach computer screen .............................................................................................. 148
7.3.44 Grasp computer screen ............................................................................................... 149
7.3.45 Pull computer screen closer ........................................................................................ 149
7.3.46 Push computer screen farther ..................................................................................... 150
7.3.47 Pull computer screen lower ......................................................................................... 150
7.3.48 Push computer screen higher ..................................................................................... 151
7.3.49 Locate device .............................................................................................................. 151
7.3.50 Reach device ............................................................................................................... 152
7.3.51 Grasp device ............................................................................................................... 152
7.3.52 Push device button ...................................................................................................... 153
7.3.53 Leave chair .................................................................................................................. 153
7.3.54 Locate storage area ..................................................................................................... 154
7.3.55 Walk to storage area ................................................................................................... 154
7.3.56 Locate stored paper ..................................................................................................... 155
7.3.57 Reach stored paper ..................................................................................................... 155
7.3.58 Grasp stored paper ...................................................................................................... 156
7.3.59 Locate printing tray ...................................................................................................... 156
7.3.60 Walk to printer area ..................................................................................................... 157
7.3.61 Reach tray ................................................................................................................... 157
7.3.62 Grasp tray .................................................................................................................... 158
7.3.63 Pull tray ........................................................................................................................ 158
7.3.64 Release paper in tray .................................................................................................. 159
7.3.65 Push tray...................................................................................................................... 159
7.3.66 Locate printer ............................................................................................................... 160
7.3.67 Reach printed document ............................................................................................. 160
7.3.68 Grasp printed document .............................................................................................. 161

7.3.69 Locate dossier ............................................................................................................. 161

7.3.70 Walk to dossier ............................................................................................................ 162
7.3.71 Reach dossier .............................................................................................................. 162
7.3.72 Grasp dossier .............................................................................................................. 163
7.3.73 Bring dossier down ...................................................................................................... 163
7.3.74 Open Dossier ............................................................................................................... 164
7.3.75 Release printed document in dossier .......................................................................... 164
7.3.76 Close dossier ............................................................................................................... 165
7.3.77 Locate shelf ................................................................................................................. 165
7.3.78 Walk to shelf ................................................................................................................ 166
7.3.79 Lift dossier to shelf ....................................................................................................... 166
7.4 Collaborative tools Simulation Models ................................................ 167
7.4.1 File upload and editing ................................................................................................ 167
7.4.2 Create Discussion ....................................................................................................... 168
7.4.3 Realise a teleconference ............................................................................................. 169
7.5 Collaborative tools Task Models ......................................................... 170
7.5.1 Select File Upload from menu ..................................................................................... 170
7.5.2 Select file to upload ..................................................................................................... 171
7.5.3 Locate and click Upload button .................................................................................. 171
7.5.4 Get aware of File uploaded message ........................................................................ 172
7.5.5 Select an uploaded file ................................................................................................ 172
7.5.6 Select Edit file from menu .......................................................................................... 173
7.5.7 Insert text in the file ..................................................................................................... 174
7.5.8 Locate and click Print button ...................................................................................... 175
7.5.9 Get aware of message Out of paper .......................................................................... 175
7.5.10 Select Create new discussion from menu ................................................................. 176
7.5.11 Insert title ..................................................................................................................... 177
7.5.12 Locate and click Post button ...................................................................................... 177
7.5.13 Get aware of Discussion created message ............................................................... 178
7.5.14 Select Post item from menu ....................................................................................... 179
7.5.15 Insert text ..................................................................................................................... 180
7.5.16 Get aware of Item posted message ........................................................................... 181
7.5.17 Locate and click Accept button .................................................................................. 181
7.5.18 Locate volume slider and adjust volume ..................................................................... 182
7.5.19 Communicate with other participants .......................................................................... 182
7.6 Collaborative tools Multimodal Interaction Models .............................. 183
7.6.1 Move Mouse ................................................................................................................ 183
7.6.2 Click Mouse Button ...................................................................................................... 183
7.6.3 Push Keyboard key ..................................................................................................... 184
7.6.4 Release Keyboard key ................................................................................................ 184
7.6.5 Locate file menu .......................................................................................................... 185
7.6.6 Locate upload file menu item....................................................................................... 185
7.6.7 Locate upload file name .............................................................................................. 186
7.6.8 Locate upload button ................................................................................................... 186
7.6.9 Locate file upload menu item....................................................................................... 187
7.6.10 Locate edit file menu ................................................................................................... 187
7.6.11 Locate inserted text ..................................................................................................... 188
7.6.12 Locate print button ....................................................................................................... 188
7.6.13 Locate message out of paper ...................................................................................... 189
7.6.14 Locate discussion menu .............................................................................................. 189
7.6.15 Locate create new discussion menu item ................................................................... 190
7.6.16 Locate title entry field ................................................................................................... 190
7.6.17 Locate post button ....................................................................................................... 191
7.6.18 Locate discussion created message ........................................................................... 191
7.6.19 Locate post item menu item ........................................................................................ 192
7.6.20 Locate text field ........................................................................................................... 192
7.6.21 Locate item posted message....................................................................................... 193

7.6.22 Locate accept button ................................................................................................... 193

7.6.23 Locate volume dialog box ............................................................................................ 194
7.6.24 Hear sound .................................................................................................................. 194
7.6.25 Speak to other participants .......................................................................................... 195

List of Figures
Figure 2-1: Common musculoskeletal disorders at office workstations .................... 14
Figure 2-2: Frequency of use of ICTs among undergraduate students per year ...... 22
Figure 2-3: Percentage of events per application area. ............................................ 22
Figure 2-4: Usage of collaborative tools among the sample ..................................... 23
Figure 2-5: Frequency of usage of collaborative tools among the sample ............... 24
Figure 2-6: Perceived usefulness of collaborative tools among the sample ............. 25
Figure 2-7: Minimum width according to intensity of use [ISO/DIS 21542] ............... 26
Figure 2-8: Clear Width at Turn [ADA 2010] ............................................................. 27
Figure 2-9: Space required for a 90o turn [ISO/DIS 21542] ...................................... 28
Figure 2-10: Space required for a 180o turn in a corridor [ISO/DIS 21542]............... 28
Figure 2-11: T-shaped turning space [ADA 2010] .................................................... 29
Figure 2-12: Ramp landings [ADA 2010] ................................................................. 30
Figure 2-13: Handrail Height [ADA 2010] ................................................................ 30
Figure 2-14: Handrail Non-Circular Cross Section [ADA 2010] ............................... 31
Figure 2-15: Clear Width of Doorways [ADA 2010] ................................................. 31
Figure 2-16: Clear opening of swinging and sliding doors [ISO/DIS 21542] ............ 32
Figure 2-17: Heights of switches, socket outlets, reading controls and controls on a
horizontal surface [ISO/DIS 21542] ................................................................... 34
Figure 2-18: Unobstructed Forward Reach [ADA 2010] ........................................... 34
Figure 2-19: Obstructed High Forward Reach [ADA 2010] ...................................... 35
Figure 2-20: Unobstructed Side Reach [ADA 2010] ................................................. 35
Figure 2-21: Obstructed High Side Reach [ADA 2010] ............................................ 35
Figure 3-1: Use case analysis process for 3D scenarios.......................................... 45
Figure 3-2: Use case analysis process for 2D scenarios.......................................... 47
Figure 4-1: Task representation ............................................................................... 50
Figure 4-2: Subtask representation .......................................................................... 51
Figure 4-3: Primitive task and related attributes ....................................................... 52
Figure 4-4: Generation of overall simulation task table ............................................ 52
Figure 4-5: Generation of UsiXML files .................................................................... 53
Figure 4-6: Simulation model tree generated from UsiXML for UC4.1.x.1 ................ 72
Figure 4-8 Simulation model tree generated from UsiXML for UC4.1.x.2................. 73
Figure 4-10: Example of a Task model definition in UsiXML for the Opening Drawer
task .................................................................................................................... 74
Figure 4-11: Example of a Multimodal Interaction model definition in UsiXML for the
Move_to_chair primitive task ........................................................................... 75
Figure 4-12: Simulation model tree generated from UsiXML for UC4.2.1 .............. 101

Figure 4-15: Task model tree generated from UsiXML for the Locate and click post
button complex task........................................................................................ 103
Figure 4-16: Multimodal Interaction Model tree generated from UsiXML for the
Locate post button primitive task ................................................................. 103
Figure 4-17: The Veritas Simulation Editor tool (Interaction and Simulation Model
Adaptor) ........................................................................................................... 105
Figure 4-18: Early version of the Veritas GUI Interaction Adaptor .......................... 107
List of Tables
Table 2-1: Maneuvering Clearances at Manual Swinging Doors and Gates [ADA
2010].................................................................................................................. 31
Table 2-2: Maneuvering Clearances at Doorways without Doors or Gates, Manual
Sliding Doors, and Manual Folding Doors [ADA 2010] ..................................... 32
Table 4-1: Overall simulation task table for Workplace Design applications ............ 54
Table 4-2: Object parameters for the Workplace Design applications ...................... 60
Table 4-3: Task success criteria for the Workplace Design simulation scenarios .... 63
Table 4-4: Overall simulation task table for Collaborative Tools use cases.............. 76
Table 4-5: Object parameter table for Workplace scenarios .................................... 84
Table 4-6: Task success criteria for the Collaborative tools simulation scenarios .... 90

Abbreviations list
Abbreviation Explanation
A Activity
API Application Programming Interface
D Deliverable
DOF Degree of freedom
ICT Information and Communication Technology
ID Internal Deliverable
DoW Description of Work
PTW Powered Two Wheeler
SP Subproject
UCD User Centred design
WP Work package

Executive Summary
This deliverable describes the work performed under activities A2.4.1 and A2.4.2 for the
generation of simulation models for the Workplace design and the Collaborative tools design
application areas.
Starting from results of task analysis and use cases description performed in WP1.7 and the
virtual user model files generated by the VERITAS model platform (WP1.6), the
requirements of end-users and of technology providers for ergonomic design with respect to
humans with limited functionalities were analysed first. Then this analysis was used to derive
specific tasks to be performed in simulation scenarios that follow the use cases. The tasks
are in turn analysed to describe the interactions, objects, success criteria and thresholds that
fully describe the simulation modeling. Finally, the simulation models are formulated into
UsiXML form, in order to abstractly describe the simulation models in a form that can be then
adapted by the Veritas Tools in order to match specific designs and users.
We started the work to create the simulation models by first performing a study of the
workplace (workplace design and collaborative tools) needs, requirements, guidelines and
standards which govern usability and accessibility in the workplace domain. The work
carried out during this activity revolved around literature research, questionnaires and expert
interviews, in order to provide a compendium of requirements with regards to accessibility
assessment in the workplace.
Based, on the Use Cases declared in D1.7.1 and analysed in multidimensional tasks in
D1.7.2, we derived the specific simulation models in table forms, from which, the resulting
UsiXML files were generated using the IdealXML tool. In total, 6 Simulation Models were
created, 3 for workplace design and 3 for Collaborative tools sub-domains, while also 39
task models (20 for Workplace and 19 for Collaborative tools) and 98 Multimodal Interaction
Models (72 in the Workplace and 26 in the Collaborative tools) were created and the
corresponding UsiXML files were generated.
Finally, we composed an overview on the integration of Simulation models to the Veritas

tools is provided that explains how these simulation models will be adapted into interactive
simulation scenarios. These tools are presented together with a description of the
methodologies and related software for human physical modeling which are expected to be
used for the simulation of the functional impairments.

1 Introduction
In the last 20 years, the workplace environment has gradually begun being the prominent
inclusive area of modern day society for people with impairments. New guidelines and
standards, as well as EU directives and laws have been introduced that all people,
regardless of impairments have access to employment, which means that buildings, facilities
and equipment that are used for workplace applications need to fulfil accessibility criteria
before they are applicable in the workplace environment.
To that effect, this document aims to compile the key requirements in workplace design
applications and collaborative tools applications, and using these requirements derive
simulation models from the workplace use cases defined in D1.7.1. For these simulation
models, object parameters and simulation success criterias and thresholds are produced.
Then, in the next part of the document, the UsiXML files, describing these simulation models
are described and examples included, while finally, an introduction to the next steps for
accessibility simulation in the workplace domain using the tools available within the Veritas
project is submitted.

2 UCD, Guidelines and Requirements in the

Workplace industry
2.1 Overview
User Centered Design in the Workplace industry covers a wide range of guidelines, best
practices, and standards that facilitate ergonomics, accessibility and usability, both with
regard to the physical space, equipment , furniture and devices in an office environment, as
well as with to ICT applications and user interface elements.
In the following sections we will describe the main aspects of UCD in workplace design and
ICT applications design and development.
2.2 UCD in Workplace Design

A lot of research has been done on the ergonomic design of the office workspace and on the
use of visual display terminals (VDU), and there are a lot of guidelines and standards
available for the ergonomic design of office workplaces. The main issue to be tackled is the
posture that will be adopted by the office worker, which has to be appropriate. Research
shows that sitting for prolonged periods of time results in discomfort, aches and even
irreversible injuries. Other issues encountered by office workers are the neck aches and the
dry eye syndrome, which are mainly caused by the wrong height of work surface. Despite
the fact that most modern office seats are manufactured in accordance to the ergonomic
guidelines, the poor users knowledge on healthy sitting is still an issue causing problems
among office workers [Vitalis et al 2000]. Therefore, the correct body posture must be
always maintained and the workers must be adequately informed.
Figure 2-1: Common musculoskeletal disorders at office workstations
The European Directive 89/654/EEC deals with the minimum safety and health requirements
for workplaces. The Directive 90/270/EEC sets out minimum safety and health requirements
for work with display screen equipment, the environment and the operator/computer

interface. The standard prEN-1005-4: Safety of machinery. Human physical performance

provides guidance for designing machinery and its components, helping to assess and
control the health risks that are due to machine-related posture and movement.
The following ISO standards are relevant:
EN ISO 9241: Ergonomic requirements for office work with visual display terminals
(VDTs)
EN ISO 9241-4: Ergonomic requirements for office work with visual display terminals
(VDTs). Keyboard requirements.
(VDTs). Workstation layout and postural requirements
(VDTs). Requirements for non-keyboard input devices.
The following standards from Australia are very detailed and relevant:
Australian Standard AS 1680, Standard AS 1680.2.2 - 1994 Interior lighting Part 2.2:
Office and screen-based tasks
Australian Standard 3590.2-1990 Screen based Workstations
The ADA 2010 Standards for Accessible Design include also some references to tables
and work surfaces.
Below, we present a list of guidelines referring to the physical placement of equipment in the
office environment and to ambient environment. They have been compiled mainly from a list
of guidelines by the European Agency for Safety and Health and Work and by the University
of Sydney.
2.2.1 Lighting and Sound

"Ordinary" visual tasks should be in range 300 to 400 lux [320 lux (task) and 160 lux
(Background)] [UTS guidelines].
For more demanding visual tasks, including proof reading and working from poor
quality photocopies, 600 lux is suitable [UTS guidelines].
Older workers may require stronger lighting [UTS guidelines].
Glare should be minimized [UTS guidelines].
Illumination should be even between adjacent areas [UTS guidelines].

The recommended decibel range for office work is 55 to 65 dBA [UTS guidelines].
2.2.2 Furniture and Storage

The maximum acceptable load to be lifted in the seated position is 4.5 kg [UTS
guidelines].
All pieces of furniture should be placed so that workers do not have to twist or reach
while carrying items weighing over 4 kgs. It is advisable to have a secondary work
space outside the maximum reach area, so that people have to stand up and move
around to reach items that should not be lifted whilst sitting [UTS guidelines].
Workers should not over-stretch in order to reach objects located beyond maximum
reach [UTS guidelines].
Heavy items should be stored on shelves around waist level. Frequently used items
should not be stored near floor level or above shoulder height [UTS guidelines].
Workers should not have to repeatedly use poor spinal postures when sideways
reaching and leaning down to a drawer unit [UTS guidelines].
Workers should avoid excessive bending or reaching to gather or store items on

shelves [UTS guidelines].
2.2.3 Visual Display Unit (VDU)

The orientation of the VDU should guarantee a normal body and head posture and
ease of viewing [UTS guidelines]. The chin should be tucked in towards the chest
and aligned with the spine rather than poking forward or upwards (EASHW
guidelines).
The VDU should be rotatable and tiltable, to be easily adjustable [UTS guidelines].
The VDU should be placed at an appropriate height above the work surface where
the top line of text is just below eye level (15 degrees) [UTS guidelines].
For people wearing glasses, the VDU should be positioned low enough so that they
do not have to raise their chin to Locate at the screen [EASHW and UTS guidelines].
The VDU should be positioned at a comfortable reading distance from the operator
(350mm to 750mm) (EASHW guidelines).
For workers wearing glasses, the monitor distance from the user should match the
focal length of the spectacles [UTS guidelines].
No more than six colours should be simultaneously displayed [UTS guidelines].

Alternative light control options should be investigated to reduce glare from the work
environment [UTS guidelines].
2.2.4 Document Holders

A document holder should be used, so that the source material is not positioned flat
on the desk or in a position to the extreme side of the monitor. Reading a document
at such angles requires prolonged bending and twisting of the neck and therefore
generates greater prolonged muscle tension [UTS guidelines].
The document holders should be placed at a comfortable viewing distance in line

with the screen, should be stable and free from vibration [UTS guidelines].
2.2.5 Keyboards
The keyboard should be separate from the screen to allow both of them to be
independently adjusted [UTS guidelines].
The keyboard design (either split, compact, "Internet" or "ergonomic") should be

selected according to the best match to the hand size, finger reach and keying style
of the users [UTS guidelines].
The primary part of the keyboard to be used (i.e. alpha or numeric), should be
directly aligned in front of the body [UTS guidelines].
The monitor and keyboard should be aligned and directly in front of the worker so
that they do not twist to reach the keys (EASHW guidelines).
The keyboard should be located in close proximity to the body to avoid over reaching
to key (EASHW guidelines). The worker should not have to overstretch the fingers to
reach shift and function keys [UTS guidelines].
The shoulders should be relaxed when the hands are resting on the keys with the
upper arms hanging naturally and the lower arm at approximately 90 degrees
(EASHW guidelines).
The wrists should be straight and in line with the forearm whilst keying or using the
mouse, to avoid excessive bending to the side or upwards (EASHW guidelines).
Laptop screens and keyboards should not be used for prolonged periods, as they
cannot be optimally adjusted. If this cannot be avoided, it is advisable to use a
standard keyboard and mouse connected to the laptop and to place the laptop
screen so that the top line of text is just below the eye line [UTS guidelines].

2.2.6 Mouse Controls

The slope and shape of the mouse should allow the wrist to be aligned with the
forearm without an angle to either side [UTS guidelines].
The incline of the mouse should guarantee minimal bending up of the wrist [UTS
guidelines].
The mouse should be at the same level and as close as possible to the keyboard to
avoid stretching the arm out to the side or across the desk (EASHW guidelines).
Controls that allow a variety of finger movements instead of holding a position on a

button should be preferred, as they allow better blood flow to the muscles and
prevent fatigue [UTS guidelines]. A scroll wheel may be employed, for example
during web searches [UTS guidelines].
If extensive mouse use is required, it is advisable to provide for easy alternation

between the left and right hand [UTS guidelines].
The possibility to adjust mouse speed via the control panel may reduce the need to
maintain a tense grip to control excess movement [UTS guidelines].
2.2.7 Chairs
The chair should maintain the curves of the spine by providing adequate support to
the lower back curve. The backrest should be sufficiently padded and contoured to fit
and support the small of the back [UTS guidelines].
A chair should be adjustable in height whilst seated and should be stable under
normal operating conditions at all heights. It should have backrest adjustable in
height and tilt whilst seated on the chair and should allow close access to the desk
[EASHW and UTS guidelines]. A chair should allow alternation between a semi-
reclined and upright posture throughout the day, e.g. when on the phone [UTS
guidelines].
The backrest width should not impede keying posture by causing the arms to be held
out to the side [UTS guidelines].
Chairs should move easily across floor surface, to avoid extra strain on the upper
limbs in pulling and pushing the worker towards or away from the desk [UTS
guidelines].
Glides are recommended if chairs are on linoleum or similar floors, as castors may
present a hazard by rolling too freely. Lockable castors may be used on linoleum
floors. These are free rolling when there is no weight on the chair, and lock in
position when weight is applied [UTS guidelines].

If the feet are not flat on the floor when sitting, then a stable footrest should be used
(EASHW guidelines).
2.2.8 Desks
The desk top size should have an adequate width and depth to allow for correct
posture at the keyboard [UTS guidelines]. Elbows should be level with, or slightly
higher than keyboard while typing (EASHW guidelines).
The desktop should easily accommodate all tasks and there should be sufficient
space for source documents. The following are the minimum desk top sizes: for
mixed tasks e.g. computer and clerical - 1500 X 900mm, for single tasks e.g.
computer only - 1200 X 900mm [EASHW and UTS guidelines].
If the height of keyboard desks is fixed this should be in the range of 680 mm to
710mm (Australian Standard 3590.2-1990). A higher work area should be used for
layout, sorting and collating of documents (Australian Standard 3590.2-1990).
The tops of tables should be in the height 660 to 760 mm above the ground. The tops
of work surfaces should be in the height 710 to 865 mm above the ground [ADA
2010].
The desk top and supporting frame should have a maximum thickness of 30mm to
allow for adequate leg clearance [UTS guidelines].
The underside of the desk should be free from obstruction to the knees through items
such as under desk CPU holders and drawer units. The minimum clearances for legs
to allow close access to work tasks are: minimum depth 550mm, minimum width
800mm (EASHW guidelines and Australian Standard 3590.2-1990).
2.2.9 Equipment positioning on desktop

The items most frequently handled should be within easy reach whilst sitting and
under 4kgs [EASHW and UTS guidelines].
The less frequently used equipment and materials should be placed within a distance
reached by the outstretched arm [UTS guidelines].
The position of source documents should be in line with or close to the monitor and
around eye level to avoid excessive twisting or bending of neck (EASHW guidelines).

2.2.10 Phones
Telephones should be positioned on the non-dominant side to allow pick up and
holding in the non-dominant hand while writing or keying with the dominant hand
[UTS guidelines].
When phone is frequently answered while keying or writing, a phone head set should
be used [UTS guidelines].
2.2.11 Office Accessories and Non Routine Processes

Non routine processes involving prolonged tasks such as stapling, hole punching,
flipping through heavy lever arch files, guillotining, handling of heavy reference texts
and large mail outs should only be performed for short intervals, at a relaxed pace
[UTS guidelines].

2.3 UCD in Collaborative tools

Collaborative software for the office includes tools allowing the collaboration through the
internet of persons who are not at the same physical location. Such tools for the office
environment may range from simple email applications and threaded message boards, to
chat and instant messaging packages, calendars, document repository and file or application
sharing packages up to web and video conferencing software. In general these tools may be
distinguished in real-time or synchronous applications, like the instant messaging or web /
video conferencing and asynchronous applications like the email, forums and newsgroups.
Research has shown that people with disabilities are less likely to live in households with
computers, are less likely to use computers and are less likely to be online. However, once
we control for socio-economic background, we find that people with hearing disabilities and
those who have limited walking ability are not less likely to be Internet users [Dobransky,
Hargittai, 2006]. Moreover, when people with disabilities do use collaborative online tools for
social discource and work collaboration ICT tools can provide a beeter medium for social
inclusion [Soderstrom, 2009]. [Lynch, 2006] performed a relative survey among
undergraduate information systems students. They were asked how often they were using
several types of technologies, and the answers were coded in the following scale: 5 (lots,
every day), 4 (few times a week), 3 (maybe once a week), 2 (a few times a month), 1
(rarely), 0 (never). The use of email was the most frequently used from the given list. The
synchronous text chat and the asynchronous chat followed, but daily use was reported for
them too. Only the synchronous video/audio chat was less used, this could be due to a
number of reasons, such as, the non-availability of hardware to interact with users, and the
relative small number of users of the technology.

Figure 2-2: Frequency of use of ICTs among undergraduate students per year
According to [Wainhouse research, 2008] the usage of audio, video, and web conferencing
is growing significantly. More precisely, the number of bridged audio conferencing minutes
increased by 55% worldwide between 2006 and 2008 approaching nearly 60 billion minutes.
The number of named end users for premise-based web conferencing solutions increased
by 48% during the period to reach 31 million. The total number of business video endpoints
sold increased by 43% to 235,000.
Webinar Success performed an online survey in 2008 to estimate web conferencing usage
characteristics. 13 web conferencing providers participated, 5 of them representing global
usage. The results of this survey are shown below and although they are not representative
of the total market, they show the size of use.
Average
Collaborative
Employee Comm.
Financial/IR
Marketing/PR
Press/Analyst
Sales
Training
Other
0.0 5.0 10.0 15.0 20.0 25.0 30.0
Figure 2-3: Percentage of events per application area.
2.3.1 A survey of preferences among office workers with disabilities

In order to identify the preferences of workers with disabilities regarding collaborative tools, a
questionnaire survey has been performed, using the questionnaire shown in the annex. This
questionnaire has been made available online at http://veritas-project.eu/2011/04/usage-of-
collaborative-tools-among-office-workers/ and at http://www.disabled.gr/lib/ . The
questionnaire has been also sent as hard copy to associations of disabled persons in
Greece.
A total of 33 completed questionnaires have been collected. 16 of the respondents were

male and 17 female and their mean age was 35 years. All of them were office workers, and
their occupations cover quite some specialties, as shown below.

Accountant 5
Cashier 2
Communication Manager 1
Economist 2
Engineer 10
Lawyer 2
Psychologist 1
Secretary 8
Salesperson 1
Software developer 1
4 persons declared that they are novice PC users, 20 standard PC users and 9 expert PC
users. 14 persons had a motor impairment, 13 a visual impairment and 6 a hearing
impairment. Mobility aids used are wheelchairs and walking sticks. Assistive devices used
are: Speech-to-text software, special trackball, built-in-sticky keys for keyboard.
The usage of the four collaborative tools categories surveyed is shown below. The email is
the tool that is being used the most and the web conferencing the least. All the respondents
stated that they are using email, 20 stated that they are using an instant messenger
application, 17 a document repository application and 14 a web conferencing application.
35
30
Numbe rof responses
25
20
15 Yes
No
10
0
Instant Email Document Web
messenger repository conferencing
Figure 2-4: Usage of collaborative tools among the sample
As regards the frequency of use of the collaborative tools, again the email is the most
frequently used, as 24 people say that they use it every day, 4 people that they use it 2-3

times a week and only 5 people say that they use it rarely. The document repository is used
quite often, since 17 people say that they use it every day, but 16 say that they never use
such an application. Instant messenger is also quite often used, 11 people use it every day,
2 once a week, 7 rarely and 13 never. The less often used tool among the respondents is
the web conferencing application, since only 1 person stated that it is used very day, 11
people a few times a month, 2 rarely and 19 never.
30
25
Numbe rof responses
20 Every day
2-3 times a week
15
Once a week
10 A few times a month
Rarely
5
Never
0
Figure 2-5: Frequency of usage of collaborative tools among the sample
The respondents were asked to rate the usefulness of the collaborative tools with 5 options,
Very useful (rated as +2), Rather useful (rated as +1), Indifferent (rated as 0), Rather not
useful (rated as -1) and Not useful at all (rated as -2). The weighted average of responses is
shown below. The ratings from people who stated that they never use a tool were not
considered, if given. The document repository applications are considered as the most
useful, followed by the email and the instant messenger, while the web conferencing got the
lower, although still very positive, rating.

2,50
2,00
Weigthed average
1,50
1,00
0,50
0,00
Figure 2-6: Perceived usefulness of collaborative tools among the sample
Unfortunately, we got very few responses on problems encountered when using such tools
and on ideas for their improvement. A lot of people responded that they do not face any
problem. We got few problems mentioned specifically for the web conferencing, which refer
to video connectivity,
According to the above findings, the tools that are most often used by the users and which
should be considered by VERITAS are the email and the document repository application,
while a teleconferencing application could also be given a medium priority.
2.4 Buildings accessibility guidelines / standards

The most detailed instructions are given in the ISO/DIS 21542 Building construction --
Accessibility and usability of the built environment and on the ADA 2010 Standards for
Accessible Design. The most relevant guidelines from these documents are summarized
below.

2.4.1 Horizontal circulation

All floor and ground surfaces must be stable, firm and slip resistant. Carpets should be
avoided, as they may increase the roll resistance of a wheelchair [ADA 2010].
The main horizontal circulation design should be level, without steps. If differences in level
cannot be avoided, ramps, lifts or platform lifts should be provided [ISO/DIS 21542]. The
[ADA 2010] standards further specify that changes in level up to 6.4 mm can be vertical,
from 6.4 mm up to 13 mm they should be beveled with a slope not steeper than 1:2, over 13
mm they should be ramped.
The running slope of walking surfaces should not be steeper than 1:20. The cross slope of
walking surfaces should not be steeper than 1:48. [ADA 2010].
According to [ADA 2010] the clear width of walking surfaces should be 915 mm and can be
reduced to 815 mm for a length of 610 mm if the reduced width segments are separated by
segments that are 1220 mm long and 915 mm wide. According to [ISO/DIS 21542] the
minimum clear width of passages should be 1200 mm, exclusive of handrails and any other
projections, while the minimum requirements increase according to intensity of use as shown
below.
Figure 2-7: Minimum width according to intensity of use [ISO/DIS 21542]
Objects with leading edges more than 685 mm and not more than 2030 mm above the finish
floor or ground should not protrude more than 100 mm maximum into the circulation path.

Handrails can protrude 115 mm maximum. [ADA 2010]. The clear width between handrails
should be 915 mm minimum. [ADA 2010]
The minimum clear height of corridors should be 2100 mm according to [ISO/DIS 21542]
and 2030 mm according to [ADA 2010]. [ADA 2010] further specify that if height is less, then
guardrails or other barriers should be provided at 685 mm maximum above the finish floor or
ground.
The [ADA 2010] specifications on the clear width at turns is shown below.
Figure 2-8: Clear Width at Turn [ADA 2010]
Junctions within a corridor should have a turning circle with a diameter of 1800 mm or more,
clear of any obstructions [ISO/DIS 21542].

o
Figure 2-9: Space required for a 90 turn [ISO/DIS 21542]
o
Figure 2-10: Space required for a 180 turn in a corridor [ISO/DIS 21542]
According to [ADA 2010], turning spaces can be circular with a diameter of at least 1525 mm
or T-shaped with a 1525 mm square with arms and base 915 mm wide. Each arm of the T
should be clear of obstructions 305 mm in each direction and the base should be clear of
obstructions 610 mm.

Figure 2-11: T-shaped turning space [ADA 2010]
To approach an element:
There should be clear floor or ground space of 760 x 1220 mm for either forward or
parallel approach [ADA 2010].
Toe clearance should be 635 to 430 x 760 mm wide under an element [ADA 2010].
Knee clearance should extend 635 mm deep maximum and 280 mm minimum under
an element at 230 mm above the finish floor or ground and 760 mm wide minimum
[ADA 2010].
2.4.2 Vertical circulation

According to [ISO/DIS 21542] internal ramps should be avoided and no series of ramps
should rise more than 2000 mm in total.
A gradient of 1:15 (6.6 cm pr m) is the maximum permissible according to [ISO/DIS 21542],

while [ADA 2010] specifies that ramp runs should have a running slope not steeper than
1:12 and cross slope should not be steeper than 1:48.
The minimum illumination at the top and bottom of the ramp should be 200 lux and 150 lux in
between the bottom and top [ISO/DIS 21542].
Ramp runs with a rise greater than 150 mm should have handrails. The floor or ground
surface of the ramp run or landing should extend 305 mm beyond the inside face of a
handrail [ADA 2010].

Figure 2-12: Ramp landings [ADA 2010]
[ISO/DIS 21542] requires the presence of handrails for stepped and sloped paths, ramps
and stairs and lift cars. [ADA 2010] specifies that handrails should be provided on both sides
of stairs and ramps and they should be continuous.
Handrails should extend horizontally for 305 mm minimum above the ramp landing or at the
top of a stair flight [ADA 2010].
The top of the gripping surfaces of handrails should be 865 mm minimum and 965 mm
maximum vertically above walking surfaces, stair nosings, and ramp surfaces. [ADA 2010]
Figure 2-13: Handrail Height [ADA 2010]
Handrail gripping surfaces with a circular cross section should have an outside diameter of
32 mm minimum and 51 mm maximum. Dimensions of non-circular cross sections are
shown below [ADA 2010].

Figure 2-14: Handrail Non-Circular Cross Section [ADA 2010]
2.4.3 Doors
[ADA 2010] specify that revolving doors, revolving gates, and turnstiles are not allowed in an
accessible route. The clear width of various door types and maneuvering clearance
according to [ADA 2010] is shown below.
Figure 2-15: Clear Width of Doorways [ADA 2010]
Type of Use Minimum Maneuvering Clearance

Door or Gate Perpendicular to Parallel to Doorway (beyond
Approach Direction
Side Doorway latch side unless noted)
From front Pull 1525 mm 455 mm
From front Push 1220 mm 0 mm
From hinge side Pull 1525 mm 915 mm
From hinge side Pull 1370 mm 1065 mm
From hinge side Push 1065 mm 560 mm
From latch side Pull 1220 mm 610 mm
From latch side Push 1065 mm 610 mm
Table 2-1: Maneuvering Clearances at Manual Swinging Doors and Gates [ADA 2010]

Minimum Maneuvering Clearance

Perpendicular Parallel to Doorway (beyond
Approach Direction
to Doorway stop/latch side unless noted)
From Front 1220 mm 0 mm
From side 1065 mm 0 mm
From pocket/hinge side 1065 mm 560 mm
From stop/latch side 1065 mm 610 mm
Table 2-2: Maneuvering Clearances at Doorways without Doors or Gates, Manual
Sliding Doors, and Manual Folding Doors [ADA 2010]
According to [ISO/DIS 21542] the clear width of doors should be minimum 800 mm, but 850
mm or more is recommended. The clear height of doors should be at least 2000 mm. A level
threshold is recommended, but where a raised threshold should exist, it should have a
maximum height of 15 mm, be beveled when higher than 5 mm and have visual contrast.
Figure 2-16: Clear opening of swinging and sliding doors [ISO/DIS 21542]
A maneuvering space of not less than 600 mm should be provided between the leading
edge of a door and a wall that is perpendicular to the doorway, 700 mm or more is
recommended. [ISO/DIS 21542]
[ADA 2010] recommend the use of doors that can be operated with a closed fist or a loose
grip and suggest to avoid systems that require simultaneous hand and finger movements.
[ADA 2010] specify that handles, pulls, latches, locks, and other operable parts on doors and
gates should be 865 mm minimum and 1220 mm maximum above the finish floor or ground.

When the operating force needed to open the door is greater than 30 N at 0 and 20 N at 30
opening, [ISO/DIS 21542] recommends an automatic opening door. In narrow spaces
sliding doors can be preferable. All automatic doors should be capable of remaining totally
open (at least 90 in the case of hinged doors) without manual support [ISO/DIS 21542].
Where a revolving door or turnstile is installed, a hinged or sliding door should be provided
as an alternative alongside. A revolving door should be large enough to allow safe passage
and accommodation for a wheelchair user and a companion [ISO/DIS 21542].
Where sliding doors are in the fully open position, operating hardware should be exposed
and usable from both sides [ADA 2010].
2.4.4 Devices and controls

Opening windows should not project into pedestrian areas below a height of 2100 mm and
they should be opened and closed with only one hand [ISO/DIS 21542]. [ADA 2010] suggest
that all operable parts should be operable with one hand and should not require tight
grasping, pinching, or twisting of the wrist.
[ISO/DIS 21542] specify that hardware shutters and switches for remote control should be
placed between 800 mm and 1000 mm above the floor and that the glazing should be no
higher than 1100 mm from the floor.
[ISO/DIS 21542] specifies that devices, controls etc. should be installed at an accessible
height for reaching and operating, between 400 mm and 1100 mm above floor level and
should be located a minimum of 600 mm from any internal corner, preferably 700 mm, while
control devices like radiator valves, fuse boxes, switches, push-buttons, intercoms, etc.,
should be installed between 800 mm 1 100 mm, and they should be located a minimum of
600 mm from any internal corner.
The force required to activate operable parts should be 22.2 N maximum [ADA 2010].
Control devices combined with text or figures should be positioned with the text and figures
or the whole control device placed at the angle of approximately 45 to the wall so that they
are easier to read and operate [ISO/DIS 21542].
Control devices placed on a horizontal surface should be placed at a height between 800
mm 900 mm and within 300 mm from the edge of the surface [ISO/DIS 21542].
Socket outlets, including those for telephone or TV, should be located not less than 400 mm
from the floor [ISO/DIS 21542].
Reading meters should be located between 1 200 mm and 1 400 mm from the floor.
[ISO/DIS 21542]

1 Fire alarm, call point, 2 Fire extinguisher, 3 Meter indicators, 4 Control devices, 5 Socket
outlets
Figure 2-17: Heights of switches, socket outlets, reading controls and controls on a horizontal
surface [ISO/DIS 21542]
2.4.5 Reach ranges

The reach ranges according to [ADA 2010] are given below.
Figure 2-18: Unobstructed Forward Reach [ADA 2010]

Figure 2-19: Obstructed High Forward Reach [ADA 2010]
Figure 2-20: Unobstructed Side Reach [ADA 2010]
Figure 2-21: Obstructed High Side Reach [ADA 2010]

2.5 Guidelines and standards for software accessibility

Several documents exist with guidelines for developing accessible software applications. A
very good and concise document is the set of guidelines issued by the Trace Research &
Development Center. Other relevant documents are the various standards for the
accessibility of electronic and information technology accessibility, issued in accordance to
the section 508 of the Rehabilitation Act and specific guidelines documents issued by
various developers in accordance to the previous guidelines and standards, for example the
Mac OS 8 Human Interface Guidelines by Apple, the Special Needs Systems Guidelines
by IBM and the Microsoft Windows Guidelines for Accessible Software Design.
2.5.1 The Trace Research & Development Center guidelines

The main guidelines given by the Trace Research & Development Center
(http://trace.wisc.edu/docs/software_guidelines/software.htm ) are highlighted below. These
guidelines have been developed taking into consideration that most accessibility software
packages work by attaching themselves to the operating system, thus these guidelines
attempt to guarantee the intuitive and easy operation of this accessibility software.
Writing to Screen
The standard text-drawing tools should be used, so that the access software can
monitor what is being written.
Text-drawing tools should be used to erase text, again to support screen reading
software.
Use of painted text should be avoided, because this is often stored as bit image and
cannot be read by screen reading routines.
Cursors, Pointers, Highlighting and Other Focus Techniques
System cursors should be used to facilitate their location by screen reading

programs.
The system cursor should be dragged along with any special cursor, which can be
invisible.
The cursor should be easy to locate, i.e. by momentarily changing it into some large
dark shape when a particular key combination is pressed.
Color and Contrast
When using color, the colors of standard elements from the system control panel
should be preferably used. If this is not possible, then colour blind people should be
considered and colour should be redundantly used maintaining high contrast.
A monochrome or gray-scale option should be provided, with sufficient contrast

between text and background.

Screen Format and Layout
The screen layout for menus, feedback messages, etc. should be consistent, to
facilitate people using screen enlargement or screen reading software.
Warnings, alerts and other popup messages should remain on screen until dismissed
by the user, else the user may not have time to read them.
Text should be arranged in single column layout, else screen readers should be
specifically programmed to handle them.
Labels should be attached to all screen controls and objects, to be available to

screen readers. Avoid icons embedded in text, as they can be missed by screen
readers.
Keyboard
Applications programs should use the Caps Lock, Scroll Lock, and Unlock keys
status flags in the system and keyboard or update them to agree with the program.
All aspects of the program, including menus, dialogs, palettes, etc., should be
accessible from the keyboard.
Key latching and other StickyKey functions should be avoided, as this may interfere
with system software.
Controls
Controls should be given meaningful names, as these are used by screen reading
software.
Standard controls should be preferred. Custom controls, if used, should be named

after the similar standard control, i.e. SpecialButton.
Fake buttons and hot spots should be avoided, because they cannot be easily
recognized by a screen reader.
Menus, Palettes and Toolbars
Standard system menu tools should be used, so that access software can read the
list of available commands.
Non-text menu items should be avoided, as they cannot be read by screen readers.
All menus should be accessible by the keyboard, to assist people who cannot use
the pointer.

Commands should be accessed alternatively either directly, which is easier for

people with physical and visual impairments, or via menus and layered dialogs,
which is easier for people with cognitive impairments.
Direct access to palettes and toolbars should be provided.
Toolbar icons should be individually drawn, so that they can be accessed by the
screen reader.
There should be a way to select an open window and bring it to the top.
Dialog Boxes
Buttons should be given meaningful names, as these are used by screen reading
software.
Buttons should be logically ordered, else they are disorienting.
Standard relationships between buttons and captions should be used, so that this is
predictable for people using screen readers.
Direct keyboard access to all aspects of the dialog should be provided, including
buttons, scroll windows, text entry fields, and pop-up menus.
Size of Objects
Most users will appreciate being able to adjust the font size as a way to reduce
eyestrain.
Cursors should be allowed to be substituted by larger or heavier lined cursors and

pointers.
The system's tools to determine monitor resolution parameters should be used.

Developers should bear in mind that future operating systems may allow users to
adjust line thickness to suit their needs.
Sound
All auditory information should be provided visually as well, to assist people with
hearing impairments.
A ShowSounds switch should be available. Manufacturers of operating systems are

also being encouraged to build captioning tools directly into the operating system to
facilitate the implementation of closed captioning by application programs.
The visual cue should be sufficient to attract the user's attention when viewed out of
the corner of the eye. For urgent messages, the whole screen may be flashing. In

other cases the window or its title bar might flash. Flashing should be 2 Hz or less,
else there is the risk for seizures in people with photosensitive epilepsy.
Synthetic or recorded speed should be accompanied by captions.
The user should be able to adjust the volume and turn sounds on or off.
Other
The user should be able to adjust time-responses or have a non-time-dependent

alternative method.
All user-settable parameters should be readable and settable via external software.
Extended ASCII character graphics rather than standard ASCII characters (such as
"***") should be used for drawing lines, making boxes, etc., because screen readers
read it as "asterisk, asterisk, asterisk,". Alphabetic characters should not be used to
draw boxes.
A highlighted bar should not be used to select items from a list, as it is much harder
for screen reading software. Instead, a small character may be carried up and down
a list.
2.5.2 The Section 508 standards

Some relevant highlights from the standards issued in accordance to the section 508 are
given below.
Functions should be executable from a keyboard.
Applications should not disrupt or disabled accessibility features.
A well-defined on-screen indication of the current focus should be available and

exposed to assistive technology.
Information about a user interface element (identity, operation and state) should be
available to assistive technology. If this element is an image, the information must
also be available in text.
The meaning associated to controls, status indicators, or other programmatic

elements should be consistent.
Textual information should be provided through operating system functions for

displaying text. The minimum information is text content, text input caret location, and
text attributes.

Applications should not override user selected contrast and colour selections and
other individual display attributes.
When animation is displayed, the information should be displayable in at least one

non-animated presentation mode at the option of the user.
Colour coding should not be used as the only means of conveying information,
indicating an action, prompting a response, or distinguishing a visual element.
When a product permits a user to adjust colour and contrast settings, a variety of
colour selections capable of producing a range of contrast levels should be provided.
Software should not use flashing or blinking text, objects, or other elements having a
flash or blink frequency greater than 2 Hz and lower than 55 Hz.
When electronic forms are used, the form should allow people using assistive
technology to access the information, field elements, and functionality required for
completion and submission of the form, including all directions and cues.
2.6 Design guidelines for collaborative tools

In general, a collaborative tool should not have a negative impact on organisation structure,
i.e. by trying to change existing structures, but it should effectively support the structure
already in place. The developers should first investigate the information communication
protocols and group relationships already in place and the system to be developed should
not enforce new protocols which contradict or make it difficult to maintain those normally in
place (Jones, 1995). System requirements imposed on the user may be minimized by
gathering appropriate and useful information about the collaboration from sources other than
the user (Cockburn and Jones, 1991).
The system should enhance existing computer based relationships, and encourage the
forging of new ones [Jones, 1995]. It should accommodate the changes in people's roles
and commitments with time [Jones, 1995].
Kraut et al (1988) have highlighted the importance of physical proximity in collaborative

tasks. Thus the system should try to provide the benefits of physical proximity (Jones, 1995).
Importance must be placed on improving the quality, efficacy and product of interactions
(Jones, 1995).
The system should support organisation, timetabling, structuring and recording of

discussions and meetings (Jones, 1995).
The system acceptance should be maximised by providing appropriate support for individual
work and providing transparent integration with support for group work (Cockburn and
Jones, 1991).

Inappropriate system imposed constraints on users should be minimized by avoiding rigid

embedded models and allowing the development of social protocols (Cockburn and Jones,
1991).
2.7 Accessibility guidelines for collaborative tools

The IMS Accessibility Project Group has issued a white paper on the development of
accessible learning applications, where they state the following generic guidelines:
The developed collaboration tool, and the real-time communication managed by the
tool, if this is the case, should be adequate for all browsers and should support
several input and output modalities and assistive technologies, to cover the needs of
all possible users.
Search functions and display options must be accessible to users of assistive

technologies.
Users should be able to easily configure the interface according to their individual
preferences.
Help files, including an orientation to the tool, are advisable.
More specific guidelines by IMS project per tool category are given in the following sections.
2.7.1 Guidelines for Developing Accessible Asynchronous Communication

and Collaboration Tools
2.7.1.1 Threaded Message Boards

To avoid creating barriers to the users due to the use of proprietary software or not-
standardised formats, the navigation system and message contents of tools that allow
posting of text messages, like discussion forums and bulletin boards, should be in standard
XHTML.
To guarantee accessibility of such tools, the navigation systems should have simple
framesets which should include title or name attributes, there should be an ALT text or
buttons to expand or contract threaded discussions, form fields should accommodate
keyboard navigation. Furthermore, the tab sequence when moving between elements on the
page should follow a certain and concise logic.
The following should be considered by developers to enhance the accessibility of threaded

message board applications for all users:
All actions should be completed using the keyboard.
Text should be used instead of images of text for navigation links or buttons.
Stylesheet attributes and text should be used to create attractive form buttons
instead of using images.

Bypass links or some other method should be provided to allow users to skip
repetitive navigation links and go directly to the main content of the page.
2.7.1.2 E-Mail Messaging

In order to ensure accessibility of e-mail messages, users must always have the option to
send plain ASCII text.
Common issues that create accessibility problems are the inclusion of non-plain text
components, i.e. XHTML markup code for fonts, colours and bold formatting, within the body
of the e-mail, the inclusion of background images that obscure text for people with low-
vision, the attachment of non-standard file formats that cannot be accessed by the recipient
of the e-mail.
Therefore, developers should ensure that e-mail content is only allowed in a plain text format
without fonts, colours, font formatting or background images. It is a good idea to provide an
easy-to-use feature to allow the users to configure the interface according to their individual
preferences (e.g. a simple or expert option).
2.7.1.3 Document Repositories

The indexing system of a document repository should be accessible and should follow a
logical document structure. Documents should be stored in standard XHTML format, as
proprietary or non-standard file formats may create barriers.
Issues to be considered are the use of indexing or navigation systems without complex
frames that do not include the title or name attributes. Form fields in search utilities should
accommodate keyboard navigation. Display options should be easy to locate and accessible
via the keyboard.
It should be possible to perform all actions by the keyboard.
2.7.1.4 Organizers, Schedulers, and Calendars

For such applications the posted information should be structured in a logical manner,
encoded using standard XHTML.
Non-visual users are at a disadvantage when confronting complex tables or scripting

languages. For these and other users, information must linearize correctly in order to be
translated accurately into other forms, such as audio output. When providers fail to properly
format structured data, dates and events can become improperly juxtaposed. Traditional
calendar layouts are particularly susceptible to this sort of error, so content providers ought
to include alternative linear output whenever possible.
Issues that have to be avoided are the use of scripts that use event handlers that are device-
dependent (i.e., require a mouse), the use of incorrect markup that inhibits the users ability
to navigate among table cells and access headers and other cell information, table cells
whose content does not linearize correctly.
The following are good practices:

Tools should be usable even when scripts are not supported.
Equivalent information should be provided on an alternative accessible page.
For data tables row and column headers should be identified. Abbreviations for
header labels should be used and structural groups of rows or columns should be
identified.
Table content should linearize correctly and a linear alternative should be provided, if
this cannot be assured.
2.7.2 Guidelines for Developing Accessible Synchronous Communication and

Collaboration Tools
A common accessibility problem in all synchronous communication tools are the fast pace of
conversation which may limit access by users who communicate slowly. Another issue is the
existence of functions that are exclusively mouse-driven.
The tool developers should provide mechanisms that allow users who communicate slowly
to participate effectively (e.g., speaker designation) and should ensure that all mouse actions
can also be completed, effectively, from the keyboard.
2.7.2.1 Synchronous Text Chat

Common synchronous text chat accessibility problems are the use of complex and non-
standard user interfaces, functions, possible need for simultaneous user attention to multiple
areas (i.e., message composition and message monitoring).
Developers may enhance the accessibility of applications for all users by following these
practices:
The user interface should be simple and appropriate platform-specific user interface
guidelines should be followed.
Keyboard accessible mechanisms should be provided to enable the user to quickly

shift the focus between the message composition and the message monitoring
areas.
It should be possible not to automatically move focus to new messages as they

arrive.
It should be possible to manually refresh the list of messages.
2.7.2.2 Audio-Conferencing
Users with hearing and speech disabilities should be accommodated by such a system.
Issues to be considered are that the audio output is inaccessible to users who are deaf or
who have profound hearing loss and that speech input may be difficult for users with speech
disabilities.

The following may support the development of accessible audio-conferencing applications

for all users:
A real-time text transcript should be available to participants. The transcript can be

provided by any one of a number of methods (e.g., generated by effective minute
taking, telecom relay service, or reliable voice recognition).
A real-time text-to-speech capability should be available to participants via telecom

relay service or automated text-to-speech.
2.7.2.3 Video-Conferencing
Users with visual, hearing, and/or speech disabilities must be accommodated by such a tool.
Issues to be considered as they may pose barriers to the tool use are that additional visual
information such as graphs and charts may be inaccessible to users who are visually
impaired, audio output is inaccessible to users who are deaf or who have profound hearing
loss, speech input requirements may be too much for users with speech disabilities.
Furthermore, videoconference systems that preferentially encode stationary elements of a
scene, rather than dynamic ones, can disrupt effective transmission of sign languages, since
they depend on movement.
Proposed good practices are:
Visual support elements should be provided and users should be encouraged to use
this function.
A real-time text transcript should be made available to participants. These transcripts

can be generated be effective minute taking, telecom relay service, or reliable voice
recognition. Once generated, this text transcript might be displayed by a sign
language "avatar" (computer-generated signer). Real-time text transcription services
can be accessed remotely.
Sign translation services provided remotely should be added. The tool should be
designed to accept a second video stream arriving from another location.
A real-time text-to-speech capability should be available to participants. Transcripts

can be generated by a telecom relay service or automated text-to-speech software.
Video encoding standards that facilitate sign language transmission, such as MPEG-
4, should be investigated.

3 Use case analysis

In D1.7.1, a number of Use Cases for the Workplace Domain have been identified, based on
which the simulation models have been created. These use cases consist of 3 Scenarios in
the Workplace Design Sub-domain and 3 scenarios in the Collaborative Tools sub-domain.
The workplace design scenarios describe physical modeling and simulation of environment,
objects and actions which we will refer to as 3D scenarios, while the Collaborative tools
scenarios describe ICT interface interaction with a software application using specific input
and output devices, so we will refer to them as 2D scenarios. Therefore, the way to handle
each one is fundamentally different. In the following sections an analysis of the transfer from
use cases to simulation models will be described
3.1 Workplace Design Use Case Scenarios

- Healthy - Joint strength
- Limited mobility - Joint mobility
- Limited force capability - Vision parameters
- Limited Vision
Open drawer Human Simulation

Actor
operation Parameter
Use
D1.7.1 Action
Case
Accessibility
Simulation
Pull Design
drawer handle Question
- Posture simulation
- Vision Simulation
- Gait Simulation
1
- Is handle reachable?
- Is drawer movable?
Figure 3-1: Use case analysis process for 3D scenarios
Scenario 4.1.x.1 (x= a|b, desktop, immersive): Entering the workspace and sitting on
desk
The users want to navigate from the entrance of the building until they reach their desk and
sit on their chair. This involves the following steps:
Step 1: Locate and enter main entrance

Step 2: Locate and approach Lift
Step 3: Locate and push Lift button

Step 2: Get aware of open doors and enter lift

Step 4: Locate and push 2nd floor button
Step 5: Get aware of open doors and exit lift
Step 6: Locate and enter office
Step 7: Locate and walk to the office chair
Step 8: Adjust and sit on chair
Scenario 4.1.x.2 (x= a|b, desktop, immersive): Using office equipment
The users want to access their desk drawers and use devices and equipment on their desk.
This involves the following steps:
Step 1: Opening drawer

Step 2: Locate button and turn on PC
Step 3: Activating computer screen
Step 4: Using devices
Scenario 4.1.x.3 (x= a|b, desktop, immersive): Print a document and classify it in a
dossier on the closet
The users want to navigate from their office, add paper to a printer, get a printed document
from the printer and classify it in a dossier. This involves the following steps:
Step 1: Go to storage area

Step 2: Get paper
Step 3: Feed paper in printing tray
Step 4: Get printed document from printer
Step 5: Get a dossier from shelf
Step 6: Classify document in dossier
Step 7: Store dossier on shelf
In the following table, for each workplace scenario, the description of the design questions
and possible impairments are shown
Subject Scenario Use Case Design Question Impairments

Orientation, Vision Impairment
Entering the
Visibility, Upper Limb
Workspace Navigation 4.1.x.1 workspace and sitting
Moveability, impairment
on desk
Reachability Lower limb impairment
Visibility, Vision Impairment
Using office
Office Equipment 4.1.x.2 Reachability, Upper Limb
Equipment
Force Capacity impairment
Orientation, Vision Impairment
Print a document and Visibility, Upper Limb
Office Design 4.1.x.3
classify it in a dossier Moveability, impairment
Reachability Lower limb impairment

3.2 Collaborative Tools Use Case Scenarios
-Input device handling

- Healthy
- Limited vision -Device output understanding
- Limited hearing
Select file to Human Simulation

Actor
upload Parameter
Use
D1.7.1 Action
Case
Accessibility
Simulation
Click upload Design
button Question
- Input control simulation

- Vision Simulation
- Hearing Simulation
- Is button viewable?
- Can the user point
accurately to the
button?
Figure 3-2: Use case analysis process for 2D scenarios
Scenario 4.2.1: File upload and online editing interface design
The users want to upload a file to a sharing repository and the print a copy of the document.
This involves the following steps:
Step 1: Select "File upload" from menu

Step 2: Locate file upload dialog box
Step 3: Select file to upload
Step 2: Locate upload button
Step 4: Click upload button
Step 5: Get aware of "File uploaded" message
Step 6: Select an uploaded file
Step 7: Select "Edit File" from menu
Step 8: Locate new window with file open for editing
Step 9: Start inserting text in the file
Step 10: Locate "print button" and send a document for print
Step 11: Become aware of message "out of paper"
Scenario 4.2.2: Create discussion and post item

The users want to create a new discussion on a text chat system. This involves the following
steps:
Step 1: Select "Create new discussion" from menu

Step 2: Locate "new discussion" dialog box
Step 3: Insert title
Step 2: Locate "Post" button
Step 4: Click post button
Step 5: Locate "Discussion created" message
Step 6: Select "Post item" from menu
Step 7: Locate "New item" dialog box
Step 8: Insert text
Step 9: Locate "Item posted" message
Scenario 4.2.2: Realise a teleconference
The users want to start a teleconference with remote collaborators. This involves the
following steps:
Step 1: Locate "Incoming call" message box

Step 2: Locate and click accept button
Step 3: Locate and adjust volume
Step 2: Hear other participants
Step 4: Speak to other participants
Subject Scenario Use Case Design Question Impairments

Usability, Vision Impairment
File upload and online
4.2.x.1 Visibility, Hearing Impairment
editing interface design
Audibility Cognitive Impairment
Interface Design Usability, Vision Impairment
Create discussion and
post item
Usability, Vision Impairment
Realise a
teleconference

4 Simulation models
4.1 General approach
All simulation models and related information are created according to the following general
process:
Use cases definition: definition of main use cases and their analysis in terms of
scenarios, actors and tasks.
Tasks and subtasks definition: tasks and subtasks are extracted from use
cases description. In case of healthcare industry and use cases selected its a
good practice restrict use cases to very simple ones. This means that use cases
should match a task to be simple enough to be achieve its objective.
Primitive tasks definition: each subtask is deeply analyzed and divided into
atomic tasks called also primitive tasks.
Specification of disabilities related with the primitive tasks: keeping in mind
the disabilities and/ or psychological states suffered by a user considered in
VERITAS, a set of impairment, disabilities and P&B states should be selected
according to specific subtasks and/or primitives.
Specification of alternative primitive tasks: For each disability an alternative
primitive task has to be defined to bypass or try to bypass the gap by objective.
Definition of objects involved in the interaction with the user: Each task
requires the interaction with one or more objects. During this step we have to
define the objects and the relative parameters considered to measure the
interaction.
Definition of success criteria for the tasks: The success criteria have to be
defined starting from the parameters and the object selected.
Tasks analysis: For each task an analysis has to be conducted in order to divide
each task in a set of subtasks and each subtask in a set of primitives. Starting
from that the impairment defined for each primitives and the alternative primitive
tasks has to be related.
Interaction analysis: Each task to be conducted requires interactions. The
interactions are defined in terms of modality, object and means.
Simulation models: Since the task and interaction analysis are in place, the
process can be completed with the generation of simulation models. This activity
will apply the UsiXML language.

4.1.1 Definition of task.

A task is an high level concept representing a sequence of actions which must be completed by
the user in order to achieve a complex goal. There is not necessarily a constraint on the order of
the actions that must be performed. A task usually involves a number (at least two) of interactions
between the end user and the system.
A simple diagram representing a task and its associated attributes is depicted in the below figure.
Figure 4-1: Task representation
4.1.2 Definition of subtask.

A subtask is a complex action that represents an intermediate goal that must be completed (along
with other goals) by the user in order to accomplish a task. The granularity of subtasks is variable,
depending on the nature of the task to be accomplished and also on how the task decomposition
can be done with respect to its components.
An example of this variability is reported here: in the context of the Collaborative Tools task
analysis, there is a subtask whose goal is that the user interacting with the UI reads an on screen
message. This is defined as a subtask involving multiple simpler actions ("components") such as
locating the message on the screen, recognizing the words and more importantly understanding
the meaning of the message. However, the "locating the message on screen" component can be
difficult if a user is affected by a vision impairment. Thus, an alternative to that component is that
the system reads the message aloud (if a screen reader assitive device exists) so that the user can
hear the message and react accordingly. In this case hearing such message is defined as an
alternative component of the action of locating the message on the screen, but it could have also
been defined as an alternative to the whole "read the message" subtask. The approach that has
been followed (where hearing is alternative to locating, not reading) implies that hearing a
message must be followed by understanding just as it is in the normal (non vision-impaired) case.
A simple diagram representing a task and its associated attributes is depicted below.
25/11/2011 50 Hypertech
Figure 4-2: Subtask representation

4.1.3 Definition of Primitive task.
What is a primitive task? A primitive is an atomic action that can be performed by the user. The
word "atomic" in this context is used in his classical meaning of "which cannot be further split into
simpler components". An example of primitive task is the action of locating an UI component (such
as a button) on the screen. A primitive task is typically associated with the following set of
attributes which in turn are defined in a UsiXML file which is called a Multimodal Interaction
Model and describes the following parameters of a primitive task:
a means of interaction : the part of the human body that is normally used to perform the
interaction between the user and the system. In the aforementioned example, the means of
interaction for locating a UI component on a screen are the eyes.
a modality : the functional capability of the human body that is involved in the performance
of the action. In the example above the modality is "vision", or the faculty of sight.
an object : the part of the system involved with the interaction with the user. Again, in the
example above the object involved in the interaction with the user is the device's screen.
A simple diagram representing the relations between a primitive task and its associated attributes
is depicted in 4.

Figure 4-3: Primitive task and related attributes
The above components are used in the following process:
1. Generation of overall task table (Figure 4-4)

All necessary data are collected from the deliverables D1.7.1 (use cases), D1.7.2 (task
models) and ID2.8.3 (interaction modalities). Finally they are structured in an EXCEL table
as illustrated in Figure 4-4.
D1.7.1 Use case definition D1.7.2 Task analysis ID2.8.3 Multimodal interaction
Primitive
Alternative
tasks
Alternative Alternative task
Use Case Task Subtask (numbers Modality Task object Disability
task(s) modality object/assistiv
indicate
e device
alternatives)
Parking brake Lower limb

Push (thumb) Motor Pull (hand) Motor Brake lever
2.1.a.3 Conducting a release button impaired
Parking brake
Handbrake car
Pull (hand)
Figure 4-4: Generation of overall simulation task table
2. Identification of object parameters

For all relevant task objects the variable parameters are identified. E.g. a hand brake
contains the parameters rotation angle and resistance force.
3. Definition of success criteria for each task
4. Generation of corresponding UsiXML files (Figure 4-5)
The UsiXML files for the simulation model, task model and multimodal interaction model file
are created from the overall simulation task table.
5. Transfer of simulation models into Veritas simulation scenarios
Finally all simulation models are transferred into the Veritas simulation scenarios using the
Veritas Simulation Editor tools (Interaction Adaptor, Simulation and Virtual User Adaptor,
GUI Adaptor).
This process is applied to the workplace design and collaborative tools application domain and the
results are reported in the following sections.

Primitive
Alternative
tasks
indicate
e device
alternatives)

Parking brake
Handbrake car
Pull (hand)
Simulation model file Task model file Multimodal interaction

(*.usi) (*.usi) model file (*.usi)
Figure 4-5: Generation of UsiXML files

4.2 Workplace Design applications

The selected scenarios derived from the use cases for the collaborative tools area are:
Accessibility of building design (navigation, access etc.). Beneficiary with no limitation, beneficiary with visual impairment). Desktop
simulation/Immersive Simulation (4.1.a.1/4.1.b.1).
Accessibility of office equipment (Using PC, furniture, devices on desk). Beneficiary with no limitation, beneficiary with visual impairments.
Desktop simulation/Immersive Simulation (4.1.a.2/4.1.b.2).
Accessibility of office equipment and access (print a document and classify). Beneficiary with no limitation, beneficiary with lower limb
impairments. Desktop simulation/Immersive Simulation (4.1.a.3/4.1.b.3).
4.2.1 Overall simulation task table
Table 4-1: Overall simulation task table for Workplace Design applications
Primitive
Subtask
tasks Alternative
(numbers Alternative Alternative
Task (numbers Modality Task object Disability task object /
indicate tasks(s) modality
indicate assistive device
alternatives)
alternatives)
Locate (eyes) Vision Main entrance Reduced vision Locate (hands) Motor =
Walk (feet) Motor Main entrance = = = =
Entering the Locate and Locate (eyes) Vision Door handle Reduced vision Locate (hands) Motor =
workspace and enter main
sitting on desk entrance Reach (hands) Motor Door handle = = = =
Grasp (hands) Motor Door handle = = = =
Push (hands) Motor Door handle = = = =
Push (hands) Motor Door = = = =
Release (hands) Motor Door handle = = = =

Primitive
Subtask
tasks Alternative
alternatives)
alternatives)
Locate and Locate (eyes) Vision Lift doors Reduced vision Locate (hands) Motor =
approach lift
Walk (feet) Motor Lift doors = = = =
Locate (eyes) Vision Button Reduced vision Locate (hands) Motor =

Locate and
push call button Reach (fingers) Motor Button = = = =
Push (fingers) Motor Button = = = =
Get aware of Open sound or
Locate (eyes) Vision Lift doors Reduced vision Locate (ears) Hearing
open doors and voice
enter lift Walk (feet) Motor Lift = = = =
Locate and Locate (eyes) Vision Button Reduced vision Locate (hands) Motor =
push button 2nd
floor Reach (fingers) Motor Button = = = =
Push (fingers) Motor Button = = = =
Open sound or
Get aware of Locate (eyes) Vision Lift doors Reduced vision Locate (ears) Hearing
voice
open doors and
exit lift Walk (feet) Motor Outside Lift doors = = = =
Locate (eyes) Vision Door Reduced vision Locate (hands) Motor =
Walk (feet) Motor Door = = = =
Locate and Locate (eyes) Vision Door handle Reduced vision Locate (hands) Motor =
enter office
Reach (hands) Motor Door handle = = = =
Grasp (hands) Motor Door handle = = = =
Push (hands) Motor Door handle = = = =
Push (hands) Motor Door = = = =
Primitive
Subtask
tasks Alternative
alternatives)
alternatives)
Release (hands) Motor Door handle = = = =
Locate and Locate (eyes) Vision Chair Reduced vision Locate (hand) Motor =
walk to the
office chair Walk (feet) Motor In front of Chair = = = =
Adjust and sit Reach (hands) Motor Chair = = = =
on chair Push (hands) Motor Chair = = = =
Sit (full body) Motor Chair = = = =
Locate (eyes) Vision Drawer Vision impaired Locate (hands) Motor =
Reach (hands) Motor Drawer handle = = = =
Opening drawer
Grasp (hands) Motor Drawer handle = = = =
Pull (hands) Motor Drawer handle = = = =
Locate power Locate (eyes) Vision Power button Reduced vision Locate (hands) Motor =
button and turn Reach (hands) Motor Power button = = = =
on PC Push (fingers) Motor Power button = = = =
Locate (eyes) Vision Power button Vision impaired Locate (hands) Motor =
Using office Reach (hands) Motor Power button = = = =
equipment
Push (finger) Motor Power button = = = =
Activating Reach (hands) Motor Computer screen = = = =
computer
screen Grasp (hands) Motor Computer screen = = = =
Pull closer
Motor Computer screen = = = =
(hands)
Push farther
(hands)

Primitive
Subtask
tasks Alternative
alternatives)
alternatives)
Pull lower
(hands)
Pull higher
(hands)
Phone (or printer,
Locate (eyes) Vision Vision impaired Locate (hands) Motor =
scanner)
Phone (or printer,
Reach (hands) Motor = = = =
Using devices scanner)
Grasp (hands) Motor Phone hook = = = =
Push buttons on
Push (hands) Motor = = = =
devices
Leave chair
Wheelchair Wheelchair
(hands, feet, Motor Chair = Motor
user wheels
Go to storage body)
area Locate (eyes) Vision Storage area = Locate (hands) = =
Walk (feet) Motor Storage area = Motor
user wheels
Print a Locate (eyes) Vision Stored paper = Locate (hands) = =
document and
classify it in a Get paper Wheelchair
Reach (hands) Motor Stored paper = Motor =
dossier on the user
closet Wheelchair
Grasp (hands) Motor Stored paper = Motor =
user
Locate (eyes) Vision Printing tray = Locate (hands) = =
Feed paper in Walk (feet) Motor Printer area = Motor
user wheels
printing tray
Wheelchair
Reach (hands) Motor Printing tray = Motor =
user

Primitive
Subtask
tasks Alternative
alternatives)
alternatives)
Wheelchair
Grasp (hands) Motor Printing tray = Motor =
user
Wheelchair
Pull (hands) Motor Printing tray = Motor =
user
Release paper Wheelchair
Motor Stored paper = Motor =
in tray (hands) user
Wheelchair
Push (hands) Motor Printing tray = Motor =
user
Locate (eyes) Vision Printer = Locate (hands) = =
Get printed Wheelchair
document from Reach (hands) Motor Printed document = Motor =
user
printer Wheelchair
Grasp (hands) Motor Printed document = Motor =
user
Locate (eyes) Vision Dossier = Locate (hands) = =
Wheelchair
Walk (feet) Motor Dossier = Motor =
user
Wheelchair
Get a dossier Reach (hands) Motor Dossier = Motor =
user
from shelf
Wheelchair
Grasp (hands) Motor Dossier = Motor =
user
Bring dossier Wheelchair
Motor Dossier = Motor =
down (hands) user
Locate (eyes) Vision Dossier = Locate (hands) = =
Open dossier Wheelchair
Motor Dossier cover = = =
Classify (hands) user
document in Release printed
Wheelchair
dossier document in Motor Dossier = = =
user
dossier (hands)
Close dossier Motor Dossier cover Wheelchair = = =

Primitive
Subtask
tasks Alternative
alternatives)
alternatives)
(hands) user
Locate (eyes) Vision Shelf = Locate (hands) = =
Wheelchair
Store document Walk (feet) Motor Shelf = Motor =
user
on shelf
Lift dossier to Wheelchair
Motor Dossier = Motor =
shelf (hands) user

4.2.2 Identification of object parameters

The table that follows reports the objects to be interacted with by the user and evaluated,
associated to a set of relevant parameters affecting their interaction performance. These
parameters, which can be parameterized totally or constitute the test independent variables,
to be added to the solutions being tested with different user profiles.
Table 4-2: Object parameters for the Workplace Design applications

Use Case Task object Task objects Alternative Alternative /
x={a|b} parameters task object / assistive
assistive parameters
device
Main entrance Position in x,y,z = =
Position in x,y,z
Rotation in degrees
Door handle Mass in kg = =
Resistance Force in
Nt
Position in x,y,z
Rotation axis
Door Mass in kg = =
Resistance Force in
Nt
Position in x,y,z
Lift Doors Sound/Voice
Lift doors Translation axis
speaker/Bell Sound volume
Mass in kg
4.1.a.1 & 4.1.b.1

Lift Position in x,y,z = =
Position in x,y,z
Translation axis
Button = =
Mass in kg Resistance
Force in Nt
Outside Lift doors Position in x,y,z = =
In front of Chair Position in x,y,z = =

Position in x,y,z
Rotation axis
Chair Mass in kg = =
Resistance Force in
Nt


device
Position in x,y,z
Translation axis
Power button = =
Force in Nt
Position in x,y,z
Translation axis
Drawer = =
Force in Nt
Position in x,y,z
Translation axis
Computer screen = =
Force in Nt
4.1.a.2 & 4.1.b.2
Phone (or printer,
Position in x,y,z = =
scanner)
Position in x,y,z
Phone hook = =
Mass in kg
Position in x,y,z
Push buttons on Translation axis
= =
devices Mass in kg Resistance
Force in Nt
Position in x,y,z
Rotation axis Mass in kg
Chair Mass in kg Wheelchair Resistance Force
Resistance Force in in Nt
Nt
Storage area Position in x,y,z = =
Position in x,y,z
Stored paper = =
Mass in kg
4.1.a.3 & 4.1.b.3 Position in x,y,z
Translation axis
Printing tray Mass in kg = =
Resistance Force in
Nt
Printer area Position in x,y,z = =
Position in x,y,z
Paper = =
Mass in kg
Printer Position in x,y,z = =


device
Position in x,y,z
Printed document = =
Mass in kg
Shelf Position in x,y,z = =
Position in x,y,z
Dossier = =
Mass in kg

4.2.3 Definition of success criteria for each task

In the table that follows are reported the success criteria for each use case of the workplace design, expressed either at sub-task level (i.e. a
complete operation) or at primitive / alternative task level.
In this way, the interaction performance can either be described at complete operation level and / or at single action level, in order to sort out the
critical factors that affect the interaction performance.
Table 4-3: Task success criteria for the Workplace Design simulation scenarios
Task success criteria
Subtask Primitive Tasks Interested in

Responsible
(numbers (numbers Alternative Sub-task Primitive Alternative testing with
Use Case Task for providing
indicate indicate tasks(s) level task level task level beneficiaries
the design
alternatives) alternatives) (disabilities)
The entrance Visually

Locate (eyes) Locate (hands) = Hypertech
door is found Impaired
The user is in
Visually
Walk (feet) = front of the = Hypertech
Impaired
door
the door
Visually
Locate (eyes) Locate (hands) handle is = Hypertech
Entering the The Impaired
Locate and found
4.1.a.1 and workspace entrance the user's hand
enter main Visually
4.1.b.1 and sitting Reach (hands) = door is is near the = Hypertech
entrance Impaired
on desk open handle
the user's hand
Visually
Grasp (hands) = grasps the = Hypertech
Impaired
handle
the handle is Visually
Push (hands) = = Hypertech
pushed Impaired
the door is Visually
open Impaired

Responsible
the design
the user's hand

Visually
Release (hands) = is free from = Hypertech
Impaired
the handle
the lift is Visually
the user is found Impaired
Locate and
in front of The user is in
approach lift Visually
Walk (feet) = the lift front of the = Hypertech
Impaired
lift door
the button is Visually
found Impaired
Locate and the lift
push call button is the button is Visually
Reach (hands) = = Hypertech
button pressed reached Impaired
Push (fingers) = = Hypertech
pressed Impaired
the doors are Visually
Get aware of Locate (eyes) Locate (ears) the user is = Hypertech
open Impaired
open doors inside the
and enter lift lift the user is Visually
Walk (feet) = = Hypertech
inside the lift Impaired
found Impaired
Locate and the 2nd
push button floor button the button is Visually
2nd floor is pressed reached Impaired
pushed Impaired
Get aware of the user is the doors are Visually
Locate (eyes) Locate (ears) = Hypertech
open doors outside the open Impaired
and exit lift Walk (feet) = lift the user is = Hypertech Visually


Responsible
the design
outside the lift Impaired
the office door Visually

is found Impaired
the user is in
Visually
Walk (feet) = front of the = Hypertech
Impaired
door
the door
Visually
Locate (eyes) Locate (hands) handle is = Hypertech
Impaired
found
the office the handle is Visually
Locate and Reach (hands) = = Hypertech
door is reached Impaired
enter office
open the user's hand
Visually
Grasp (hands) = grasps the = Hypertech
Impaired
handle
the handle is Visually
pushed Impaired
the door is Visually
open Impaired
the user's hand
Visually
Release (hands) = is free from = Hypertech
Impaired
the handle
the chair is Visually
Locate (eyes) Locate (hands) the user is = Hypertech
Locate and found Impaired
in front of
walk to the the user is in
the office Visually
office chair Walk (feet) = front of the = Hypertech
chair Impaired
chair


Responsible
the design
the chair is Visually

reached Impaired
Adjust and sit the chair is
Visually
on chair Push (hands) = placed in = Hypertech
the user is Impaired
position
sitting on
the user is
the chair Visually
Sit (full body) = sitting on the = Hypertech
Impaired
chair
The drawer is Locate Visually
Locate (eyes) Locate (hands) Hypertech
found (hands) Impaired
The user's
Visually
Reach (hands) = hand is near = Hypertech
Impaired
the handle
Opening The Drawer
The user's
drawer is opened
hand is Visually
Grasp (hands) = = Hypertech
grasping the Impaired
handle
The drawer is Visually
4.1.a.2 and Using office Pull (hands) = = Hypertech
pulled out Impaired
4.1.b.2 equipment
found Impaired
the PC
Locate power
power the button is Visually
button and Reach (hands) = = Hypertech
button is reached Impaired
turn on PC
pressed
pushed Impaired
Activating The screen The power
Locate Visually
computer Locate (eyes) Locate (hands) is activated button is Hypertech
(hands) Impaired
screen and found


Responsible
the design
adjusted the button is Visually

reached Impaired
The power
Visually
Push (finger) = button is = Hypertech
Impaired
pressed
the screen is Visually

reached Impaired
The user's
hand is Visually
screen
The screen
Pull closer Visually
= has moved = Hypertech
(hands) Impaired
closer
The screen
Push farther Visually
(hands) Impaired
farther
The screen
Pull lower Visually
(hands) Impaired
lower
The screen
Push higher Visually
(hands) Impaired
higher
The device is Locate Visually
Locate (eyes) Locate (hands) Hypertech
found (hands) Impaired
The device
Using devices The user's
is activated Visually
Reach (hands) = hand is near = Hypertech
Impaired
the phone


Responsible
the design
The user's
hand is Visually
phone hook
The button(s) Visually
Push (finger) = = Hypertech
are pushed Impaired
the user is
Leave sit the user has
standing in
(hands, feet, Roll (hands) moved out Hypertech Wheelchair user
front of the
body) the user is of the desk
chair
Go to storage in front of
the storage
area Locate (eyes) = the storage = Hypertech Wheelchair user
area is found
area
the user is in
Walk (feet) Roll (hands) front of the = Hypertech Wheelchair user
storage area
Print a the paper is
Locate (eyes) = = Hypertech Wheelchair user
document found
4.1.a.3 and and classify the user's hand
the user is
4.1.b.3 it in a Reach (hands) = is close to the = Hypertech Wheelchair user
Get paper Grasp the
dossier on paper
paper
the closet the user is
Grasp (hands) = Grasp the = Hypertech Wheelchair user
paper
the printer
tray is found
the paper is
the user is in
Feed paper in in the tray
printing tray and the tray
printer
is closed
the tray is Visually
reached Impaired

Responsible
the design
the tray is
Grasp (hands) = = Hypertech Wheelchair user
grasped
the tray is
Pull (hands) = = Hypertech Wheelchair user
open
Release paper in the paper is in
= = Hypertech Wheelchair user
tray (hands) the tray
the tray is
Push (hands) = = Hypertech Wheelchair user
closed
the printed
Locate (eyes) = document is = Hypertech Wheelchair user
found
Get printed the user is the user's had
document Reach (hands) = Grasp the is close to the = Hypertech Wheelchair user
from printer document paper
the user is
paper
the dossier is
found
the user is in
the dossier dossier
Get a dossier
is in the the user's hand
from shelf
Reach (hands) = user's hand is close to the = Hypertech Wheelchair user
dossier
the user is
dossier


Responsible
the design
Bringing dossier the user's hand

down (hands) is lowered
the dossier is
found
Open dossier the dossier is
Classify (hands) the paper is opened
document in in the the document
Release paper in
dossier = dossier is in the = Hypertech Wheelchair user
dossier (hands)
dossier
Close dossier the dossier is
(hands) closed
the shelf is
found
the dossier the user is in
Store dossier
Walk (feet) Roll (hands) is on the front of the = Hypertech Wheelchair user
on shelf
shelf shelf
Lift dossier to the dossier is
shelf (hands) on the shelf

4.2.4 Generation of UsiXML files

UsiXML V1.8 is the user interface description language used by Veritas. It aims at
expressing user interfaces built with various modalities of interaction and independently of
them. UsiXML is XML-compliant to enable flexible exchange of information and powerful
communication between models and tools used in user interface engineering. The UsiXML
files for the simulation model, task model and multimodal interaction model file are created
from the overall simulation task table.
Overall, the Simulation Models included in this deliverable cover all use case scenarios for
both Workplace Design and Collaborative tools sub-domains. In the Simulation Models task
sequences are represented up to sub-task level, while complex tasks in turn are further
analysed into primitive tasks in the respective Task Models.
For the Workplace design sub-domain there are 3 simulation models, while one example of
Task Model (Open Drawer) is demonstrated, in which the primitive task that compose the
complex sub-task are detailed and finally one example of Multimodal Interaction Model in
which alternative modalities in order to perform a primitive task are demonstrated, containing
information on the object and means of the primitive task (Locate lift doors).
The UsiXML code for the simulation models is included in the Annex of this deliverable while
the UsiXML files themselves are available from the website and the FTP repository of the
project.

Primitive
Alternative
tasks
indicate
e device
alternatives)

Parking brake
Handbrake car
Pull (hand)
Simulation model file Task model file Multimodal interaction

(*.usi) (*.usi) model file (*.usi)
Figure 4-6: Simulation model tree generated from UsiXML for UC4.1.x.1

4.2.4.1 Use Case 4.1.x.1: Entering the workspace and sitting on desk
4.2.4.2 Use Case 4.1.x.2: Using office equipment
Figure 4-8 Simulation model tree generated from UsiXML for UC4.1.x.2

4.2.4.3 Use Case 4.1.x.3: Print a document and classify it in a dossier on the closer
4.2.4.4 Task Model and Multimodal Interaction Model Examples for the Workplace Design sub-domain
Figure 4-10: Example of a Task model definition in UsiXML for the Opening Drawer task

Figure 4-11: Example of a Multimodal Interaction model definition in UsiXML for the Move_to_chair primitive task

4.3 Collaborative Tools applications

The selected scenarios derived from the use cases for the collaborative tools area are:
Accessibility of distant collaborative working tool (file upload, document online editing). Beneficiary with no limitation, elderly beneficiary.
Desktop simulation (4.2.1).
Accessibility of distant collaborative working tool (create a new discussion and post an item). Beneficiary with no limitation, elderly beneficiary
with cognitive impairments. Desktop simulation (4.2.2).
Accessibility of teleconferencing tool (realise a teleconference). Beneficiary with no limitation, elderly beneficiary with hearing impairments.
Desktop simulation (4.2.3).
4.3.1 Overall simulation task table

Table 4-4: Overall simulation task table for Collaborative Tools use cases
Primitive
Subtask Alternative
tasks
Use Case (numbers Alternative Alternative task object /
Task (numbers Modality Task object Disability
x={a|b} indicate tasks(s) modality assistive
indicate
alternatives) device
alternatives)
Reduced
Locate (eyes) Vision File menu = = =
vision
Move mouse
Motor Mouse = = = =
(hands)
Click mouse
Select "File Motor Mouse button = = = =
Upload and button (hands)
online upload" from
4.2.1 Upload File Reduced
document menu Locate (eyes) Vision = = =
menu item vision
editing
Move mouse
Motor Mouse = = = =
(hands)
Click mouse
Motor Mouse button = = = =
button (hands)
Select file to Locate (eyes) Vision File name Reduced = = =

Primitive
Subtask Alternative
tasks
indicate
alternatives)
upload vision
Move mouse
Motor Mouse = = = =
(hands)
Click mouse
button (hands)
Upload Reduced
Locate (eyes) Vision = = =
Locate and button vision
click upload Move mouse
Motor Mouse = = = =
button (hands)
Click mouse
button (hands)
"File
uploaded" Reduced
message on vision
screen
Get aware of
"File Move mouse
uploaded" Motor Mouse = = = =
(hands)
message
Click mouse
button (hands)
Uploaded file Reduced

name vision
Select an Move mouse
Motor Mouse = = = =
uploaded file (hands)
Click mouse
button (hands)

Primitive
Subtask Alternative
tasks
indicate
alternatives)
Edit File Reduced
menu vision
Move mouse
Motor Mouse = = = =
(hands)
Select "Edit Click mouse
File" from button (hands)
Edit File Reduced
menu Locate (eyes) Vision = = =
menu item vision
Move mouse
Motor Mouse = = = =
(hands)
Click mouse
button (hands)
Reduced
Locate (eyes) Vision Inserted text = = =
vision
Insert text in Move mouse
Motor Mouse = = = =
the file (hands)
Push (finger) Motor Keyboard key = = = =
Release (finger) Motor Keyboard key = = = =
Locate (eyes) Vision Print button = = = =
Locate and Move mouse
Motor Mouse = = = =
click Print (hands)
button Click mouse
button (hands)
Get aware of
Message on
message "out Locate (eyes) Vision = = = =
screen
of paper"

Primitive
Subtask Alternative
tasks
indicate
alternatives)
Move mouse
Motor Mouse = = = =
(hands)
Click mouse
button (hands)
Elderly with
Discussion Voice
Locate (eyes) Vision cognitive = Hearing
menu command
impairment
Elderly with
Move mouse Voice
Motor Mouse cognitive = Speak
(hands) command
impairment
Create
Elderly with
discussion Select "Create Click mouse Voice
Motor Mouse button cognitive = Speak
and post item new button (hands) command
4.2.2 impairment
on distant discussion"
collaborative from menu Create new Elderly with
Voice
Locate (eyes) Vision discussion cognitive = Hearing
working tool command
menu item impairment
Elderly with
Move mouse Voice
(hands) command
impairment
Elderly with
Click mouse Voice
button (hands) command
impairment

Primitive
Subtask Alternative
tasks
indicate
alternatives)
Elderly with
Title entry Voice
field command
impairment
Elderly with
Move mouse Voice
Insert title Motor Mouse cognitive = Speak
(hands) command
impairment
Elderly with
Click mouse Voice
impairment
Elderly with
Voice
Locate (eyes) Vision Post button cognitive = Hearing
command
impairment
Locate and
click post Elderly with
Move mouse Voice
impairment
Elderly with
Click mouse Voice
impairment
"Discussion
Elderly with
created" Voice
message on command
impairment
screen
Get aware of
"Discussion Elderly with
Move mouse Voice
created" Motor Mouse cognitive = Speak
(hands) command
message impairment
Elderly with
Click mouse Voice
impairment
Primitive
Subtask Alternative
tasks
indicate
alternatives)
Elderly with
Discussion Voice
menu command
impairment
Elderly with
Move mouse Voice
(hands) command
impairment
Elderly with
Click mouse Voice
Select "Post Motor Mouse button cognitive = Speak
item" from impairment
menu Elderly with
Post item Voice
menu item command
impairment
Elderly with
Move mouse Voice
(hands) command
impairment
Elderly with
Click mouse Voice
impairment
Elderly with
Voice
Locate (eyes) Vision Text field cognitive = Hearing
command
impairment
Elderly with
Move mouse Voice
Insert text Motor Mouse cognitive = Speak
(hands) command
impairment
Elderly with
Click mouse Voice
impairment

Primitive
Subtask Alternative
tasks
indicate
alternatives)
Elderly with
Push keyboard Voice
key (finger)
Motor Keyboard key cognitive = Speak
command
impairment
Release Elderly with

Voice
keyboard key Motor Keyboard key cognitive = Speak
(finger) command
impairment
"Item posted" Elderly with
Voice
Locate (eyes) Vision message on cognitive = Hearing
command
screen impairment
Get aware of Elderly with
Move mouse Voice
"Item posted" Motor Mouse cognitive = Speak
(hands) command
message impairment
Elderly with
Click mouse Voice
impairment
Elderly with
Assistive
Locate (eyes) Vision Accept button hearing Hear (ears) Hearing
hearing aid
impairment
Locate and Elderly with
Move mouse Assistive
click accept Motor Mouse hearing = =
(hands) hearing aid
Realise a button impairment
4.2.3
teleconference Elderly with
Click mouse Assistive
Motor Mouse button hearing = =
button (hands) hearing aid
impairment
Locate Elderly with
Volume Assistive
volume slider Locate (eyes) Vision hearing Hear (ears) Hearing
dialog box hearing aid
and adjust impairment

Primitive
Subtask Alternative
tasks
indicate
alternatives)
volume Elderly with
Move mouse Assistive
Motor Mouse hearing = =
(hands) hearing aid
impairment
Elderly with
Click mouse Assistive
Motor Mouse button hearing = =
button (hands) hearing aid
impairment
Elderly with
Assistive
Hear (ears) Hearing Sound hearing = =
hearing aid
impairment
Elderly with
Locate Assistive
Communicate Hear (ears) Hearing Sound hearing Vision
written text hearing aid
with other impairment
participants Elderly with
Assistive
Speak (voice) Voice Sound hearing = =
hearing aid
impairment

4.3.2 Identification of object parameters

The following table reports the objects to be interacted with by the user, associated to a set
of relevant parameters affecting the interaction performance. These parameters, which can
be parameterized totally or partially (i.e. only some such as e.g. intelligibility of a speech-
synthesized message) constitute the test independent variables, to be added to the solutions
(primitive vs alternative object of table 4-4) being tested with different user profiles.
Table 4-5: Object parameter table for Workplace scenarios

Use Case Task object Task objects parameters Alternative Alternative /
x={a|b} task object / assistive
device
Position in x,y
Dimensions in w,h
Contrast level, as
specified by the Weber
File menu contrast sensitivity
= =
formula:
Position in x,y
Dimensions in w,h
Contrast level, as
File upload specified by the Weber
contrast sensitivity = =
menu item
formula:
4.2.1 Mouse Position in x,y = =

Mouse button button id = =
Position in x,y
Dimensions in w,h
Contrast level, as
File upload specified by the Weber
Dialog box
formula:
Position in x,y -
Dimensions in w,h
Contrast level, as
File name in list specified by the Weber
of files
formula:


device
Position in x,y
Dimensions in w,h
Contrast level, as
Upload button contrast sensitivity = =
formula:
Position in x,y
Dimensions in w,h
"File uploaded" Contrast level, as
message on contrast sensitivity = =
screen formula:
Position in x,y
Dimensions in w,h
Uploaded file Contrast level, as
name in list of contrast sensitivity
= =
files formula:
(pure number)
Position in x,y
Dimensions in w,h
Contrast level, as
Edit File menu specified by the Weber
item
formula:
Position in x,y
Dimensions in w,h
Contrast level, as
Inserted text contrast sensitivity = =
formula:
Position in x,y
Print button Dimensions in w,h = =
Contrast level, as


device
contrast sensitivity
formula:
Position in x,y
Dimensions in w,h
"Out of paper" Contrast level, as
message on contrast sensitivity = =
screen formula:
Position in x,y
Dimensions in w,h
Contrast level, as
OK button contrast sensitivity = =
formula:
Keyboard key key value = =

Position in x,y
Dimensions in w,h
Contrast level, as
Discussion specified by the Weber Voice Recognition
menu contrast sensitivity command rate
formula:
Position in x,y Recognition

Dimensions in w,h rate
4.2.2
Create new Contrast level, as
specified by the Weber Voice
discussion contrast sensitivity command
menu item formula: Semantics
Recognition
rate
Mouse Position in x,y Voice output Semantics
Sound level


device
Position in x,y
Contrast level, as
New discussion specified by the Weber
dialog box on contrast sensitivity = =
screen formula:
Position in x,y
Dimensions in w,h
Contrast level, as
formula:
Position in x,y
Dimensions in w,h
Contrast level, as
Title entry field contrast sensitivity = =
formula:
Keyboard key key value = =

Position in x,y
Dimensions in w,h
Contrast level, as
Post button contrast sensitivity = =
formula:
Position in x,y
Dimensions in w,h
"Discussion Contrast level, as
created" specified by the Weber
message on
screen formula:
Position in x,y
OK button Dimensions in w,h = =
Contrast level, as


device
formula:
Position in x,y
Dimensions in w,h
Contrast level, as
Text field contrast sensitivity = =
formula:
Position in x,y
Dimensions in w,h
Contrast level, as
Post item menu specified by the Weber
= =
item
formula:
Position in x,y
Dimensions in w,h
"New item" Contrast level, as
dialog box on contrast sensitivity
= =
screen formula:
Position in x,y
Dimensions in w,h
Written text as Contrast level, as
inserted in new contrast sensitivity = =
item dialog box formula:
Position in x,y
Dimensions in w,h
"Item posted" Contrast level, as
message on specified by the Weber = =
screen contrast sensitivity
formula:


device
Position in x,y
Dimensions in w,h
Contrast level, as
formula:
Position in x,y
Dimensions in w,h
"Incoming call" Contrast level, as
message box on contrast sensitivity = =
screen formula:
Position in x,y
Dimensions in w,h
Contrast level, as
Accept button contrast sensitivity
= =
formula:
4.2.3
Mouse Position in x,y = =

Position in x,y
Dimensions in w,h
Contrast level, as
Volume slider contrast sensitivity = =
formula:
Assistive
Sound Sound level in dB hearing aid
Sound level

4.3.3 Definition of success criteria for each task

Table 4-6: Task success criteria for the Collaborative tools simulation scenarios
Primitive
Subtask Responsible Interested in
Tasks
(numbers Alternative Sub-task Primitive Alternative for testing with
Use Case Task (numbers
indicate tasks(s) level task level task level providing beneficiaries
indicate
alternatives) the design (disabilities)
alternatives)
the 'File
Visually
Locate (eyes) = menu is = Byte
Impaired
located
New position
the 'File in x,y of the
Move mouse Visually
= menu is mouse over = Byte
(hands) Impaired
activated the "File"
menu
Click mouse Mouse left
Visually
Upload and button = button is = Byte
Select "File Impaired
online (hands) clicked
4.2.1 upload" from the "File
document
menu upload" menu Visually
editing Locate (eyes) = = Byte
item is Impaired
located
New position
the 'file
in x,y of the
upload' menu
Move mouse mouse over Visually
= item is = Byte
(hands) the "File Impaired
activated
Upload"
menu item
Visually
button = button is = Byte
Impaired
(hands) clicked


Primitive
Tasks
indicate
alternatives)
the file name
of the file to Visually
Locate (eyes) = = Byte
be uploaded Impaired
is located
New position
in x,y of the
Select file to Move mouse the file is mouse over Visually
= = Byte
upload (hands) selected the filename Impaired
of the file to
be uploaded

Visually
Impaired
(hands) clicked
the "Upload"
Visually
Locate (eyes) = button is = Byte
Impaired
located
New position
the 'upload in x,y of the
Activate upload Move mouse Visually
= button' is mouse over = Byte
button (hands) Impaired
activated the "Upload"
button
Visually
Impaired
(hands) clicked
the "File the "File
Get aware of "File
uploaded" uploaded" Visually
uploaded" Locate (eyes) = = Byte
message is message is Impaired
message
located located


Primitive
Tasks
indicate
alternatives)
New position
Move mouse in x,y of the Visually
= = Byte
(hands) mouse over Impaired
the 'ok' button
Visually
Impaired
(hands) clicked
the file name
of an Visually
uploaded file Impaired
is located
New position
in x,y of the
Select an the file is
uploaded file = selected = Byte
(hands) the filename Impaired
of the
uploaded file
Visually
Impaired
(hands) clicked
the "File"
Visually
Locate (eyes) = menu is = Byte
the edit file' Impaired
Select "Edit File" located
menu item is New position
from menu
activated in x,y of the
Move mouse Visually
= mouse over = Byte
(hands) Impaired
the "File"
menu


Primitive
Tasks
indicate
alternatives)
Visually
Impaired
(hands) clicked
the "Edit
File" menu Visually
item is Impaired
located
New position
in x,y of the
= = Byte
(hands) the "Edit Impaired
File" menu
item
Visually
Impaired
(hands) clicked
Locate the
text input Visually
area on Impaired
screen
New position
in x,y of the
Move mouse Visually
Insert text in the = the text is mouse in the = Byte
(hands) Impaired
file inserted text insertion
area
Visually
Impaired
(hands) clicked
keyboard key Visually
Push (fingers) = = Byte
is pressed Impaired


Primitive
Tasks
indicate
alternatives)
Release keyboard key Visually

= = Byte
(finger) is released Impaired

located Impaired
New position
in x,y of the
Move mouse the 'print' Visually
Locate and click = mouse over = Byte
(hands) button is Impaired
Print button the 'print'
activated
button
Visually
Impaired
(hands) clicked
the message Visually
is located Impaired
New position
Get aware of Move mouse in x,y of the Visually
= the message = Byte
message "out of (hands) mouse over Impaired
is located
paper" the 'ok' button
Visually
Impaired
(hands) clicked
Create The user can "Discussion"
Select "Create "Discussion" Elderly with
4.2.2 Speak start a new selected for
discussion and Locate (eyes) menu is Byte cognitive
new discussion" (mouth) discussion activation via
post item on located impairment
board and speech


Primitive
Tasks
indicate
alternatives)
distant from menu post an item New position
collaborative on it in x,y of the
Elderly with
working tool Move mouse mouse over
= = Byte cognitive
(hands) the
impairment
"Discussion"
menu
Click mouse Mouse left "Discussion" Elderly with
Speak
button button is activated via Byte cognitive
(mouth)
(hands) clicked speech impairment
"Create new
"Create new
discussion" Elderly with
Speak discussion"
Locate (eyes) selected for Byte cognitive
(mouth) menu item is
activation via impairment
located
speech
New position
in x,y of the
mouse over Elderly with
Move mouse
= the "Create = Byte cognitive
(hands)
new impairment
discussion"
menu item
"Create new
Click mouse Mouse left Elderly with
Speak discussion"
button button is Byte cognitive
(mouth) activated via
(hands) clicked impairment
speech
New position
Elderly with
Move mouse the text is in x,y of the
Insert title = = Byte cognitive
(hands) inserted mouse over
impairment
the textbox to


Primitive
Tasks
indicate
alternatives)
insert title
Click mouse Mouse left Text insertion Elderly with

Speak
(mouth)
Elderly with
keyboard key
Push (fingers) = = Byte cognitive
is pressed
impairment
Elderly with
Release keyboard key
= = Byte cognitive
(finger) is released
impairment
"Post" button
the "Post" Elderly with
Speak selected for
Locate (eyes) button is Byte cognitive
(mouth) activation via
located impairment
speech
New position
the 'post'
Activate 'post' in x,y of the Elderly with
Move mouse button is
button = mouse over = Byte cognitive
(hands) clicked
the "Post" impairment
button
Click mouse Mouse left "Post" button Elderly with
Speak
(mouth)
the the
Get aware of "Discussion confirmation Elderly with
the message
"Discussion Locate (eyes) Hear (ears) created" that the new Byte cognitive
is located
created" message message is discussion impairment
located was created


Primitive
Tasks
indicate
alternatives)
was heard
New position
Move mouse in x,y of the Visually
= = Byte
(hands) mouse over Impaired
the 'ok' button

Visually
Impaired
(hands) clicked
"Discussion"
"Discussion" Elderly with
Speak selected for
Locate (eyes) menu is Byte cognitive
located impairment
speech
New position
the 'Post item'
Select "Post item" in x,y of the
menu entry is Elderly with
from menu Move mouse mouse over
= activated = Byte cognitive
(hands) the
impairment
"Discussion"
menu
Click mouse Mouse left "Discussion" Elderly with
Speak
(mouth)


Primitive
Tasks
indicate
alternatives)
the "Post "Post" button
Elderly with
Speak item" menu selected for
Locate (eyes) Byte cognitive
(mouth) item is activation via
impairment
located speech
New position
in x,y of the
Elderly with
Move mouse mouse over
= = Byte cognitive
(hands) the "Post
impairment
item" menu
item
Speak
(mouth)
the textbox to Elderly with
Locate (eyes) = insert text is = Byte cognitive
located impairment
New position
Elderly with
Move mouse in x,y of the
= = Byte cognitive
(hands) mouse over
impairment
the textbox
Click mouse the text is Mouse left Text insertion Elderly with
Insert text Speak
button inserted button is activated via Byte cognitive
(mouth)
Elderly with
keyboard key
Push (finger) = = Byte cognitive
is pressed
impairment
Elderly with
Release keyboard key
= = Byte cognitive
(finger) is released
impairment


Primitive
Tasks
indicate
alternatives)
"Post" button
the "Post" Elderly with
Speak selected for
Locate (eyes) button is Byte cognitive
located impairment
speech
New position
the 'post'
Activate 'post' in x,y of the Elderly with
Move mouse button is
button = mouse over = Byte cognitive
(hands) clicked
the "Post" impairment
button
Speak
(mouth)
the "Item Hear the
Elderly with
the message posted" confirmation
Locate (eyes) Hear (ears) Byte cognitive
is located message is that the item
impairment
located was posted
Get aware of New position
"Item posted" Move mouse in x,y of the Visually
= = Byte
message (hands) mouse over Impaired
the 'ok' button
Visually
Impaired
(hands) clicked
the "Accept" Elderly with
Locate (eyes) = button is = Byte cognitive
the 'Accept' located impairment
Realise a Locate and click
4.2.3 button is New position
teleconference accept button Elderly with
Move mouse activated in x,y of the
= = Byte cognitive
(hands) mouse over
impairment
the "Accept"

Primitive
Tasks
indicate
alternatives)
button

button = button is = Byte cognitive
the
Elderly with
"Volume"
Locate (eyes) = = Byte cognitive
slider is
impairment
located
New position
in x,y of the Elderly with
Move mouse
Locate volume = mouse over = Byte cognitive
(hands) the volume is
slider and adjust the "Volume" impairment
adjusted
volume slider
button = button is = Byte cognitive
Elderly with
Test sound
Hear (ears) = = Byte cognitive
heard
impairment
Elderly with
Communicate Discussion Discussion
Hear (ears) = = Byte cognitive
heard heard
with other impairment
participants Participation Participation Elderly with
Speak (voice) = in the in the = Byte cognitive
discussion discussion impairment

4.3.4 Generation of UsiXML files

For the Collaborative Tools sub-domain there are 3 Simulation Models, while one example of Task Model (Select "Post item" from menu) is
demonstrated, in which the primitive tasks that compose the complex sub-task are detailed and finally one example of Multimodal Interaction Model in
which alternative modalities in order to perform a primitive task are demonstrated, containing information on the object and means of the primitive
task (Click mouse button). The UsiXML code for the simulation models is included in the Annex of this deliverable while the UsiXML files themselves
are available from the website and the FTP repository of the project.
4.3.4.1 Use Case 4.2.1: Upload and online document editing
Figure 4-12: Simulation model tree generated from UsiXML for UC4.2.1

4.3.4.2 Use Case 4.2.2: Create discussion and post item on distant collaborative working tool
4.3.4.3 Use Case 4.2.3: Realise a Teleconference

4.3.4.4 Task Model and Multimodal Interaction Model Examples for the Collaborative tools sub-domain
Figure 4-15: Task model tree generated from UsiXML for the Locate and click post button complex task
Figure 4-16: Multimodal Interaction Model tree generated from UsiXML for the Locate post button primitive task

4.4 Integration of VERITAS tools

The simulation models that were created during activity A2.4.2 and presented in the previous
sections will need to be adapted in the following months under A2.4.4, using the Veritas
tools developed to facilitate such an adaptation under A2.1.5 and A2.1.6. As we have
already indicated, there are two types of simulation models. The ones that refer to 3-
dimensional environments and physical interaction with tangible designs (as is the case with
workplace design simulation models) and the ones that refer to 2-dimensional software
environments and interaction using specific input and output devices. Therefore there are
two different sets of tools facilitating the adaption of 3D and 2D simulation models
respectively. The following sections will describe the tools and methodology that will be
followed in each case, in order to adapt, generate and perform accessibility assessment
simulation scenarios for 3D and 2D designs respectively.
4.4.1 VERITAS tools for Workplace Design

For 3D designs, the Veritas Simulation Editor (Figure 4-17) tool will be used to adapt the
abstract Simulation and Interaction models of the design into scenarios that can then be
executed to test for accessibility assessment. Using the Veritas Simulation Editor, the 3D
designs will be first converted into a physical representation of the objects and environment
of the design that can be simulated using the Veritas Core Simulation Platform, and the
Simulation models describing in abstract form the complex and primitive tasks that perform a
scenario will be adapted to match the specific objects and actions of the user in the
particular design.
The integration approach undertakes:
Conversion of the 3D design in a format loadable by the Core Simulation Platform

Assignment of Object parameters, scene rules and conditions that describe the
physical characteristics of the 3D design
Adaptation of Complex Tasks and Primitive tasks from the Simulation, Task and
Multimodal Interaction models into specific actions performed by the Virtual User
avatar on objects within the 3D design.
The methodology that will be employed in order to integrate the 3D simulation models of the
Workplace Design with the Veritas Simulation Editor will be the following:
1. The designer creates a 3D workplace design.

2. The designer uses the Veritas Simulation Editor to convert the 3D design into a
format loadable by the Veritas Core Simulation Platform
3. The designer assigns simulation parameters to the 3D objects of the design she
wants to assess for accessibility in a specific simulation scenario
4. The designer assigns scene rules and conditions that describe what actions the
scene objects perform
5. The designer loads an abstract simulation model and its subtasks and primitive tasks
6. The designer assigns rules and conditions for these tasks pertaining to the specific
requirements of the design

7. The designer assigns initial posture, position and orientation for the virtual user
avatar in the design
8. The designer stores the adapted simulation scenario and interactions
9. The designer loads the scenario in the appropriate Veritas tool (either the Core
Simulation Platform or the Immersive Simulation Platform) in order to test against
various virtual user models with impairments
Figure 4-17: The Veritas Simulation Editor tool (Interaction and Simulation Model
Adaptor)
4.4.2 VERITAS tools for Collaborative Tools

The interaction with a GUI is considered from 2D perspective, since, although performed
through the use of tangible devices (mouse keyboard, monitor, speakers etc.) in the end, the
tasks that need to be performed involve elements of the interface, and their projection on a
2D medium, the screen of either a computer or a mobile device. This results in handling the
task management of an ICT use case scenario such as the Collaborative Tools scenarios as
sequences of input events on the devices used for human-computer interaction and the
resulting output either on screen or as an audio stimulus.
The integration approach undertakes:
Development of a knowledge base related to impairments classification. For each

impairment type VERITAS needs to know statistically how much that affects a task

on an ICT user interface. In order to obtain this, a VERITAS tool needs to be trained
to a set of elementary and atomic UIs like button, text etc. in order to collect enough
data and then statistics classified per impairment.
Development of a GUI interaction adaptor tool. This tool, which is the result of the
work carried out in A2.1.5 and A2.1.6 and part of the Integrated core simulation
platform and exportable toolbox (D2.1.4) will provide the recording of a session
using a software application, where interaction events on UIs will be captured and
then attributed to given set of tasks that describe an abstract simulation model
(Figure 4-18)
Development of a GUI simulation viewer tool. This tool which is the result of the
work carried out in A2.1.1 and part of the Integrated core simulation platform and
exportable toolbox (D2.1.4) will simulate the scenario exported after applying filters
to simulate impairment symptoms based on the parameters contained in a virtual
user model.
The methodology that will be employed in order to assess a UI-based application for
accessibility will be the following:
1. The developer designs a functional UI as executable application.

2. The developer executes the application and sets it as target application for the GUI
Interaction adaptor
3. The developer initiates the recording of timestamped input events along with screen
captures during these events and performs a session that covers the tasks described
in a simulation model
4. When the session is over, the developer marks the areas on the recorded screen
captures corresponding to the UI elements involved in each task, and matches them
to the objects described in the abstract simulation model
5. The developer saves the simulation scenario after all tasks are matched to recorded
events
6. The developer loads a simulation scenario to the GUI Simulation Viewer tool and a
virtual user model to test against it for accessibility
7. The developer executes his application again and through the GUI Simulation Viewer
either as an immersed impaired user or a virtual user agent controlled by the
computer attempts to perform the tasks described in the simulation scenario
8. The GUI Simulation Viewer will apply filtering based on the impairments parameters
that affect mouse motion path, mouse target position accuracy, key entry accuracy,
speed of motion and mouse button press and release, visual representation of the
GUI, audio filtering of UI sounds, delay in cognitive understanding of UI elements etc.

Figure 4-18: Early version of the Veritas GUI Interaction Adaptor

5 Conclusions
Users interaction modeling and simulation for an accessibility assessment is a great challenge
either in the context of 3-Dimensional designs or in the context of Interactive ICT applications. The
Workplace application area, involves designs of both categories, therefore simulation models that
describe interactions of either type are necessary to cover the requirements in this field. In the
scope of this deliverable we have researched these requirements, the use cases that need to be
simulated, the resulting analysis and generation of appropriate abstract user models, as well as the
methodology to follow in the future in order to adapt these abstract simulation models to specific
designs.
Following a User Centric Design methodology, we described the standards, guidelines and best
practices that govern accessibility in the workplace domain. We elaborated on the specific design
issues and requirements in the Workplace design and Collaborative tools subdomains explicitly
and using this research we set forth to generate simulation models for these domains.
The work carried out with respect to the generation of simulation models began with use case
analysis, based on which the use cases of D1.7.1 were created. These use cases were further
refined in D1.7.2 to analyse the tasks required in order to perform the use cases. These use cases
along with the task analysis were further refined and updated during the course of Activity A2.4.2
and fed back into the updated version of D1.7.1b. Simulation Models were then defined following
the definition of application requirements. First, a definition of Simulation Models, Task Models and
Multimodal interaction models was outlined that refer to Tasks, Subtasks and Primitive Tasks,
modeled with UML diagrams, accordingly, describing the levels of abstraction for a sequence of
tasks that perform a use case scenario.
Then, a detailed description of task parameters was constructed, tabulating the modalities, object
parameters, success criteria and thresholds, as well as alternative modalities when specific
impairments occur. Identification of objects, definition of parameters and success criteria allow the
simulation to be based on quantitative and measurable values, so that the basis of an automatic
testing mechanism can be set up. The final Simulation models are described along with examples
of the Task and Multimodal Interaction models they consist of. The models are created in UsiXML
form files, which are included in the Annex.
The deliverable is finalized with a description of the integration methodology with the Veritas Tools,
describing how these abstract Simulation models can be converted into specific simulation
scenarios on actual designs in either the Workplace Design or the Collaborative Tools sub-
domains.

6 References
[1] 2010 ADA Standards for Accessible Design
http://www.ada.gov/regs2010/2010ADAStandards/2010ADAstandards.htm
[2] Australian Standard 3590.2-1990 Screen based Workstations
[3] Australian Standard AS 1680, Standard AS 1680.2.2 - 1994 Interior lighting Part 2.2: Office
and screen-based tasks
[4] Cockburn, A., and Jones, S. (1994): Four principles for groupware design: a foundation for
participative development. In OZCHI '94: conference of the computer human interaction
special interest group of the ergonomics society of Australia
[5] Czerwinski , Mary, Eric Horvitz, Susan Wilhite A diary study of task switching and
interruptions. CHI '04 Proceedings of the SIGCHI conference on Human factors in
computing systems , ACM New York, NY, USA 2004
[6] Dobransky, K. & Hargittai, E. The Disability divide in internet access and use. Information,
Communication & Society 9(3), 313-334, 2006.
[7] European Agency for Safety and Health at Work: Office ergonomics
[8] Homan, M.M. and Armstrong, T.J., 2003. Evaluation of three methodologies for assessing
work activity during computer use. American Industrial Hygiene Association Journal, 64, p.
4855
[9] http://trace.wisc.edu/docs/software_guidelines/software.htm
[10] IMS Accessibility Project Group Guidelines for Developing Accessible Learning
Applications version 1.0 white paper,
http://www.imsglobal.org/accessibility/accessiblevers/index.html
[11] Jones Steve, Identification and use of guidelines for the design of computer supported
collaborative writing tools, Computer Supported Cooperative Work (CSCW) Volume 3,
Numbers 3-4, 379-404, 1995
[12] Kraut R., Egido, C. (1988) Patterns of contact and communication in scientific research
collaborations. Computer Supported Cooperative Work: A book of readings, Morgan
Kaufmann, pp.1-12
[13] Lynch, Kathy Readiness to Communicate in a Digital World, Issues in Informing Science
and Information Technology Volume 3, 2006, p.389-398
[14] Sderstrm, Sylvia Offline social ties and online use of computers: A study of disabled
youth and their use of ICT advances, New Media & Society August 2009 11: 709-727
[15] Van Eerd, Dwayne , Hogg-Johnson, Sheilah , Mazumder, Anjali , Cole, Donald , Wells,
Richard and Moore, Anne(2009) 'Task exposures in an office environment: a comparison of
methods', Ergonomics, 52: 10, 1248 1258

[16] Vitalis, A., Marmaras, N., Legg, St. and Poulakakis, G. (2000). Please be seated. In
Proceedings of the 14th Triennial Congress of the International Ergonomics Association,
San Diego: HFES, Tome 6, pp. 43-45.
[17] UTS Office Ergonomic Guidelines - Equipment Set Up,

http://sydney.edu.au/ohs/ohs_manual/ergonomics/ERGO5.shtml
[18] Wainhouse Research, Unified Communications Products and Services forecasts, July
2008, http://www.wainhouse.com/reports/ucfcst2008.html
[19] www.wsuccess.com/download/survey.doc
[20] Reference Manual of UsiXML V1.8 14 February 2007 by Universit Catholique de

Louvain

7 ANNEX Simulation/Task/Multimodal Interaction

models in UsiXML
7.1 Workplace Design Simulation Models
7.1.1 Locate and enter main entrance
<?xml version="1.0" encoding="UTF-8"?>
<taskmodel>

<task id="st0task0" name="Entering_the_workspace_and_sitting_on_desk" type="abstraction">
<task id="st0task1" name="Locate_and_enter_main_entrance" type="abstraction"/>
<task id="st0task2" name="Locate_and_approach_lift" type="abstraction"/>
<task id="st0task3" name="Locate_and_push_open_button" type="abstraction"/>
<task id="st0task4" name="Get_aware_of_open_doors_and_enter_lift" type="abstraction"/>
<task id="st0task5" name="Locate_and_push_2nd_floor_button" type="abstraction"/>
<task id="st0task6" name="Get_aware_of_open_doors_and_exit_lift" type="abstraction"/>
<task id="st0task7" name="Locate_and_enter_office" type="abstraction"/>
<task id="st0task8" name="Locate_and_walk_to_desk_chair" type="abstraction"/>
<task id="st0task9" name="Adjust_and_sit_on_desk_chair" type="abstraction"/>
</task>

<enabling>
<source sourceId="st0task1"/>
<target targetId="st0task2"/>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.1.2 Using office Equipment

<taskmodel>

<task id="st0task0" name="Using_office_equipment" type="abstraction">
<task id="st0task1" name="Opening_drawer" type="abstraction"/>
<task id="st0task2" name="Locate_power_button_and_turn_on_PC" type="abstraction"/>
<task id="st0task3" name="Activating_computer_screen" type="abstraction"/>
<task id="st0task4" name="Using_devices" type="abstraction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.1.3 Print a document and classify it in a dossier on the closet

<taskmodel>

<task id="st0task0"
name="Print_a_document_and_classify_it_in_a_dossier_on_the_closet"
type="abstraction">
<task id="st0task1" name="Go_to_storage_area" type="abstraction"/>
<task id="st0task2" name="Get_paper" type="abstraction"/>
<task id="st0task3" name="Feed_paper_into_printer_tray" type="abstraction"/>
<task id="st0task4" name="Get_printed_document_from_printer" type="abstraction"/>
<task id="st0task5" name="Get_a_dossier_from_shelf" type="abstraction"/>
<task id="st0task6" name="Classify_document_in_dossier" type="abstraction"/>
<task id="st0task7" name="Store_dossier_on_shelf" type="abstraction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.2 Workplace Design Task Models

7.2.1 Locate and enter main entrance
<taskmodel>

<task id="st0task0" name="Locate_and_enter_main_entrance" type="abstraction">
<task id="st0task1" name="Locate_main_entrance" type="interaction"/>
<task id="st0task2" name="Walk_to_main_entrance" type="interaction"/>
<task id="st0task3" name="Locate_door_handle" type="interaction"/>
<task id="st0task4" name="Reach_door_handle" type="interaction"/>
<task id="st0task5" name="Grasp_door_handle" type="interaction"/>
<task id="st0task6" name="Push_door_handle" type="interaction"/>
<task id="st0task7" name="Push_door" type="interaction"/>
<task id="st0task8" name="Release_door_handle" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.2.2 Locate and approach lift

<taskmodel>

<task id="st0task0" name="Locate_and_approach_lift" type="abstraction">
<task id="st0task1" name="Locate_lift" type="interaction"/>
<task id="st0task2" name="Walk_to_lift" type="interaction"/>
</task>
<enabling>
</enabling>
</taskmodel>
7.2.3 Locate and push call button

<taskmodel>

<task id="st0task0" name="Locate_and_push_call_button" type="abstraction">
<task id="st0task1" name="Locate_call_button" type="interaction"/>
<task id="st0task2" name="Reach_call_button" type="interaction"/>
<task id="st0task3" name="Push_call_button" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.2.4 Get aware of open doors and enter lift

<taskmodel>

<task id="st0task0" name="Get_aware_of_open_doors_and_enter_lift"
type="abstraction">
<task id="st0task1" name="Locate_open_lift_doors" type="interaction"/>
<task id="st0task2" name="Walk_inside_lift" type="interaction"/>
</task>
<enabling>
</enabling>
</taskmodel>
7.2.5 Locate and push 2nd floor button

<taskmodel>

<task id="st0task0" name="Locate_and_push_open_button" type="abstraction">
<task id="st0task1" name="Locate_open_button" type="interaction"/>
<task id="st0task2" name="Reach_open_button" type="interaction"/>
<task id="st0task3" name="Push_open_button" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.2.6 Get aware of open doors and exit lift

<taskmodel>

<task id="st0task0" name="Get_aware_of_open_doors_and_exit_lift" type="abstraction">
<task id="st0task1" name="Locate_open_lift_doors" type="interaction"/>
<task id="st0task2" name="Walk_outside_lift" type="interaction"/>
</task>
<enabling>
</enabling>
</taskmodel>

7.2.7 Locate and enter office

<taskmodel>

<task id="st0task0" name="Locate_and_enter_office" type="abstraction">
<task id="st0task1" name="Locate_door" type="interaction"/>
<task id="st0task2" name="Walk_to_door" type="interaction"/>
<task id="st0task3" name="Locate_door_handle" type="interaction"/>
<task id="st0task4" name="Reach_door_handle" type="interaction"/>
<task id="st0task5" name="Grasp_door_handle" type="interaction"/>
<task id="st0task6" name="Push_door_handle" type="interaction"/>
<task id="st0task7" name="Push_door" type="interaction"/>
<task id="st0task8" name="Release_door_handle" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.2.8 Locate and walk to office chair

<taskmodel>

<task id="st0task0" name="Locate_and_walk_to_office_chair" type="abstraction">
<task id="st0task1" name="Locate_chair" type="interaction"/>
<task id="st0task2" name="Walk_to_office_chair" type="interaction"/>
</task>
<enabling>
</enabling>
</taskmodel>
7.2.9 Adjust and sit on chair

<taskmodel>

<task id="st0task0" name="Adjust_and_sit_on_chair" type="abstraction">
<task id="st0task1" name="Reach_chair" type="interaction"/>
<task id="st0task2" name="Push_chair" type="interaction"/>
<task id="st0task3" name="Sit_on_chair" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.2.10 Opening drawer

<taskmodel>

<task id="st0task0" name="Opening_drawer" type="abstraction">
<task id="st0task1" name="Locate_drawer" type="interaction"/>
<task id="st0task2" name="Reach_drawer_handle" type="interaction"/>
<task id="st0task3" name="Grasp_drawer_handle" type="interaction"/>
<task id="st0task4" name="Pull_drawer_handle" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.2.11 Locate power button and turn on PC

<taskmodel>

<task id="st0task0" name="Locate_and_turn_on_PC" type="abstraction">
<task id="st0task1" name="Locate_power_button" type="interaction"/>
<task id="st0task2" name="Reach_power_button" type="interaction"/>
<task id="st0task3" name="Push_power_button" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.2.12 Activating computer screen

<taskmodel>

<task id="st0task0" name="Activating_computer_screen" type="abstraction">
<task id="st0task1" name="Locate_power_button" type="interaction"/>
<task id="st0task2" name="Reach_power_button" type="interaction"/>
<task id="st0task3" name="Push_power_button" type="interaction"/>
<task id="st0task9" name="Grasp_computer_screen" type="interaction"/>
<task id="st0task10" name="Adjust_computer_screen" type="abstraction">
<task id="st0task11" name="Pull_screen_closer" type="interaction"/>
<task id="st0task12" name="Push_screen_farther" type="interaction"/>
<task id="st0task13" name="Push_screen_higher" type="interaction"/>
<task id="st0task14" name="Pull_screen_lower" type="interaction"/>
</task>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<deterministicChoice>
</deterministicChoice>
</taskmodel>

7.2.13 Using devices

<taskmodel>

<task id="st0task5" name="Using_devices" type="abstraction">
<task id="st0task6" name="Locate_device" type="interaction"/>
<task id="st0task7" name="Reach_device" type="interaction"/>
<task id="st0task8" name="Grasp_device" type="interaction"/>
<task id="st0task9" name="Push_button" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.2.14 Go to storage area

<taskmodel>

<task id="st0task5" name="Using_devices" type="abstraction">
<task id="st0task6" name="Locate_device" type="interaction"/>
<task id="st0task7" name="Reach_device" type="interaction"/>
<task id="st0task8" name="Grasp_device" type="interaction"/>
<task id="st0task9" name="Push_button" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>
7.2.15 Get paper

<taskmodel>

<task id="st0task0" name="Get_paper" type="abstraction">
<task id="st0task1" name="Locate_stored_paper" type="interaction"/>
<task id="st0task2" name="Reach_stored_paper" type="interaction"/>
<task id="st0task3" name="Grasp_stored_paper" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.2.16 Feed paper into printing tray

<?xml version="1.0" encoding="UTF-8" ?>
<taskmodel>

<task id="st0task0" name="Feed_paper_in_printing_tray" type="abstraction">
<task id="st0task1" name="Locate_printing_tray" type="interaction" />
<task id="st0task2" name="Walk_to_printer_area" type="interaction" />
<task id="st0task3" name="Reach_tray" type="interaction" />
<task id="st0task4" name="Grasp_tray" type="interaction" />
<task id="st0task5" name="Pull_tray" type="interaction" />
<task id="st0task6" name="Release_paper_in_tray" type="interaction" />
<task id="st0task7" name="Push_tray" type="interaction" />
</task>

<enabling>
<source sourceId="st0task1" />
<target targetId="st0task2" />
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.2.17 Get printed document from printer

<taskmodel>

<task id="st0task0" name="Get_printed_document_from_printer" type="abstraction">
<task id="st0task1" name="Reach_printed_document" type="interaction"/>
<task id="st0task2" name="Grasp_printed_document" type="interaction"/>
</task>
<enabling>
</enabling>
</taskmodel>
7.2.18 Get a dossier from shelf

<taskmodel>

<task id="st0task0" name="Get_a_dossier_from_shelf" type="abstraction">
<task id="st0task1" name="Locate_dossier" type="interaction"/>
<task id="st0task2" name="Walk_to_shelf" type="interaction"/>
<task id="st0task3" name="Reach_dossier" type="interaction"/>
<task id="st0task4" name="Grasp_dossier" type="interaction"/>
<task id="st0task5" name="Bring_down_dossier" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.2.19 Classify document in dossier

<taskmodel>

<task id="st0task0" name="Classify_document_in_dossier" type="abstraction">
<task id="st0task1" name="Locate_dossier" type="interaction"/>
<task id="st0task2" name="Open_dossier" type="interaction"/>
<task id="st0task3" name="Release_paper_in_dossier" type="interaction"/>
<task id="st0task4" name="Close_dossier" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>
7.2.20 Store dossier on shelf

<taskmodel>

<task id="st0task0" name="Store_document_on_shelf" type="abstraction">
<task id="st0task1" name="Locate_shelf" type="interaction"/>
<task id="st0task2" name="Walk_to_shelf" type="interaction"/>
<task id="st0task3" name="Lift_dossier_to_shelf" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.3 Workplace Design Multimodal Interaction Models

7.3.1 Locate main entrance
<taskmodel>

<task id="st0task0" name="Locate_main_entrance" type="interaction">
<task id="st0task1" name="See(object:main_entrance)(means:eyes)(modality:vision)"
type="interaction"/>
<task id="st0task3" name="Touch(object:main_entrance)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.2 Walk to main entrance

<taskmodel>

<task id="st0task0" name="Walk_to_main_entrance">
<task id="st0task1" name="See(object:main_entrance)(means:feet)(modality:motor)"/>
<task id="st0task3"
name="Rool_wheelchair(object:main_entrance)(means:hands)(modality:motor)"/>
</task>
</taskmodel>

7.3.3 Locate door handle

<taskmodel>

<task id="st0task0" name="Locate_door_handle" type="interaction">
<task id="st0task1" name="See(object:door_handle)(means:eyes)(modality:vision)"
<task id="st0task2" name="Touch(object:door_handle)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.4 Reach door handle

<taskmodel>

<task id="st0task0" name="Reach_door_handle" type="interaction">
<task id="st0task1" name="Reach(object:door_handle)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.5 Grasp door handle

<taskmodel>

<task id="st0task0" name="Grasp_drawer_handle" type="interaction">
<task id="st0task1" name="Grasp(object:drawer_handle)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.6 Push door handle

<taskmodel>

<task id="st0task3" name="Push_door_handle" type="interaction">
<task id="st0task4" name="Push(object:door_handle)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.7 Push door

<taskmodel>

<task id="st0task3" name="Push_door" type="interaction">
<task id="st0task4" name="Push(object:door)(means:hands)(modality:motor)"
<task id="st0task5" name="Push(object:door)(means:feet)(modality:motor)"
</task>
</taskmodel>
7.3.8 Release door handle

<taskmodel>

<task id="st0task0" name="Release_door_handle" type="interaction">
<task id="st0task1" name="Release(object:door_handle)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.9 Locate lift doors

<taskmodel>

<task id="st0task0" name="Locate_lift" type="interaction">
<task id="st0task1" name="See(object:lift)(means:eyes)(modality:vision)"
<task id="st0task2" name="Touch(object:lift)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.10 Walk to lift doors

<taskmodel>

<task id="st0task0" name="Walk_to_lift" type="interaction">
<task id="st0task1" name="Walk(object:lift)(means:feet)(modality:motor)"
<task id="st0task2" name="Rool_wheelchair(object:lift)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.11 Locate call button

<taskmodel>

<task id="st0task0" name="Locate_call_button" type="interaction">
<task id="st0task1" name="See(object:button)(means:eyes)(modality:vision)"
<task id="st0task2" name="Touch(object:button)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.12 Reach call button

<taskmodel>

<task id="st0task0" name="Reach_call_button" type="interaction">
<task id="st0task1" name="Reach(object:button)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.13 Push call button

<taskmodel>

<task id="st0task0" name="Reach_call_button" type="interaction">
</task>
</taskmodel>
7.3.14 Locate open lift doors

<taskmodel>

<task id="st0task0" name="Locate_open_doors" type="interaction">
<task id="st0task1" name="See(object:open_doors)(means:eyes)(modality:vision)"
<task id="st0task2"
name="Hear(object:open_doors_sound)(means:ears)(modality:hearing)"
</task>
</taskmodel>

7.3.15 Locate open lift doors

<taskmodel>

<task id="st0task0" name="Locate_open_doors" type="interaction">
<task id="st0task1" name="See(object:open_doors)(means:eyes)(modality:vision)"
<task id="st0task2"
name="Hear(object:open_doors_sound)(means:ears)(modality:hearing)"
</task>
</taskmodel>
7.3.16 Walk inside lift

<taskmodel>

<task id="st0task0" name="Walk_inside_lift" type="interaction">
<task id="st0task1" name="Walk(object:inside_lift)(means:feet)(modality:motor)"
<task id="st0task2"
name="Rool_wheelchair(object:outside_lift)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.17 Locate 2nd floor button

<taskmodel>

<task id="st0task0" name="Locate_2nd_floor_button" type="interaction">
</task>
</taskmodel>
7.3.18 Reach 2nd floor button

<taskmodel>

<task id="st0task0" name="Reach_2nd_floor_button" type="interaction">
</task>
</taskmodel>

7.3.19 Push 2nd floor button

<taskmodel>

<task id="st0task0" name="Push_2nd_floor_button" type="interaction">
<task id="st0task1" name="Push(object:button)(means:finger)(modality:motor)"
</task>
</taskmodel>
7.3.20 Walk outside lift

<taskmodel>

<task id="st0task0" name="Walk_outside_lift" type="interaction">
<task id="st0task1" name="Walk(object:outside_lift)(means:feet)(modality:motor)"
<task id="st0task2"
name="Rool_wheelchair(object:outside_lift)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.21 Locate office door

<taskmodel>

<task id="st0task0" name="Locate_door" type="interaction">
<task id="st0task1" name="See(object:door)(means:eyes)(modality:vision)"
<task id="st0task2" name="Touch(object:door)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.22 Walk to office door

<taskmodel>

<task id="st0task0" name="Walk_to_door" type="interaction">
<task id="st0task1" name="Walk(object:door)(means:feet)(modality:motor)"
<task id="st0task2" name="Rool_wheelchair(object:door)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.23 Locate door handle

<taskmodel>

<task id="st0task0" name="Locate_door_handle" type="interaction">
<task id="st0task1" name="See(object:door_handle)(means:eyes)(modality:vision)"
<task id="st0task2" name="Touch(object:door_handle)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.24 Reach door handle

<taskmodel>

<task id="st0task0" name="Reach_door_handle" type="interaction">
<task id="st0task1" name="Reach(object:door_handle)(means:hands)(modality:motor)"
</task>
</taskmodel>


<taskmodel>

<task id="st0task0" name="Grasp_door_handle" type="interaction">
<task id="st0task1" name="Grasp(object:door_handle)(means:hands)(modality:motor)"
</task>
</taskmodel>

<taskmodel>

<task id="st0task0" name="Grasp_door_handle" type="interaction">
<task id="st0task1" name="Grasp(object:door_handle)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.27 Push door handle

<taskmodel>

<task id="st0task3" name="Push_door_handle" type="interaction">
<task id="st0task4" name="Push(object:door_handle)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.28 Push door

<taskmodel>

<task id="st0task3" name="Push_door" type="interaction">
<task id="st0task4" name="Push(object:door)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.29 Release door handle

<taskmodel>

<task id="st0task3" name="Release_door_handle" type="interaction">
<task id="st0task4" name="Push(object: door_handle)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.30 Locate chair

<taskmodel>

<task id="st0task0" name="Locate_chair" type="interaction">
<task id="st0task1" name="See(object:chair)(means:eyes)(modality:vision)"
<task id="st0task2" name="Touch(object:chair)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.31 Walk to chair

<taskmodel>

<task id="st0task0" name="Walk_to_chair" type="interaction">
<task id="st0task1" name="Walk(object:chair)(means:feet)(modality:motor)"
<task id="st0task2"
name="Rool_wheelchair(object:chair)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.32 Reach chair

<taskmodel>

<task id="st0task0" name="Reach_chair" type="interaction">
<task id="st0task1" name="Reach(object:chair)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.33 Push chair

<taskmodel>

<task id="st0task0" name="Push_chair" type="interaction">
<task id="st0task1" name="Push(object:chair)(means:hands)(modality:motor)"
<task id="st0task2" name="Push(object:chair)(means:feet)(modality:motor)"
</task>
</taskmodel>

7.3.34 Sit on chair

<taskmodel>

<task id="st0task0" name="Sit_on_chair" type="interaction">
<task id="st0task1" name="Sit(object:chair)(means:body)(modality:motor)"
</task>
</taskmodel>
7.3.35 Locate drawer

<taskmodel>

<task id="st0task0" name="Locate_drawer" type="interaction">
<task id="st0task1" name="See(object:drawer)(means:eyes)(modality:vision)"
<task id="st0task2" name="Touch(object:drawer)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.36 Reach drawer

<taskmodel>

<task id="st0task0" name="Reach_drawer_handle" type="interaction">
<task id="st0task1" name="Reach(object:drawer_handle)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.37 Grasp drawer handle

<taskmodel>

<task id="st0task0" name="Reach_drawer_handle" type="interaction">
<task id="st0task1" name="Reach(object:drawer_handle)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.38 Pull drawer handle

<taskmodel>

<task id="st0task0" name="Pull_drawer_handle" type="interaction">
<task id="st0task1" name="Pull(object:drawer_handle)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.39 Locate power button

<taskmodel>

<task id="st0task0" name="Locate_power_button" type="interaction">
</task>
</taskmodel>

7.3.40 Reach power button

<taskmodel>

<task id="st0task0" name="Reach_power_button" type="interaction">
</task>
</taskmodel>
7.3.41 Push power button

<taskmodel>

<task id="st0task0" name="Push_power_button" type="interaction">
<task id="st0task1" name="Push(object:button)(means:finger)(modality:motor)"
</task>
</taskmodel>

7.3.42 Locate computer screen

<taskmodel>

<task id="st0task0" name="Locate_computer_screen" type="interaction">
<task id="st0task1" name="See(object:computer_screen)(means:eyes)(modality:vision)"
<task id="st0task2"
name="Touch(object:computer_screen)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.43 Reach computer screen

<taskmodel>

<task id="st0task0" name="Reach_computer_screen" type="interaction">
<task id="st0task1"
name="Reach(object:computer_screen)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.44 Grasp computer screen

<taskmodel>

<task id="st0task0" name="Grasp_computer_screen" type="interaction">
<task id="st0task1"
name="Grasp(object:computer_screen)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.45 Pull computer screen closer

<taskmodel>

<task id="st0task0" name="Pull_computer_screen_closer" type="interaction">
<task id="st0task1" name="Pull(object:computer_screen)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.46 Push computer screen farther

<taskmodel>

<task id="st0task0" name="Push_computer_screen_farther" type="interaction">
<task id="st0task1" name="Push(object:computer_screen)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.47 Pull computer screen lower

<taskmodel>

<task id="st0task0" name="Pull_computer_screen_lower" type="interaction">
<task id="st0task1" name="Pull(object:computer_screen)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.48 Push computer screen higher

<taskmodel>

<task id="st0task0" name="Push_computer_screen_higher" type="interaction">
<task id="st0task1" name="Push(object:computer_screen)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.49 Locate device

<taskmodel>

<task id="st0task0" name="Locate_device" type="interaction">
<task id="st0task1" name="See(object:device)(means:eyes)(modality:vision)"
<task id="st0task2" name="Touch(object:device)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.50 Reach device

<taskmodel>

<task id="st0task0" name="Reach_device" type="interaction">
<task id="st0task1" name="Reach(object:device)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.51 Grasp device

<taskmodel>

<task id="st0task0" name="Grasp_device" type="interaction">
<task id="st0task1" name="Grasp(object:device)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.52 Push device button

<taskmodel>

<task id="st0task0" name="Push_device_button" type="interaction">
<task id="st0task1" name="Push(object: device_button)(means:finger)(modality:motor)"
</task>
</taskmodel>
7.3.53 Leave chair

<taskmodel>

<task id="st0task0" name="Leave_chair" type="interaction">
<task id="st0task1" name="Stand_up(object:chair)(means:body)(modality:motor)"
</task>
</taskmodel>

7.3.54 Locate storage area

<taskmodel>

<task id="st0task0" name="Locate_storage_area" type="interaction">
<task id="st0task1" name="See(object:storage_area)(means:eyes)(modality:vision)"
<task id="st0task2" name="Touch(object:storage_area)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.55 Walk to storage area

<taskmodel>

<task id="st0task0" name="Walk_to_storage_area" type="interaction">
<task id="st0task1" name="Walk(object:storage_area)(means:feet)(modality:motor)"
<task id="st0task2"
name="Rool_wheelshelf(object:storage_area)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.56 Locate stored paper

<taskmodel>

<task id="st0task0" name="Locate_stored_paper" type="interaction">
<task id="st0task1" name="See(object:stored_paper)(means:eyes)(modality:vision)"
<task id="st0task2" name="Touch(object:stored_paper)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.57 Reach stored paper

<taskmodel>

<task id="st0task0" name="Reach_stored_paper" type="interaction">
<task id="st0task1" name="Reach(object:stored_paper)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.58 Grasp stored paper

<taskmodel>

<task id="st0task0" name="Grasp_stored_paper" type="interaction">
<task id="st0task1" name="Grasp(object:stored_paper)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.59 Locate printing tray

<taskmodel>

<task id="st0task0" name="Locate_printing_tray" type="interaction">
<task id="st0task1" name="See(object:printing_tray)(means:eyes)(modality:vision)"
<task id="st0task2" name="Touch(object:printing_tray)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.60 Walk to printer area

<taskmodel>

<task id="st0task0" name="Walk_to_printer_area" type="interaction">
<task id="st0task1" name="Walk(object:printer_area)(means:feet)(modality:motor)"
<task id="st0task2"
name="Roll_wheelchair(object:printer_area)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.61 Reach tray

<taskmodel>

<task id="st0task0" name="Reach_tray" type="interaction">
<task id="st0task1" name="Reach(object: tray)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.62 Grasp tray

<taskmodel>

<task id="st0task0" name="Reach_ tray" type="interaction">
<task id="st0task1" name="Reach(object: tray)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.63 Pull tray

<taskmodel>

<task id="st0task0" name="Pull_tray" type="interaction">
<task id="st0task1" name="Pull(object: tray)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.64 Release paper in tray

<taskmodel>

<task id="st0task0" name="Release_paper_in_tray" type="interaction">
<task id="st0task1" name="Release(object:stored_paper)(means:hand)(modality:motor)"
</task>
</taskmodel>
7.3.65 Push tray

<taskmodel>

<task id="st0task0" name="Push_tray" type="interaction">
<task id="st0task1" name="Push(object: tray)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.66 Locate printer

<taskmodel>

<task id="st0task0" name="Locate_printer" type="interaction">
<task id="st0task1" name="See(object:printer)(means:eyes)(modality:vision)"
<task id="st0task2" name="Touch(object:printer)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.67 Reach printed document

<taskmodel>

<task id="st0task0" name="Reach_printed_document" type="interaction">
<task id="st0task1"
name="Reach(object:printed_document)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.68 Grasp printed document

<taskmodel>

<task id="st0task0" name="Grasp_printed_document" type="interaction">
<task id="st0task1"
name="Grasp(object:printed_document)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.69 Locate dossier

<taskmodel>

<task id="st0task0" name="Locate_dossier" type="interaction">
<task id="st0task1" name="See(object:dossier)(means:eyes)(modality:vision)"
<task id="st0task2" name="Touch(object:dossier)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.70 Walk to dossier

<taskmodel>

<task id="st0task0" name="Walk_to_dossier" type="interaction">
<task id="st0task1" name="Walk(object:dossier)(means:feet)(modality:motor)"
<task id="st0task2"
name="Rool_wheelshelf(object:dossier)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.71 Reach dossier

<taskmodel>

<task id="st0task0" name="Reach_dossier" type="interaction">
<task id="st0task1" name="Reach(object:dossier)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.72 Grasp dossier

<taskmodel>

<task id="st0task0" name="Grasp_dossier" type="interaction">
<task id="st0task1" name="Grasp(object:dossier)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.73 Bring dossier down

<taskmodel>

<task id="st0task0" name="Bring_dossier_down" type="interaction">
<task id="st0task1" name="Move(object:dossier)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.74 Open Dossier

<taskmodel>

<task id="st0task0" name="Open_dossier" type="interaction">
<task id="st0task1" name="Move(object:dossier_cover)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.75 Release printed document in dossier

<taskmodel>

<task id="st0task0" name="Release_printed_document_in_dossier" type="interaction">
<task id="st0task1"
name="Release(object:printed_document)(means:hand)(modality:motor)"
</task>
</taskmodel>

7.3.76 Close dossier

<taskmodel>

<task id="st0task0" name="Close_dossier" type="interaction">
<task id="st0task1" name="Move(object:dossier_cover)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.77 Locate shelf

<taskmodel>

<task id="st0task0" name="Locate_shelf" type="interaction">
<task id="st0task1" name="See(object:shelf)(means:eyes)(modality:vision)"
<task id="st0task2" name="Touch(object:shelf)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.3.78 Walk to shelf

<taskmodel>

<task id="st0task0" name="Locate_shelf" type="interaction">
<task id="st0task1" name="See(object:shelf)(means:eyes)(modality:vision)"
<task id="st0task2" name="Touch(object:shelf)(means:hands)(modality:motor)"
</task>
</taskmodel>
7.3.79 Lift dossier to shelf

<taskmodel>

<task id="st0task0" name="Lift_dossier_to_shelf" type="interaction">
<task id="st0task1" name="Move(object:dossier)(means:hands)(modality:motor)"
</task>
</taskmodel>

7.4 Collaborative tools Simulation Models

7.4.1 File upload and editing
<taskmodel>

<task id="st0task0" name="File_Upload_Editing" type="abstraction">
<task id="st0task1" name="Select_File_Upload_menu_item" type="abstraction"/>
<task id="st0task2" name="Select_file_to_upload" type="abstraction"/>
<task id="st0task3" name="Click_upload_button" type="abstraction"/>
<task id="st0task4" name="Get_aware_of_File_uploaded_message" type="abstraction"/>
<task id="st0task5" name="Select_an_uploaded_file" type="abstraction"/>
<task id="st0task6" name="Select_edit_file_from_menu" type="abstraction"/>
<task id="st0task7" name="Insert_text_in_the_file" type="abstraction"/>
<task id="st0task8" name="Locate_and_click_print_button" type="abstraction"/>
<task id="st0task10" name="Get_aware_of_message_out_of_paper" type="abstraction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.4.2 Create Discussion

<taskmodel>

<task id="st0task0" name="Create_discussion" type="abstraction">
<task id="st0task1" name="Select_create_new_discussion_from_menu"
type="abstraction"/>
<task id="st0task2" name="Insert_title" type="abstraction"/>
<task id="st0task3" name="Locate_and_click_post_button" type="abstraction"/>
<task id="st0task4" name="Get_aware_of_discussion_created_message"
<task id="st0task5" name="Select_post_item_from_menu" type="abstraction"/>
<task id="st0task6" name="Insert_text" type="abstraction"/>
<task id="st0task7" name="Get_aware_of_item_posted_message" type="abstraction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.4.3 Realise a teleconference

<taskmodel>

<task id="st0task0" name="Realise_a_teleconference" type="abstraction">
<task id="st0task1" name="Locate_and_click_accept_button" type="abstraction"/>
<task id="st0task2" name="Locate_volume_slider_and_adjust_volume"
<task id="st0task3" name="Communicate_with_other_participants" type="abstraction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.5 Collaborative tools Task Models

7.5.1 Select File Upload from menu
<taskmodel>

<task id="st0task0" name="Select_file_upload_from_menu" type="abstraction">
<task id="st0task1" name="Locate_file_menu" type="interaction"/>
<task id="st0task2" name="Move_mouse" type="interaction"/>
<task id="st0task3" name="Click_mouse_button" type="interaction"/>
<task id="st0task4" name="Locate_file_upload_menu_item" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.5.2 Select file to upload

<taskmodel>

<task id="st0task0" name="Select_file_to_upload" type="abstraction">
<task id="st0task1" name="Locate_file_name" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>
7.5.3 Locate and click Upload button

<taskmodel>

<task id="st0task0" name="Locate_and_click_upload_button" type="abstraction">
<task id="st0task1" name="Locate_upload_button" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.5.4 Get aware of File uploaded message

<taskmodel>

<task id="st0task0" name="Get_aware_of_file_uploaded_message" type="abstraction">
<task id="st0task1" name="Locate_file_uploaded_message" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>
7.5.5 Select an uploaded file

<taskmodel>

<task id="st0task0" name="Select_an_uploaded_file" type="abstraction">
<task id="st0task1" name="Locate_uploaded_filename" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.5.6 Select Edit file from menu

<taskmodel>

<task id="st0task0" name="Select_edit_file_from_menu" type="abstraction">
<task id="st0task1" name="Locate_file_menu" type="interaction"/>
<task id="st0task4" name="Locate_edit_file_menu_item" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.5.7 Insert text in the file

<taskmodel>

<task id="st0task0" name="Insert_text_in_the_file" type="abstraction">
<task id="st0task1" name="Locate_inserted_text" type="interaction"/>
<task id="st0task4" name="Enter_text" type="abstraction">
<task id="st0task5" name="Press_keyboard_key" type="interaction"/>
<task id="st0task6" name="Release_keyboard_key" type="interaction"/>
</task>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
<iteration>
</iteration>
<enabling>
</enabling>
</taskmodel>

7.5.8 Locate and click Print button

<taskmodel>

<task id="st0task0" name="Locate_and_click_print_button" type="abstraction">
<task id="st0task1" name="Locate_print_button" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>
7.5.9 Get aware of message Out of paper

<taskmodel>

<task id="st0task0" name="Get_aware_of_message_out_of_paper" type="abstraction">
<task id="st0task1" name="Locate_message_out_of_paper" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.5.10 Select Create new discussion from menu

<taskmodel>

<task id="st0task0" name="Select_create_new_discussion_from_menu"
type="abstraction">
<task id="st0task1" name="Locate_discussion_menu" type="interaction"/>
<task id="st0task4" name="Locate_create_new_discussion_menu_item"
</task>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.5.11 Insert title

<taskmodel>

<task id="st0task0" name="Insert_title" type="abstraction">
<task id="st0task1" name="Locate_title_entry_field" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>
7.5.12 Locate and click Post button

<taskmodel>

<task id="st0task0" name="Locate_and_click_post_button" type="abstraction">
<task id="st0task1" name="Locate_post_button" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.5.13 Get aware of Discussion created message

<taskmodel>

<task id="st0task0" name="Get_aware_of_discussion_created_message"
type="abstraction">
<task id="st0task1" name="Locate_discussion_created_message" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.5.14 Select Post item from menu

<taskmodel>

<task id="st0task0" name="Select_post_item_from_menu" type="abstraction">
<task id="st0task1" name="Locate_Discussion_menu" type="interaction"/>
<task id="st0task4" name="Locate_post_item_menu_item" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.5.15 Insert text

<taskmodel>

<task id="st0task0" name="Insert_text" type="abstraction">
<task id="st0task1" name="Locate_text_field" type="interaction"/>
<task id="st0task5" name="Enter_text" type="abstraction">
<task id="st0task6" name="Press_keyboard_key" type="interaction"/>
<task id="st0task7" name="Release_keyboard_key" type="interaction"/>
</task>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
<iteration>
</iteration>
<enabling>
</enabling>
</taskmodel>

7.5.16 Get aware of Item posted message

<taskmodel>

<task id="st0task0" name="Get_aware_of_item_posted_message" type="abstraction">
<task id="st0task1" name="Locate_item_posted_message" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>
7.5.17 Locate and click Accept button

<taskmodel>

<task id="st0task0" name="Locate_and_click_accept_button" type="abstraction">
<task id="st0task1" name="Locate_accept_button" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.5.18 Locate volume slider and adjust volume

<taskmodel>

<task id="st0task0" name="Locate_and_adjust_volume" type="abstraction">
<task id="st0task1" name="Locate_volume_dialog_box" type="interaction"/>
<task id="st0task4" name="Hear_sound" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>
7.5.19 Communicate with other participants

<taskmodel>

<task id="st0task0" name="Locate_and_adjust_volume" type="abstraction">
<task id="st0task1" name="Locate_volume_dialog_box" type="interaction"/>
</task>
<enabling>
</enabling>
<enabling>
</enabling>
</taskmodel>

7.6 Collaborative tools Multimodal Interaction Models

7.6.1 Move Mouse
<taskmodel>

<task id="st0task0" name="Move_mouse" type="interaction">
<task id="st0task1" name="Move(object:mouse)(means:hands)(modality:motor)"
<task id="st0task2" name="Speak(object:voice_command)(means:mouth)(modality:speech)"
</task>
</taskmodel>
7.6.2 Click Mouse Button

<taskmodel>

<task id="st0task0" name="Click_mouse_button" type="interaction">
<task id="st0task1"
name="Click(object:mouse_button_left)(means:finger)(modality:motor)"
<task id="st0task2" name="Speak(object:voice_command)(means:mouth)(modality:speech)"
</task>
</taskmodel>

7.6.3 Push Keyboard key

<taskmodel>

<task id="st0task0" name="Push_keyboard_key" type="interaction">
<task id="st0task1" name="Push(object:keyboard_key)(means:finger)(modality:motor)"
</task>
</taskmodel>
7.6.4 Release Keyboard key

<taskmodel>

<task id="st0task0" name="Release_keyboard_key" type="interaction">
<task id="st0task1"
name="Release(object:keyboard_key)(means:finger)(modality:motor)"
</task>
</taskmodel>

7.6.5 Locate file menu

<taskmodel>

<task id="st0task0" name="Locate_file_menu" type="interaction">
<task id="st0task1" name="See(object:file_menu)(means:eyes)(modality:vision)"
</task>
</taskmodel>
7.6.6 Locate upload file menu item

<taskmodel>

<task id="st0task0" name="Locate_ upload_file_menu_item" type="interaction">
<task id="st0task1" name="See(object:
upload_file_menu_item)(means:eyes)(modality:vision)" type="interaction"/>
</task>
</taskmodel>

7.6.7 Locate upload file name

<taskmodel>

<task id="st0task0" name="Locate_file_name" type="interaction">
<task id="st0task1" name="See(object:file_name)(means:eyes)(modality:vision)"
</task>
</taskmodel>
7.6.8 Locate upload button

<taskmodel>

<task id="st0task0" name="Locate_upload_button" type="interaction">
<task id="st0task1" name="See(object:upload_button)(means:eyes)(modality:vision)"
</task>
</taskmodel>

7.6.9 Locate file upload menu item

<taskmodel>

<task id="st0task0" name="Locate_file_upload_menu_item" type="interaction">
<task id="st0task1"
name="See(object:file_upload_menu_item)(means:eyes)(modality:vision)"
</task>
</taskmodel>
7.6.10 Locate edit file menu

<taskmodel>

<task id="st0task0" name="Locate_edit_file_menu_item" type="interaction">
<task id="st0task1"
name="See(object:edit_file_menu_item)(means:eyes)(modality:vision)"
</task>
</taskmodel>

7.6.11 Locate inserted text

<taskmodel>

<task id="st0task0" name="Locate_inserted_text" type="interaction">
<task id="st0task1" name="See(object:inserted_text)(means:eyes)(modality:vision)"
</task>
</taskmodel>
7.6.12 Locate print button

<taskmodel>

<task id="st0task0" name="Locate_print_button" type="interaction">
<task id="st0task1" name="See(object:print_button)(means:eyes)(modality:vision)"
</task>
</taskmodel>

7.6.13 Locate message out of paper

<taskmodel>

<task id="st0task0" name="Locate_message_out_of_paper" type="interaction">
<task id="st0task1"
name="See(object:message_out_of_paper)(means:eyes)(modality:vision)"
</task>
</taskmodel>
7.6.14 Locate discussion menu

<taskmodel>

<task id="st0task0" name="Locate_discussion_menu" type="interaction">
<task id="st0task1" name="See(object:discussion_menu)(means:eyes)(modality:vision)"
<task id="st0task2"
name="Hear(object:discussion_menu_sound)(means:ears)(modality:hearing)"
</task>
</taskmodel>

7.6.15 Locate create new discussion menu item

<taskmodel>

<task id="st0task0" name="Locate_create_new_discussion_menu_item"
type="interaction">
<task id="st0task1"
name="See(object:create_new_discussion_menu_item)(means:eyes)(modality:vision)"
<task id="st0task2"
name="Hear(object:create_new_discussion_menu_item_sound)(means:ears)(modality:hearin
g)" type="interaction"/>
</task>
</taskmodel>
7.6.16 Locate title entry field

<taskmodel>

<task id="st0task0" name="Locate_title_entry_field" type="interaction">
<task id="st0task1"
name="See(object:title_entry_field)(means:eyes)(modality:vision)"
<task id="st0task2"
name="Hear(object:title_entry_field_sound)(means:ears)(modality:hearing)"
</task>
</taskmodel>

7.6.17 Locate post button

<taskmodel>

<task id="st0task0" name="Locate_post_button" type="interaction">
<task id="st0task1" name="See(object:post_button)(means:eyes)(modality:vision)"
<task id="st0task2"
name="Hear(object:post_button_sound)(means:ears)(modality:hearing)"
</task>
</taskmodel>
7.6.18 Locate discussion created message

<taskmodel>

<task id="st0task0" name="Locate_discussion_created_message" type="interaction">
<task id="st0task1"
name="See(object:discussion_created_message)(means:eyes)(modality:vision)"
<task id="st0task2"
name="Hear(object:discussion_created_message_sound)(means:ears)(modality:hearing)"
</task>
</taskmodel>

7.6.19 Locate post item menu item

<taskmodel>

<task id="st0task0" name="Locate_post_item_menu_item" type="interaction">
<task id="st0task1"
name="See(object:_post_item_menu_item)(means:eyes)(modality:vision)"
<task id="st0task2"
name="Hear(object:post_item_menu_item_sound)(means:ears)(modality:hearing)"
</task>
</taskmodel>
7.6.20 Locate text field

<taskmodel>

<task id="st0task0" name="Locate_text_field" type="interaction">
<task id="st0task1" name="See(object:text_field)(means:eyes)(modality:vision)"
<task id="st0task2"
name="Hear(object:text_field_sound)(means:ears)(modality:hearing)"
</task>
</taskmodel>

7.6.21 Locate item posted message

<taskmodel>

<task id="st0task0" name="Locate_item_posted_message" type="interaction">
<task id="st0task1"
name="See(object:item_posted_message)(means:eyes)(modality:vision)"
<task id="st0task2"
name="Hear(object:item_posted_message_sound)(means:ears)(modality:hearing)"
</task>
</taskmodel>
7.6.22 Locate accept button

<taskmodel>

<task id="st0task0" name="Locate_accept_button" type="interaction">
<task id="st0task1" name="See(object:accept_button)(means:eyes)(modality:vision)"
<task id="st0task2"
name="Hear(object:accept_button_sound)(means:ears)(modality:hearing)"
</task>
</taskmodel>

7.6.23 Locate volume dialog box

<taskmodel>

<task id="st0task0" name="Locate_volume_dialog_box" type="interaction">
<task id="st0task1"
name="See(object:volume_dialog_box)(means:eyes)(modality:vision)"
<task id="st0task2"
name="Hear(object:volume_dialog_box_sound)(means:ears)(modality:hearing)"
</task>
</taskmodel>
7.6.24 Hear sound

<taskmodel>

<task id="st0task0" name="Hear_sound" type="interaction">
<task id="st0task1" name="Hear(object:sound)(means:ears)(modality:hearing)"
<task id="st0task2" name="See(object:sound_to_text)(means:eyes)(modality:vision)"
</task>
</taskmodel>

7.6.25 Speak to other participants

<taskmodel>

<task id="st0task0" name="Speak_to_other_participants" type="interaction">
<task id="st0task1" name="Speak(object:sound)(means:mouth)(modality:speech)"
</task>
</taskmodel>

Veritas D2.4.1

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Veritas D2.4.1

Caricato da

Copyright:

Formati disponibili

Accessible and Assistive ICT

Virtual and Augmented Environments and Realistic User Interactions To achieve

Simulation models for the workplace design

Deliverable No. D2.4.1

Version History table

1.0 November 2011: First draft version produced (Hypertech)

1.1 November 2011: Collaborative Tools sections included (Byte)

1.2 December 2011: Revision and improvements performed; Document

December 2011 3 Hypertech

December 2011 4 Hypertech

4.1.2 Definition of subtask. ..................................................................................................... 50

December 2011 5 Hypertech

7.3.11 Locate call button ........................................................................................................ 133

December 2011 6 Hypertech

7.3.69 Locate dossier ............................................................................................................. 161

December 2011 7 Hypertech

7.6.22 Locate accept button ................................................................................................... 193

December 2011 8 Hypertech

December 2011 9 Hypertech

December 2011 10 Hypertech

December 2011 11 Hypertech

Finally, we composed an overview on the integration of Simulation models to the Veritas

December 2011 12 Hypertech

December 2011 13 Hypertech

2 UCD, Guidelines and Requirements in the

2.2 UCD in Workplace Design

Figure 2-1: Common musculoskeletal disorders at office workstations

December 2011 14 Hypertech

interface. The standard prEN-1005-4: Safety of machinery. Human physical performance

The following ISO standards are relevant:

Australian Standard 3590.2-1990 Screen based Workstations

2.2.1 Lighting and Sound

Older workers may require stronger lighting [UTS guidelines].

Glare should be minimized [UTS guidelines].

Illumination should be even between adjacent areas [UTS guidelines].

December 2011 15 Hypertech

2.2.2 Furniture and Storage

Workers should avoid excessive bending or reaching to gather or store items on

2.2.3 Visual Display Unit (VDU)

No more than six colours should be simultaneously displayed [UTS guidelines].

December 2011 16 Hypertech

2.2.4 Document Holders

The document holders should be placed at a comfortable viewing distance in line

The keyboard design (either split, compact, "Internet" or "ergonomic") should be

December 2011 17 Hypertech

2.2.6 Mouse Controls

Controls that allow a variety of finger movements instead of holding a position on a

If extensive mouse use is required, it is advisable to provide for easy alternation

December 2011 18 Hypertech

2.2.9 Equipment positioning on desktop

December 2011 19 Hypertech

2.2.11 Office Accessories and Non Routine Processes

December 2011 20 Hypertech

2.3 UCD in Collaborative tools

December 2011 21 Hypertech

0.0 5.0 10.0 15.0 20.0 25.0 30.0

Figure 2-3: Percentage of events per application area.

2.3.1 A survey of preferences among office workers with disabilities

A total of 33 completed questionnaires have been collected. 16 of the respondents were

December 2011 22 Hypertech

Figure 2-4: Usage of collaborative tools among the sample

December 2011 23 Hypertech

Figure 2-5: Frequency of usage of collaborative tools among the sample