Artem Sapegin
Artem Sapegin
I drafted my ideas on the new API: #75. I hope this covers your use case — let me know what you think.
Why do you want to have an HTML specifically? How are you planning to use it?
For now you can use [`violationCallback`](https://github.com/component-driven/cypress-axe#violationcallback-optional). ```js cy.checkA11y(subject, null, violations => cy.task('reportA11y', violations), skipFailures) ``` And then do whatever you want with them in your `cypress/plugins/index.js` file. For example, I...
@kristina-hager Thanks for the comment! The problem with this approach is that it requires too much setup from the user to have anything useful. I want to have a zero-config...
Sorry but such API is _extremely_ difficult to use. If that's what you really need, you could use axe-core directly. I'm happy to make the API more flexible, if it...
> return the 'results' object from the function 👍 > change the argument skipFailures (optional, defaults to false) to failOnViolations (optional, defaults to false). This way users can opt in...
I've updated the initial comment so we have the single source of truth here. I've also simplified reporters: now it's just a function that gets the full results object and...
I think I want to migrate the code to TypeScript first — it will be easier to work on the new API, and also we'll have our own typings.
> Hahah, well, I won't get into debates about typescript vs javascript for relatively small codebases. 😄 Very good idea.
That's a good point!