re: ATAG 2.0 test writing assignments

A.4.2.1 Describe Accessibility Features:
For each authoring tool feature that is used to meet Part A of ATAG 2.0, at least one of the following is true: (Level A)
    (a) Described in the Documentation: Use of the feature is explained in the authoring tool's documentation; or
    (b) Described in the Interface: Use of the feature is explained in the authoring tool user interface; or
    (c) Platform Service: The feature is a service provided by an underlying platform; or
    (d) Not Used by Authors: The feature is not used directly by authors (e.g., passing information to a platform accessibility service).
    Note: The accessibility of the documentation is covered by Guideline A.1.1 and Guideline A.1.2.

Test 0001 Assertion:  
Test 0001 Author: Jan Richards
Test 0001 Steps [Updated]:

1. Examine the user interface of the authoring tool, noting each user interface component that is necessary in order to meet part A of ATAG 2.0 (e.g. search functions). Note: Many of the success criteria in Part A are more qualitative and will not require particular user interface functionality (e.g. the requirement to follow WCAG 2.0). (Components are checked because they are the constituents of features)

2. For each of these user interface components:

2a. If the user interface component is part of functionality provided by the platform (e.g. the menu bar of the browser in the case of a web-based tool), then skip to the next component.

2b. If use of the user interface component is a convention of the platform (e.g. how to operate scrollbars, standard Save and Open dialog boxes), then skip to the next component.

2c. If use of the user interface component is clear from its context (e.g. a page zoom feature with percentage values in a drop-down list) , then skip to the next component.

2d. If the user interface component is documented in the interface (e.g. with text next to the item, context-sensitive help), then skip to the next component.

2e. Look up the user interface component (or its associated functionality) in the documentation. If documentation exists, then skip to the next component.
 
2f. If there is no way to discover how to use the user interface component besides trial-and-error then select FAIL.



A.4.2.2 Document All Features: For each authoring tool feature, at least one of the following is true: (Level AA)
    (a) Described in the Documentation: Use of the feature is explained in the authoring tool's documentation; or
    (b) Described in the Interface: Use of the feature is explained in the authoring tool user interface; or
    (c) Platform Service: The feature is a service provided by an underlying platform; or
    (d) Not Used by Authors: The feature is not used directly by authors (e.g., passing information to a platform accessibility service).
    Note: The accessibility of the documentation is covered by Guideline A.1.1 and Guideline A.1.2.

Test 0001 Assertion:  
Test 0001 Author: Jan Richards
Test 0001 Steps [Updated]:

1. Examine the user interface of the authoring tool, noting each user interface component that accepts input is available to the author. (Components are checked because they are the constituents of features)

2. For each of these user interface components:

2a. If the user interface component is part of functionality provided by the platform (e.g. the menu bar of the browser in the case of a web-based tool), then skip to the next component.

2b. If use of the user interface component is a convention of the platform (e.g. how to operate scrollbars, standard Save and Open dialog boxes), then skip to the next component.

2c. If use of the user interface component is clear from its context (e.g. a page zoom feature with percentage values in a drop-down list) , then skip to the next component.

2d. If the user interface component is documented in the interface (e.g. with text next to the item, context-sensitive help), then skip to the next component.

2e. Look up the user interface component (or its associated functionality) in the documentation. If documentation exists, then skip to the next component.
 
2f. If there is no way to discover how to use the user interface component besides trial-and-error then select FAIL.

@@this would definitely benefit from a details section.







(MR) JAN RICHARDS
PROJECT MANAGER
INCLUSIVE DESIGN RESEARCH CENTRE (IDRC)
OCAD UNIVERSITY

T 416 977 6000 x3957
F 416 977 9844
E jrichards@ocadu.ca

Received on Monday, 1 October 2012 15:53:25 UTC