AutoSponge
commented
5 years ago For instance, assume axe-core was the engine. What is the testEngineId? Some options I thought about:
- URL to commit hash in a repo (e.g., https://github.com/dequelabs/axe-core/commit/430b07fa36ac9f6932a0eb63fed1fb0524f26a02). Only works for projects that are public and is lost when you change hosts, project names, etc.
- URL to a tagged release (e.g., https://github.com/dequelabs/axe-core/releases/tag/v3.2.0). Same as above but only works for projects use tags.
- Engine's canonical URL. Not enough info: needs at least a version identifier.
- Engine's canonical URL + a version identifier. This seems flimsy. What if the company sells and the URL is re-branded?
- Instead of a single ID, perhaps a rich data structure can cover more use cases: https://schema.org/SoftwareApplication offers some interesting properties:
downloadUrl,softwareVersion,accessMode(for when a single app/version has multi-modal use like Braille mode), etc.
Feedback from Peter Durham:
Might be helpful to have an id for test engines, so testEngineId + ruleId maps consistently to a unique rule (to allow consistent decoration of results, for example with links to relevant WCAG criteria)