1. Cloud platforms Lead to Open and Universal access for people with Disabilities and for All www.cloud4all.eu Pofile initialisation and management Teleconference 13.11.12

2. Agenda 1.General Aspects on profile initialisation and management 2.High impact variables 3.Use context profile initialization/ management 4.Process/ screen flow for initialization and management 5.Next steps for ID102.1 and 1 st annual review

3. General aspects on profile initialisation and management Review of the results of the user workshop in Berlin Main requirements identified Based on requirements first concept on profile initialisation and management Second user workshop on Friday 16th of November to validate concept LoFi tests at Fraunhofer Laboratory

4. Requirements Profile Initialisation Users are willing to spend a lot of time on profile initialisation, if they have an added value afterwards, e.g high accessiblity, high usability. Users would use a personal device (e.g. personal computer, smartphone, tablet PC) for profile initialisation that is already adjusted to the user needs/ already equipped with the needed AT. There should be two modes for profile initialisation – an expert mode for advanced users and a simple mode for users with cognitive difficulties and low computer literacy. Profile initialisation could be handled comparable to an application store: different alternatives for preference settings are offered and can be accepted or rejected

5. Requirements Users would prefer a step by step approach for profile initialisation (e.g. dialogue wizard), where user interface parameters can be adjusted to the user’s needs by selecting an option out of an defined number of proposed options or by adjusting the value for an interface parameter (simple and advanced mode). users want to take over the device settings of the device used for initialization as default profile. If the user wants neither the wizard or to take over the device settings, the profile should be left blank until the user changes the setting of a parameter Users would prefer to set a ‘rough’ profile first and to adjust the preference setting afterwards in more detail.

6. Requirements Profile Management Clearly structured. Maximum of three levels within the menu hierarchy. WYSIWYG – when changing a preference setting a preview of the change should be given. Clear label of menu items and clear categorisation of variables within the menu A filter function should be provided to switch between a view of the main preferences and all preferences. Browser based. Users would like to manage profiles and to change preference settings of public devices via remote, using a personal device (e.g. preferences settings for a ticket machine are assessed via a persona smartphone using near-field-communication).

7. Concept Profile initialisation Wizard high impact preferences Device settings as default profile Blank profile Use case  The device is not set up for the user  Caregiver is initialising the profile  User does not know his/ her needs and preferences Use case  The device is is already adapted to the user needs Outcome  Profile with high impact variables = global profile  all other variables are blank Use Case  User wants to adjust a specific variable (not part of the high impact variables)  User wants to skip the initialisation process Outcome  Profile filled in with settings of the device used for initialisation  High impacts as well as all other variables of the profile have a preference setting value Outcome  Blank profile  Blank variables are handled by the matchmaker (e.g. use default of the device)

8. General concept reduce all adaptable interface variables to a defined number of variables that are presented to the user as preference settings for profile initialisation They are fundamental to make an interface accessible/ perceivable. These variables/ preferences will be presented within the Discovery Aid Wizard and will be provided in the filtered view of the profile management editor. First set of high impact variables was generated on expert decision using the document „Unified Table D101“ (first with focus on elderly users) This set will be validated within a requirement analysis with users High impact variables

9. Concept Profile management Cloud manageGeneral settings  Profile selection (device, platform, global  Search for end devices within reach  Preference settings (high impact and all)  Privacy settings  Advanced functionalities (recommendations, sharing among peers )

10. Profiles Global profile Without device specific conditional preferences Will be used by the matchmaker for accessing new devices Device/ platform specific profile With device specific conditional preferences Will be used by the matchmaker for accessing similar devices/ platforms Profiles Profiles within management tool refers to a user view of device/platform specific preference settings (independent of the reprasentation in the registry/ ontology) Device specific profile can be generated by accessing a new device (matchmaker will derive preference settings for new device) Search for a device within area and set preferences or define which device preference settings should be used for the new device (advanced) New profile Search for device Define new profile (advanced)

11. User workshop and LoFi tests User workshop Requirement analysis with focus on validation of „high impacts“ Clustering of user interface variables (card sorting) LoFi user tests Comparitive evaluation of different paper mock ups with focus on Overall usability Menu structure

12. ID 102.1 Next steps: Input from the workshop and results of the user testing to ID102.1 until Wednesday next week (21 st of November) Pending issues to be discussed with architecture team and matchmaker team (to when?) What should be ready for Madrid What should be ready for the first annual review?