Support V2 test format when manually running a test

[mcking65]

Overview

Change the content shown in the test runner when a test plan written in the V2 format is opened.

Note:

• Unlike test plan viewing and reporting functions, It is not essential the system be able to support running both V1 and V2 formatted test plans. We could stop running test plans that are not in the V2 format on a planned transition date.
• Implementing the solution for this issue does not require Change results collection form to support pass/fail assertion verdicts aria-at#969 to be complete. This issue is a higher priority, although it might be more efficient to work on both in the same PR.
• A few changes specified below are not dependent on the V2 format; they are minor wording improvements that are simple to make while working on this issue.

In general, the changes needed in the runner are exact reflections of a subset of changes specified for the test plan preview generated during test plan build. Those changes are specified in w3c/aria-at#977.

Changes to display of a test in the runner

Change heading 1

Streamline wording of the first level 1 heading. It is currently:

Testing task:1. Navigate forwards to a collapsed disclosure button in reading mode

Replace the string "Testing task:1." with the string "Test 1:"

Test 1: Navigate forwards to a collapsed disclosure button in reading mode

Note that the V2 format contains a column for presentationNumber in tests.csv. That number specifies the sequence of test presentation.

Remove redundant heading 1 and subsequent paragraph

Following the AT and browser version information, there is another h1 followed by a paragraph that describes the task. Remove the h1 and the paragraph. Both are unnecessary.

Example:

Testing task: Navigate forwards to a collapsed disclosure button in reading mode

With JAWS in reading mode, describe how JAWS behaves when performing task "With the reading cursor on the 'Navigate forwards from here' link, navigate to the 'About' disclosure button."

Change instructions

Change the text of the level 2 heading from "Test Instructions" to "Instructions". Implement the instructions format as described in w3c/aria-at#977. Be sure to include the instructions for command settings where appropriate.

Remove success criteria

Remove the level 2 heading with text "Success Criteria" and the paragraph and list that follow it.

Example:

Success Criteria

To pass this test, JAWS needs to meet all the following assertions when each specified command is executed:

1. Role 'navigation landmark' is conveyed
2. Name 'Mythical University' is conveyed
3. Role list is conveyed
4. Number of list items, '3', is conveyed
5. Role 'button' is conveyed
6. Name 'About' is conveyed
7. State 'collapsed' is conveyed

Command headings

For each command there is a level 3 and level 4 heading. For example:

After 'F'

Assertions After 'F'

The commands in the headings need to be converted to command-specification strings as described in w3c/aria-at#977 with the command followed by settings in parentheses. For example:

After 'F' (virtual cursor active)

Assertions After 'F' (virtual cursor active)

[ccanash]

Hi @mcking65 is it ok if we close this?

[mcking65]

This is complete and shipped to prod, closing.