1Matchmaker Evaluation protocol



Download 134.81 Kb.
Date conversion25.06.2017
Size134.81 Kb.

1Matchmaker Evaluation protocol

1.1General Overview of the Matchmaker Evaluation


The goal of the matchmaker evaluation is to gather data on the accuracy of matchmaker inferences by comparing the inference outcomes with the settings chosen by a “human matchmaker”, i.e. a person who has the expertise that is required to set up a system (accessibility features of the operating system, assistive technologies and any other relevant applications) for a specific type of user group.

The “human matchmaker” or expert will be given a pre-defined preference set that will be used with a corresponding device reporter file, and will set up the system to match the settings in the preference set. The preference sets given to the experts will use common terms only. The settings and solutions that the expert chooses will be logged so that they can later be compared with the settings that the matchmakers would infer.

The test facilitator will support the expert while they are configuring the system and tweaking its settings. The test facilitator must make sure that the expert finds all the settings that are needed to adapt the system; this must be done to prevent that difficulties in finding the right settings becomes a confounding variable in the evaluation process. In other words, the test facilitator can guide the expert to the location of the settings, but the decisions about the values of these settings must be left to the expert.

This evaluation process does not require the test facilitator or the expert to choose and run a matchmaker: the matchmaker inferences can be generated separately by the matchmaker teams, and the resulting settings can be compared with those from the expert evaluation at any time before or after the expert evaluation. This process also has another advantage: each expert evaluation can be compared with both matchmakers, whereas the second pilot phase could compare each user’s settings with only one matchmaker.


1.2Technical preconditions


For the matchmaker evaluation, each pilot site needs the following equipment and software:

