You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On report pages and in candidate review, we need a summary of assertion failures and an easy way to navigate to them.
This summary would include:
A heading
A summary statement
A table of failing assertions
Content for the heading:
Summary of Failing Assertions (n must, n should)
Under the heading, a summary statement of form:
X assertions failed for Y commands in Z tests.
Columns in the table:
Test name(make it a link to that test)
Command
Assertion Priority
Assertion (show the phrase form of the assertion)
{AT} Response: {AT} is the name of the AT, e.g., "JAWS Response"
In the candidate review experience, this summary would be the first page when the user opens the candidate review experience. It would have its own link at the beginning of the left nav just before test 1. Do not give it a number in the list; just name it "summary of Failing Assertions".
On report pages, this section would appear just after the summary of tests and before test 1.
mcking65
changed the title
Add report table summarizing failing assertions from all tests in a plan
Add report section summarizing failing assertions from all tests in a plan
Oct 21, 2024
On report pages and in candidate review, we need a summary of assertion failures and an easy way to navigate to them.
This summary would include:
Content for the heading:
Under the heading, a summary statement of form:
Columns in the table:
In the candidate review experience, this summary would be the first page when the user opens the candidate review experience. It would have its own link at the beginning of the left nav just before test 1. Do not give it a number in the list; just name it "summary of Failing Assertions".
On report pages, this section would appear just after the summary of tests and before test 1.
For example, on the report page
JAWS and Chrome for Action Menu Button Example Using aria-activedescendant | ARIA-AT Reports,
this section would appear after the section titled "Results for JAWS and Chrome" and before the section titled "Test 1: Navigate forwards to a menu button in reading mode (16 passed, 0 failed)".
Accessibility Note: be sure the table is labeled by the heading.
The text was updated successfully, but these errors were encountered: