w3c
[DO NOT MERGE] Test plan that illustrates assertion exception enhancement specified in issue 1039
Issue #1039 proposes an enhancement to the logic for assertion exceptions. The first two tests in the radio group test plan in this PR illustrates how that logic would be used.
In the tests.csv file, the assertions for the first test, navForwardsRadioGroupWhereNoRadioButtonsAreChecked, includes 0:interactionModeEnabled. This specifies that the assertion interactionModeEnabled is not included for any commands associated with this test unless a specific command includes an assertion exception overrides the 0 priority. In jaws-commands.csv and nvda-commands.csv, there is one command associated with this test, tab with a readingCursor setting, that overrides the priority 0 with priority 2.
Similarly, in the test NavBackIntoRadioGroupWhereLastRadioUnchecked, the assertions column includes:
nameThinCrust 0:nameRegularCrust
So, by default, the nameThinCrust assertion is included for all commands. However, for the shift+tab command, each of the screen reader command files includes the assertionException of:
0:nameThinCrust 1:nameRegularCrust
This is because when navigating backward with shift+tab, the cursor moves to the regular curst radio instead of the thin crust radio.
As a result, if #1039 is implemented, the tab and shift+tab commands for these two tests would have assertions that are different from the assertions for other commands.