One PC with Windows 7 and the following applications:



    1. NVDA

    2. SuperNova Access Suite 13. (i.e. not the most recent version!)

    3. JAWS

    4. Read&Write Gold

    5. Google Chrome with the extension Cloud4Chrome

    6. A bookmark for WebAnywhere should be easy to find in the browser(s), and/or a desktop shortcut to WebAnywhere should be available

    7. Optionally, a program for taking screenshots, e.g. IrfanView (freeware: http://www.irfanview.com/)

One PC with a freshly installed version of Fedora Linux 21 with Gnome. (Orca is installed by default with this Fedora version). You can download this version from https://getfedora.org/en/workstation/download/. In addition to the default programs and tools, the following will need to be installed:

    1. The GPII real-time framework. See the installation instructions at http://wiki.gpii.net/w/Cloud4all_Pilot_3_-_Set_up_and_installation#Installing_GPII_on_Fedora.

    2. The dconf-editor and the gnome-tweak-tool (see the above installation instructions).

    3. Optionally, GIMP for taking screenshots (see the above installation instructions).

An Android smartphone (see the requirements for the auto-configuration use cases).

The guide to the settings of the SP3 solutions. [@@link to be provided].

The spreadsheet for logging the settings tweaked by the expert user. [@@to be created]

The list of tokens to be used in this test and human-readable descriptions of the preference in the matchmaker payloads.

The device reporter files to be used in this test.

Note: This test does not require the PMT or the PCP, nor USB sticks or NFC cards to transfer a token from platform A to platform B.


1.3Test Protocol for Matchmaker Evaluation


This test protocol uses the following terminology:

The person who performs the evaluation is called the “expert”. The protocol makes no distinction between experts with or without disabilities.

The person who supervises the evaluation and helps the expert when needed is called the “test facilitator”.

Each instance of the expert evaluating the system using a specific NP set (and device reporter file) is called a “test run”. Each expert can perform one or more test runs, each time with a different NP set (and its accompanying device reporter file).

The platform that the expert adapts is called the “target platform”. In contrast to the matchmaker evaluation process in the second pilot phase, this protocol does not use the concepts “platform A” and “platform B”.

The matchmaker evaluation protocol is broken down into 13 test cases, each using a specific NP set and device reporter file (see below). In total, there should be at least 85 test runs, which each test cases being run at least 6 times. (Running each test case 7 times would result in 91 test runs.)

Note: Most of the payloads contain a language preference (e.g. for synthetic speech) that is set to English; this settings needs to be adapted to the language of the test site.

1.3.1Preliminary Steps


The test facilitator welcomes the expert and informs them about the testing venue (toilets, exits, etc.).

The test facilitator gives a general description of the main objective and the test purpose (i.e. we are here to test the preliminary outcomes of Cloud4all system). It is very important to explain that the system is to be tested, not the participant (i.e. test person)! Similarly, it is important to clarify that the usability and the accessibility of the SP3 solutions are not the object of the evaluation.

The test facilitator hands the consent form to the expert and ask them to read it and sign two copies (if this has not happened already during the screening procedure). If the participant is not able to read the consent form, the test facilitator assists them to understand its meaning and sign it. The consent form can be found at Annex B1: Cloud4all Informed Consent (pre-tests).

The test facilitator asks the expert to fill in the pre-test questionnaire for the matchmaker evaluation (@@todo: determine which annexsee ANNEX A. Pre-test questionnaire).

The test facilitator presents the concept of Cloud4all using the video. This video will allow you to provide the participant with the basic information of the project. Since the video of the project is in English you have to be prepared to explain content of the video in the participant’s native language. The video of the project with English subtitles is available at https://www.youtube.com/watch?v=pYNxNN5p45Y. The video of the GPII concept is available at http://gpii.net/node/108.

The participants of the pilots will receive a short training session before the actual tests in order to be informed about the tools that they will use and the scenarios they will perform. The training will be carried out using the ATutor web platform that you will find at this link, http://www.hit-projects.gr/cloud4all/login.php. The training should be about how to adapt settings using the solutions listed in the section on technical preconditions: Windows’ built-in solutions (magnifier, colour inversion, high contrast, cursor size, screen resolution), Linux GNOME’s built-in solutions (Orca, magnifier, high contrast, colour inversion, and some of the settings in the GNOME tweak tool (finer control over text size) and the dconf-editor (i.e. cursor size, magnification over 2000%), NVDA, SuperNova Access Suite, JAWS, Read&Write Gold, Cloud4Chrome and Android.


1.3.2The Evaluation Protocol


Step 1: The test facilitator chooses a matchmaker payload that represents a type of user for which the expert has the necessary expertise to set up the target platform.

Note: if the expert user needs AT to read the preference set and the device reporter file, they may need a separate device to do this. However, this would not be considered as "platform A". The test process only assumes a target platform.

Step 2: The test facilitator gives the payload to the expert and provides a human readable description of both the preferences and the device reporter info. If the local system contains solutions that are not part of the device reporter info, these solutions must not be used to set up the system (e.g. if NVDA is installed, but NVDA is not listed in the device reporter info, the expert must not use it). The expert sets up the solutions and the settings to match the needs and preferences expressed in the preference set. The expert is encouraged to think aloud about his choices and questions. The test facilitator helps the expert find the location of the settings when necessary. [@@We may need a form for the test facilitator to capture the questions, comments and ideas, e.g. when the expert is considering different alternative solutions or settings. @@Add this to the same spreadsheet!]

Step 3: The test facilitator records the resulting settings in a spreadsheet. [@@cf. the spreadsheet mentioned above.]

Step 4. [Will we have a post-test questionnaire here?]


1.3.3Categories of Test Cases


The table below shows how the test cases are distributed over the three platforms and the types of impairments that are covered by the matchmaker evaluation protocol. The test cases for blindness cover only screen reader settings; the other test cases cover features such as magnification, high contrast and (large) font size and sometimes also screen reader settings.




Test cases for blindness only




Test cases for other visual impairments




MS Windows

1a

1b


1c

2





1d

3

4a



6b




Linux GNOME







4b

5b


6a




Android







4c

5a






1.4Description of test cases

1.4.1Test case 1a: Multiple AT Solutions of the Same Class Are Available and Locally Installed.

1.4.1.1Settings and Available Solutions (JSON)


Settings:

"http://registry.gpii.net/common/screenReaderTTSEnabled": true,

"http://registry.gpii.net/common/speechRate": 300,

"http://registry.gpii.net/common/trackingTTS": ["caret"],

"http://registry.gpii.net/common/speakTutorialMessages": false,

"http://registry.gpii.net/common/keyEcho": true,

"http://registry.gpii.net/common/wordEcho": false,

"http://registry.gpii.net/common/announceCapitals": false,

"http://registry.gpii.net/common/punctuationVerbosity": "some",

"http://registry.gpii.net/common/readingUnit": "paragraph",

"http://registry.gpii.net/common/auditoryOutLanguage": "en",

"http://registry.gpii.net/common/pitch": 0.8

Solutions:

{

"id": "com.freedomscientific.jaws"



},

{

"id": "com.baumretec.cobra"



},

{

"id": "com.yourdolphin.supernova-as"



},

{

"id": "org.nvda-project"



}

1.4.1.2Description of the Settings and Solutions


The user of this preference set wants a screen reader that speaks 300 words per minute. The screen reader also tracks the caret (the input position) but not the keyboard focus or the mouse. It echoes every character entered through the keyboard, but not the completed words. It reads most punctuation (but not all). The pitch ("tone") is at 80%.

The user needs synthetic speech and but we have no information about their preferred screen reader, so JAWS, SuperNova or NVDA can be used to help them.


1.4.2Test case 1b: Multiple AT Solutions of the Same Class Are Available, Either Locally or as Cloud-Based Service

1.4.2.1Settings and Available Solutions (JSON)


Settings:

"http://registry.gpii.net/common/screenReaderTTSEnabled": true,

"http://registry.gpii.net/common/speechRate": 300,

"http://registry.gpii.net/common/trackingTTS": ["caret"],

"http://registry.gpii.net/common/speakTutorialMessages": false,

"http://registry.gpii.net/common/keyEcho": true,

"http://registry.gpii.net/common/wordEcho": false,

"http://registry.gpii.net/common/announceCapitals": false,

"http://registry.gpii.net/common/punctuationVerbosity": "some",

"http://registry.gpii.net/common/readingUnit": "paragraph",

"http://registry.gpii.net/common/auditoryOutLanguage": "en",

"http://registry.gpii.net/common/pitch": 0.8

Solutions:

{

"id": "com.freedomscientific.jaws"



},

{

"id": "com.baumretec.cobra"



},

{

"id": "com.yourdolphin.supernova-as"



},

{

"id": "org.nvda-project"



},

{

"id": "webinsight.webAnywhere.windows"



}

1.4.2.2Description of the Settings and Solutions


The user of this preference set wants a screen reader that speaks 300 words per minute. The screen reader also tracks the caret (the input position) but not the keyboard focus or the mouse. It echoes every character entered through the keyboard, but not the completed words. It reads most punctuation (but not all). The pitch ("tone") is at 80%.

The user needs synthetic speech and but we have no information about their preferred screen reader, so JAWS, SuperNova, NVDA or WebAnywhere can be used to help them. (The test facilitator should make the expert aware of WebAnywhere, which is not a locally installed solution.)


1.4.3Test case 1c: Multiple AT Solutions of the Same Class and Sharing Common Functionalities

1.4.3.1Settings and Available Solutions (JSON)


Settings:

"http://registry.gpii.net/common/screenReaderTTSEnabled": true,

"http://registry.gpii.net/common/speechRate": 300,

"http://registry.gpii.net/common/trackingTTS": ["caret"],

"http://registry.gpii.net/common/speakTutorialMessages": false,

"http://registry.gpii.net/common/keyEcho": true,

"http://registry.gpii.net/common/wordEcho": false,

"http://registry.gpii.net/common/announceCapitals": false,

"http://registry.gpii.net/common/punctuationVerbosity": "some",

"http://registry.gpii.net/common/readingUnit": "paragraph",

"http://registry.gpii.net/common/auditoryOutLanguage": "en",

"http://registry.gpii.net/common/pitch": 0.8

Solutions:

{

"id": "com.freedomscientific.jaws"



},

{

"id": "com.baumretec.cobra"



},

{

"id": "com.yourdolphin.supernova-as"



},

{

"id": "org.nvda-project"



},

{

"id": "com.texthelp.readWriteGold"



},

{

"id": "org.chrome.cloud4chrome"



}

1.4.3.2Description of the Settings and Solutions


The user of this preference set wants a screen reader that speaks 300 words per minute. The screen reader also tracks the caret (the input position) but not the keyboard focus or the mouse. It echoes every character entered through the keyboard, but not the completed words. It reads most punctuation (but not all). The pitch ("tone") is at 80%.

The user needs synthetic speech and but we have no information about their preferred screen reader, so JAWS, SuperNova or NVDA or WebAnywhere can be used to help them. In addition, Read&Write Gold and Cloud4Chrome (both solutions provide few screen reader functionalities) are also available on the system.


1.4.4Test case 1d: Multiple AT Solutions or Suites of the Same Class

1.4.4.1Settings and Available Solutions (JSON)


Settings:

"http://registry.gpii.net/common/screenReaderTTSEnabled": true,

"http://registry.gpii.net/common/speechRate": 300,

"http://registry.gpii.net/common/trackingTTS": ["caret"],

"http://registry.gpii.net/common/speakTutorialMessages": false,

"http://registry.gpii.net/common/keyEcho": true,

"http://registry.gpii.net/common/wordEcho": false,

"http://registry.gpii.net/common/announceCapitals": false,

"http://registry.gpii.net/common/punctuationVerbosity": "some",

"http://registry.gpii.net/common/readingUnit": "paragraph",

"http://registry.gpii.net/common/auditoryOutLanguage": "en",

"http://registry.gpii.net/common/pitch": 0.8,

"http://registry.gpii.net/common/magnifierEnabled": true,

"http://registry.gpii.net/common/magnification": 2,

"http://registry.gpii.net/common/tracking": ["cursor"],

"http://registry.gpii.net/common/magnifierPosition": "TopHalf",

"http://registry.gpii.net/common/invertColours": true,

"http://registry.gpii.net/common/showCrosshairs": true

Solutions:

{

"id": "com.freedomscientific.jaws"



},

{

"id": "com.baumretec.cobra"



},

{

"id": "com.yourdolphin.supernova-as"



},

{

"id": "org.nvda-project"



},

{

"id": "com.microsoft.windows.magnifier"



}

1.4.4.2Description of the Settings and Solutions


The user of this preference set wants a screen reader that speaks 300 words per minute. The screen reader also tracks the caret (the input position) but not the keyboard focus or the mouse. It echoes every character entered through the keyboard, but not the completed words. It reads most punctuation (but not all). The pitch ("tone") is at 80%. In addition, the user also wants a magnifier with a double magnification factor (200%) in the top half of the screen. The magnifier should follow the user's cursor, invert the colours and show cross-hairs to make the cursor position more visible.

The user needs synthetic speech and magnification but we have no information about their preferred screen reader and magnifier, so JAWS, SuperNova, NVDA or Windows’ built-in magnifier can be used to help them.


1.4.5Test case 2: Multiple AT Solutions of the Same Class Locally Available but the Preferred Solution is Missing

1.4.5.1Settings and Available Solutions (JSON)


Settings:

"http://registry.gpii.net/common/screenReaderTTSEnabled": true,

"http://registry.gpii.net/common/speechRate": 300,

"http://registry.gpii.net/common/trackingTTS": ["caret"],

"http://registry.gpii.net/common/speakTutorialMessages": false,

"http://registry.gpii.net/common/keyEcho": true,

"http://registry.gpii.net/common/wordEcho": false,

"http://registry.gpii.net/common/announceCapitals": false,

"http://registry.gpii.net/common/punctuationVerbosity": "some",

"http://registry.gpii.net/common/readingUnit": "paragraph",

"http://registry.gpii.net/common/auditoryOutLanguage": "en",

"http://registry.gpii.net/common/pitch": 0.8

Solutions:

{

"id": "com.freedomscientific.jaws"



},

{

"id": "com.baumretec.cobra"



},

{

"id": "com.yourdolphin.supernova-as"



}

1.4.5.2Description of the Settings and Solutions


The user of this preference set wants a screen reader that speaks 300 words per minute. The screen reader also tracks the caret (the input position) but not the keyboard focus or the mouse. It echoes every character entered through the keyboard, but not the completed words. It reads most punctuation (but not all). The pitch ("tone") is at 80%.

In addition, the user's preferred screen reader is NVDA but this screen reader is not available on the local system. The user’s preferences need to be addressed with either JAWS or SuperNova Access Suite.


1.4.6Test case 3: Multiple ATs of the Same Class Installed and Multiple AT Classes Needed

1.4.6.1Settings and Available Solutions (JSON)


Settings:

"http://registry.gpii.net/common/screenReaderTTSEnabled": true,

"http://registry.gpii.net/common/speechRate": 300,

"http://registry.gpii.net/common/trackingTTS": ["caret"],

"http://registry.gpii.net/common/speakTutorialMessages": false,

"http://registry.gpii.net/common/keyEcho": true,

"http://registry.gpii.net/common/wordEcho": false,

"http://registry.gpii.net/common/announceCapitals": false,

"http://registry.gpii.net/common/punctuationVerbosity": "some",

"http://registry.gpii.net/common/readingUnit": "paragraph",

"http://registry.gpii.net/common/auditoryOutLanguage": "en",

"http://registry.gpii.net/common/pitch": 0.8,

"http://registry.gpii.net/common/magnifierEnabled": true,

"http://registry.gpii.net/common/magnification": 2,

"http://registry.gpii.net/common/tracking": ["cursor"],

"http://registry.gpii.net/common/magnifierPosition": "TopHalf",

"http://registry.gpii.net/common/invertColours": true,

"http://registry.gpii.net/common/showCrosshairs": true

Solutions:

{

"id": "com.freedomscientific.jaws"



},

{

"id": "com.baumretec.cobra"



},

{

"id": "com.yourdolphin.supernova-as"



},

{

"id": "org.nvda-project"



},

{

"id": "com.microsoft.windows.magnifier"



}

1.4.6.2Description of the Settings and Solutions


The user of this preference set wants a screen reader that speaks 300 words per minute. The screen reader also tracks the caret (the input position) but not the keyboard focus or the mouse. It echoes every character entered through the keyboard, but not the completed words. It reads most punctuation (but not all). The pitch ("tone") is at 80%. In addition, the user also wants a magnifier with a double magnification factor (200%) in the top half of the screen.

The user's preferred screen reader is NVDA. The magnifier should follow the user's cursor, invert the colours and show cross-hairs to make the cursor position more visible.

NVDA is available on the local system but there is no third-party magnifier (only Windows’s built-in magnifier).

1.4.7Test case 4a: No Magnifier on Windows

1.4.7.1Settings and Available Solutions (JSON)


Settings:

"http://registry.gpii.net/common/magnifierEnabled": true,

"http://registry.gpii.net/common/magnification": 1.5

Solutions:

{

"id": "com.microsoft.windows.highContrast"



},

{

"id": "com.microsoft.windows.mouseTrailing"



},

{

"id": "com.microsoft.windows.displaySettings"



},

{

"id": "com.microsoft.windows.cursors"



}

1.4.7.2Description of the Settings and Solutions


The user of this preference set needs a magnification of 150% but no magnifier is available on the local system.

The local system allows modifications to the following solutions: high contrast, mouse trailing, mouse cursor size and screen resolution.


1.4.8Test case 4b: No Magnifier on Linux

1.4.8.1Settings and Available Solutions (JSON)


Settings:

"http://registry.gpii.net/common/magnifierEnabled": true,

"http://registry.gpii.net/common/magnification": 1.5

Solutions:

{

"id": "org.gnome.desktop.interface"



},

{

"id": "org.gnome.shell.overrides"



},

{

"id": "org.gnome.desktop.wm.preferences"



},

{

"id": "org.gnome.nautilus"



},

{

"id": "org.gnome.desktop.a11y.keyboard"



},

{

"id": "org.gnome.desktop.a11y.applications.onscreen-keyboard"



}

1.4.8.2Description of the Settings and Solutions


The user of this preference set needs a magnification of 150% but no magnifier is available on the local system.

The available solutions are settings for font size (cf. access settings) and cursor size (cf. dconf-editor), contrast themes, Window Manager preferences, the font settings for Nautilus, and keyboard settings.


1.4.9Test case 4c: No Magnifier on Android

1.4.9.1Settings and Available Solutions (JSON)


Settings:

"http://registry.gpii.net/common/magnifierEnabled": true,

"http://registry.gpii.net/common/magnification": 1.5

Solutions:

{

"id": "com.android.activitymanager"



},

{

"id": "com.android.talkback"



},

{

"id": "com.android.freespeech"



},

{

"id": "com.android.persistentConfiguration"



},

{

"id": "com.android.audioManager"



},

{

"id": "com.android.settings.system"



},

{

"id": "com.android.settings.secure"



},

{

"id": "com.technosite.smarttwitter"



}

1.4.9.2Description of the Settings and Solutions


The user of this preference set needs a magnification of 150% but no magnifier is available on the local system.

Any Android settings can be tweaked to help the user, except magnification.


1.4.10Test case 5a: Required High-Contrast Theme not Available on Android

1.4.10.1Settings and Available Solutions (JSON)


Settings:

"http://registry.gpii.net/common/highContrastEnabled": true,

"http://registry.gpii.net/common/highContrastTheme": "yellow-black"

Solutions:

{

"id": "com.android.activitymanager"



},

{

"id": "com.android.talkback"



},

{

"id": "com.android.freespeech"



},

{

"id": "com.android.persistentConfiguration"



},

{

"id": "com.android.audioManager"



},

{

"id": "com.android.settings.system"



},

{

"id": "com.android.settings.secure"



}

1.4.10.2Description of the Settings and Solutions


The user of this preference set needs a yellow-on-black contrast theme but this theme is not available on the local system.

All other Android settings can be adapted to address the user’s needs.


1.4.11Test case 5b: Required High-Contrast Theme not Available on Linux GNOME

1.4.11.1Settings and Available Solutions (JSON)


Settings:

"http://registry.gpii.net/common/highContrastEnabled": true,

"http://registry.gpii.net/common/highContrastTheme": "yellow-black"

Solutions:

{

"id": "org.gnome.desktop.interface"



},

{

"id": "org.gnome.nautilus"



},

{

"id": "org.gnome.desktop.a11y.keyboard"



},

{

"id": "org.gnome.desktop.a11y.applications.onscreen-keyboard"



},

{

"id": "org.gnome.orca"



},

{

"id": "org.gnome.desktop.a11y.magnifier"



},

{

"id": "org.gnome.shell.overrides"



},

{

"id": "org.gnome.desktop.wm.preferences"



}

1.4.11.2Description of the Settings and Solutions


The user of this preference set needs a yellow-on-black contrast theme but this theme is not available on the local system.

The available solutions are settings for font size (cf. access settings) and cursor size (cf. dconf-editor), magnification, Window Manager preferences, the font settings for Nautilus, Orca, and keyboard settings.


1.4.12Test case 6a: Required Font Size Can Be Addressed at Various Levels

1.4.12.1Settings and Available Solutions (JSON)


Settings:

"http://registry.gpii.net/common/fontSize": 18

Solutions:

{

"id": "org.gnome.desktop.interface"



},

{

"id": "org.gnome.desktop.a11y.magnifier"



},

{

"id": "org.gnome.nautilus"



},

{

"id": "org.gnome.desktop.a11y.applications.onscreen-keyboard"



},

{

"id": "org.gnome.desktop.a11y.keyboard"



},

{

"id": "org.gnome.desktop.wm.preferences"



},

{

"id": "org.gnome.shell.overrides"



},

{

"id": "org.gnome.orca"



},

{

"id": "org.alsa-project"



},

{

"id": "org.freedesktop.xrandr"



},

{

"id": "org.chrome.cloud4chrome"



},

{

"id": "com.bdigital.easit4all"



},

{

"id": "eu.gpii.olb"



}{

"id": "com.microsoft.windows.magnifier"

},

{

"id": "com.microsoft.windows.onscreenKeyboard"



},

{

"id": "com.microsoft.windows.highContrast"



},

{

"id": "com.microsoft.windows.mouseTrailing"



},

{

"id": "com.microsoft.windows.displaySettings"



},

{

"id": "com.microsoft.windows.cursors"



}

1.4.12.2Description of the Settings and Solutions


The user of this preference set needs a font size of 18 points.

The font size cannot be set on Windowsin Linux GNOME. In this test, the user should also check the effect of Linux GNOME’s font size setting on web pages in Google Chrome. Changing the font size in Cloud4Chrome is also allowed. (Changing the settings of the magnifier, the screen resolution, the contrast theme, the cursor size and the pointer trailscrosshairs is allowed.)


1.4.13Test case 6b: Required Magnification Can Be Set at Various Levels

1.4.13.1Settings and Available Solutions (JSON)


Settings:

"http://registry.gpii.net/common/magnification": 1.2

Solutions:

{

"id": "com.microsoft.windows.magnifier"



},

{

"id": "com.microsoft.windows.onscreenKeyboard"



},

{

"id": "com.microsoft.windows.highContrast"



},

{

"id": "com.microsoft.windows.mouseTrailing"



},

{

"id": "com.microsoft.windows.displaySettings"



},

{

"id": "com.microsoft.windows.cursors"



},

{

"id": "org.chrome.cloud4chrome"



},

{

"id": "org.chrome.zoom"



},

{

"id": "org.chrome.textScaling"



}

1.4.13.2Description of the Settings and Solutions


The user of this preference set needs a magnification of 120%.

The magnification can be set at several levels: the Windows magnifier, the screen resolution, the Cloud4Chrome extension. However, the SuperNova Access Suite is not available.


1.5Assignment of test cases to experts


ID

Expertise

Test cases

01

Blind & low vision

Test case 1, 3 &11

02

Hearing impaired

Test case 5,6,8,12

























12








ANNEX A. Pre-test questionnaire




Pre-test questionnaire

Site: ________________________________________________________

Nationality: ________________________________________________________

Gender:  Male  Female

Age: ____ Years

Profession: ________________________________________________________

Disability:  Yes  No

Type of Disability: ________________________________________________________



Assessment of expertise:




Strongly dis-agree
















Strongly agree

I have a good knowledge of …






















  1. Accessibility Guidelines and Experiences






















1.1 Web Technologies and Applications (e.g. WCAG 2.0)

1

2

3

4

5

6

7

1.2 Mobile Accessibility

1

2

3

4

5

6

7

1.3 Desktop Applications






















1.3.1 Windows (e.g )

1

2

3

4

5

6

7

1.3.2 Mac OS

1

2

3

4

5

6

7

1.3.3 Linux GNOME

1

2

3

4

5

6

7

  1. Diversity of user disabilities






















2.1 Auditory disabilities

1

2

3

4

5

6

7

2.2 Visual disabilities

1

2

3

4

5

6

7

2.3 Physical disabilities

1

2

3

4

5

6

7

2.4 Cognitive disabilities

1

2

3

4

5

6

7

2.5 Speech disabilities

1

2

3

4

5

6

7

  1. Configuring and adjusting the settings of ICT products for people with disabilities






















3.1 Windows

1

2

3

4

5

6

7

3.2 Mac OS

1

2

3

4

5

6

7

3.3 Linux GNOME

1

2

3

4

5

6

7

4. Configuring and adjusting the settings of assistive technologies (only the type of AT or accessibility feature that the expert has experience with; cross out the types that are irrelevant)






















Screen readers

1

2

3

4

5

6

7

Screen magnifiers

1

2

3

4

5

6

7

Settings to improve readability (font size, font face, contrast theme, ….)

1

2

3

4

5

6

7



1

2

3

4

5

6

7

Other (specify which ones): …

1

2

3

4

5

6

7


The database is protected by copyright ©ininet.org 2016
send message

    Main page