How is this tool used?

[mgifford]

As I've already noted, it can be difficuclt to get started. 

Even understanding what are the intentions of using this multi-tool tool. 

Is this a CI/CD tool? 

Should I be able to scan a page from the command line? 

Do I need to create custom configs for each page I want scanned? 

I assume it doesn't act like https://unlighthouse.dev/ or https://github.com/GovTechSG/purple-a11y in scanning whole domains.

You're a lot of tools, but it would be interesting to see the results of a page.  Sometimes less is more in the context of accessibility.

[jrpool]

Thank you for describing ways in which the usage documentation is confusing. This is helpful for making the README file clearer.

Basically, Testaro makes one contribution: facilitating ensemble testing (testing with 11 different tools) for web accessibility. That contribution can be leveraged in various environments, such as CLIs, web UIs, development pipelines, and surveillance daemons. Testaro provides some help in setting up such environments, such as the call module for CLI usage, and for each Testaro module the README file shows how to use it programmatically and via a CLI. But integrating Testaro into any testing practice will require development work similar to the work for integrating a single testing tool; the difference is that this work gives you findings from 11 tools instead of 1.

In my own work putting Testaro to use, I am also making heavy use of the Testilo package. That streamlines the use of Testaro, but still requires development of a system to manage user requests, authorization, scheduling, recordkeeping, etc.

Your comment suggests it could be helpful to produce a few tutorials on typical use cases. I am working on one overview article now, but more specific examples might ease onboarding.