Candidate Test Plan page, design updates

Hi all,

Since we didn’t have an ARIA-AT Community Group meeting last week, I wanted
to provide an asynchronous update for those who are following the design of
the new Candidate Test Plan page where vendors will be able to review test
plans for their AT.

The following update can also be found as a comment on the GitHub thread
<https://github.com/w3c/aria-at-app/issues/437#issuecomment-1193834553>
containing the original mockups. Feel free to provide feedback or continue
the conversation on the thread. The original mockups will be updated to
reflect these changes soon.

   - New top-level hierarchy of test plans
      - The top-level view of Candidate test plans has been updated to
      organize plans by AT, so that vendors can easily identify the plans that
      they are responsible for reviewing.
      - Each AT is given a separate heading and a separate table of test
      plans. For now these tables have two columns: Test Plan Name
(which is also
      a link) and Review Status
      - Pending an ongoing discussion, this table could also include
      another column with a summary of results
   - New view for reviewing tests and test content
      - The new view for reviewing test and test content resembles the Test
      Run view, rather than the reports page.
      - There is a left-hand navigation section with an ordered list of all
      tests and an icon to indicate progress.
      - The right-hand pane contains the full test material: instructions,
      test page link, commands, and assertions
      - The output and assertion results are visible as read-only form
      elements. This design choice allows us to maintain consistency with the
      Test Run view and convey that the results are included for
context, but not
      part of the actual content being reviewed.
      - The action buttons would be updated to reflect the capabilities of
      the vendor reviewers
   - New format for test content and results
      - The new format of the test content is identical to the initial form
      that testers see when filling in results. This will allow reviewers to
      easily understand the test instructions, success criteria, and test page,
      in context.
      - The candidate results (output and assertions results) will be
      visible as readonly form inputs or text within a disclosure widget. This
      allows the results to be seen, but foregrounds the test content itself
      (instructions, commands, and assertions) as the object of review.
      - This change replaces the tabular summary view of results which is
      visible on the reports page and as a confirmation screen after submitting
      results as a tester.

Looking forward to discussing these changes in more detail at the upcoming
meeting. We're happy to provide additional context and considerations for
these choices or to consider other options for any design challenges.

Best,
Seth & Isaac