Re: ATAG Report Tool - Initial input on new resource

Hello Kevin,

Thanks for your responses! 

> Doesn't seem to make sense not to link this to the authoring tools list. This tool provides data that can drive the list. It seems to make sense to have this linked on the list and show the outputs from evaluations conducted with the help of this tool.

You’re right, I  think we should look at this when this tool and the list are more mature, so we can have literal links between them.

Conceptually they are linked, they are two sides of the same coin.

> Yes, or better yet, on completion ask if the user wants to submit to the Authoring Tools list. This does create a potential problem of moderating the content on the list, but that is there if you intend to allow JSON submissions as well.

Good idea, I have added this as issue 30 <https://github.com/w3c/wai-atag-report-tool/issues/30>. 

> Not sure about the alignment to the WAI site. Would it not be better to align more with the WCAG-EM Reporting Tool? Or create a pattern that can support all WAI tools, for example WCAG-EM Reporting Tool, Quick Reference, Easy checks (it could be a tool some day :)). (…) I keep coming back to the question as to why this isn't more like the EM reporting tool. Not arguing for a completely unique and separate style (WAI has enough of them) but developing a 'tool' style would be good. 

From team side, we are aiming to make all of these things look more like each other (with the WAI website as the definitive source for design components). The Design Components <https://wai-website-theme.netlify.com/components/> project is part of that effort.

>  Wonder if this needs some upfront guidance on who the tool is for or what skills are necessary to conduct the evaluation. 

Good suggestion! we are looking at revising the content in the first page, I have added your comment as a comment in issue 34 <https://github.com/w3c/wai-atag-report-tool/issues/34#issuecomment-581998222>..

Thanks again for your help! 

Best,
Hidde