Thanks for your interest in Asqatasun !
Response in two points:
- You don’t have to create a scenario to run an accessibility audit. You can directly use the user interface (either use the default project “openbar” to copy/paste your URL or create a project with a dedicated URL).
- Accessibility testing is a not fully automatable (at least nowadays ), so for a full and extensive audit you’ll have to run manual tests. Good news is Asqatasun not only runs a lot of automated tests but also gives you clues about suspicious tests (“pre-qualified”) which saves you time.
That’s true. Since Firefox is doing a full refactor of its addons to migrate to webextensions for Firefox 57 in November '17, it is not simple.
But you may tweak your Firefox to still allow installation of unsigned addons (maybe Firefox Nightly is mandatory, I don’t remember). We expect to see changes from the SeBuilder team : Firefox 55 and Selenium IDE, also the thread IDE 2.0 on selenium-developers, and eventually the project ddavison/selenium-ide.
Please also note that your scenarios can be written (coded) as it is only Javscript, which quickly becomes the faster way to create them.
Installation is not the same depending on whether you want a runner or not. For a “standalone” install you just need to follow the installer, or faster use the Docker image (but not for production use; as nothing is saved).
If you want to leverage the Jenkins plugin, you need to follow the asqatasun-runner install doc
Hope this helps. Don’t hesitate to come back with questions