w3c
Preview of results collection form has title and instructions that are inconsistent with preview of test plan
Testing for issue #977 , which is resolved by #997 , I found that the headings and test instructions are correctly presented in the test plan preview, but if you follow the link to view the preview of the results collection form, the instructions still have the V1 text and format.
For example, the 997 preview for Alert Example Test Plan | For Pattern: alert has the correct headings and instructions. However, if you open the link to the JAWS collection form for test 1, Trigger an alert, I found the following inconsistencies.
The H1 in the preview is:
Testing task: Trigger an alert
It should be:
Test: Trigger an alert
Following the H1, the following paragraph is still present. It should not be there:
With JAWS in PC cursor active mode, describe how JAWS behaves when performing task "With focus on the 'Trigger Alert' button, activate the button to trigger the alert."
The H2 shown in the preview is:
Test instructions
It should be:
Instructions
The list of instructions shown is:
- Restore default settings for JAWS. For help, read Configuring Screen Readers for Testing.
- Activate the "Open test page" button below, which opens the example to test in a new window and runs a script that sets focus on the 'Trigger Alert' button.
- Press Alt + Delete to determine which cursor is active. If the virtual cursor is active, press Insert + z to disable the virtual cursor.
- With focus on the 'Trigger Alert' button, activate the button to trigger the alert.
- Using the following commands, With focus on the 'Trigger Alert' button, activatethe button to trigger the alert.
- Space (virtual cursor active)
- Enter (virtual cursor active)
- Space (PC cursor active) ◦ Enter (PC cursor active)
The instructions should exactly match the instructions section on Alert Example Test Plan | For Pattern: alert, including the instructions for settings that follow the numbered list.
Following the instructions, the success criteria section is still present. This is documented separately in #1009.
The requirements for the preview are the same as the requirements for the test runner specified in w3c/aria-at-app#743. Since this preview is only used primarily by Isabel, James, and myself, it is not as critical as ensuring this content is correct in the test runner, which is used by all testers. So, I am prioritizing fixing this bug as a P2 rather than P1.
Looked at the tests preview linked in #1017. For example, JAWS tests for alert. That PR fixes this problem.