It could be easier to find test cases from the various test result tables and pages

[cookiecrook]

Dennis pointed out that WebKit generated the wrong label for this datalist test case example.

I'm sharing this usability feedback as it's the first time I've tried to navigate results pages on https://a11ysupport.io/ Sometimes the first-time user's experience is valuable.

The link I saw first in the thread was:
https://a11ysupport.io/tech/html/datalist_element

From there it took way too many clicks to find the test case.

1. I scrolled to the first red failure in the "support by expectation" table. The Safari "none" result was not linked, so I clicked the first expectation in the row, "must convey its role."
2. Which took me to support table 0 https://a11ysupport.io/tech/html/datalist_element#support-table-0
3. From there I followed the prior table’s UI pattern and clicked on the first cell in the table row again: https://a11ysupport.io/tests/tech__html__datalist
4. And again to this one: https://a11ysupport.io/tests/tech__html__datalist/html__datalist_element/convey_role/vo_macos/safari
5. But I figured a full test run and results submission was not what I needed and went back to the test: https://a11ysupport.io/tests/tech__html__datalist
6. At this point, I found a linked "none" result (later noticed this would have also been available in step 3) and went to https://a11ysupport.io/tests/tech__html__datalist#assertion-html-datalist_element-convey_role--vo_macos-safari
7. I expanded the disclosure triangle (<details>/<summary>)
8. And finally linked to the test case: https://a11ysupport.io/tests/html/html/datalist.html

Even without some of the red herrings, this would have taken me 5 clicks, and that was for a single expectation discrepancy, listed several pages back. I think (but I'm honestly not sure) that all those failures link to the same test case, so perhaps that should be surfaced more prominently in the interface?

Suggestions to improve this:

1. Make the "open the test page" link easier to spot. It's somewhat lost in a see of red, orange, and green tables, and dozens of other general navigation links.
2. Consider renaming "run this test and submit your results" to something like "submit new test results" so it's more clear that link is not the test case itself.
3. Consider linking the test case directly to the "support by expectation" table rows. Since I often navigated to the tables directly, the "open the test page" link was scrolled off-screen, and I likely would not have seen it even if it had been styled more prominently.
4. Consider linking the test case from all results pages. Example page with no link to test case: https://a11ysupport.io/tests/tech__html__datalist/html__datalist_element/convey_role/vo_macos/safari
5. Consider linking all test cases back to their respective test results? So it's not a dead-end if you're linked directly in from an engine bug to the test case itself.

To be clear, I am suggesting you make all of the above changes, not just one. But take it or leave it, as I'm a first-time user of the site. Thanks.

[mfairchild365]

Thank you, @cookiecrook! I very much appreciate this feedback and your thoughts on this.

[mfairchild365]

@cookiecrook Thank you again for the feedback and suggestions!

Make the "open the test page" link easier to spot. It's somewhat lost in a see of red, orange, and green tables, and dozens of other general navigation links.

Done. I also now refer to the test case as "Test case HTML file" - hopefully this will clarify what the thing actually is.

Consider renaming "run this test and submit your results" to something like "submit new test results" so it's more clear that link is not the test case itself.

Done.

Consider linking the test case directly to the "support by expectation" table rows. Since I often navigated to the tables directly, the "open the test page" link was scrolled off-screen, and I likely would not have seen it even if it had been styled more prominently.

I love this idea but I struggle with how to make this work well with an already complex table. The thing that makes it especially difficult is that this "support by expectation" table represents the sum result of potentially many test cases. In other words, potentially many test cases can bubble up to this table. I've been struggling with this for a while, but I'll continue to think about it. I'll open a separate issue for this.

Consider linking the test case from all results pages.

Done.

Consider linking all test cases back to their respective test results?

I would love to do this as well. However, the system is not currently built to handle this. Each file is an independent HTML file that knows nothing about the rest of the application. This, of course, can be fixed. I'd like to avoid manually creating this link (URLs can change) - so I'd like a robust solution for this. I'll think on it some more (and open a separate issue).

I'll close this for now. Please feel free to comment and I can re-open this if needed. Thank you again!