How to preserve accessibility support test cases

[WilcoFiers]

Some of the accessibility support texts are getting a little older. I'm sure that at the time we wrote them, there were code snippets we used to test them. But those aren't preserved in a way that we could quickly check them again to see if anything has changed.

I think we should figure out a way to make this a little easier for ourselves. We definitely should keep the test cases somewhere, maybe even preserve the test data in some format that can quickly be updated.

[EmmaJP]

Perhaps a folder in the repo for the code used to test with, and a dated results file/spreadsheet. There could be a link to these in the website, so if anyone wants to rerun a test and add an updated results file that is easy to do.

It could be very helpful. Lack of evidence of the research data has been frustrating for us in regard justifying guidelines etc. years after the research behind them happened.

[Jym77]

In an ideal world, if we consider that a tool is not respecting specs, we should probably open issues on their trackers, then the test cases (or the Accessibility support) could references these issues which would be a clear way of "we're helping improve the tools", plus keeping context and date, and once the issue is fixed, even if we don't update our side immediately, everybody could see we point at a solved issue, so the concern is likely not here anymore.

[WilcoFiers]

I'm going to work on a proposal to discuss, before bringing this back to the meeting.

[Jym77]

This seems to have been superceded by #1939
@WilcoFiers do you agree we can close that one and keep the other?