Closed angela-choo closed 7 years ago
It appears that we're not passing on the information in the axe
property to . Would you be interested in writing this feature yourself? I think you'd just want to change this part to:
AxeBuilder(browser.driver)
.options(context.axe.options)
.analyze(function(results) {
deferred.resolve(results);
});
@angela-choo and @sjelin I started working on this functionality here: https://github.com/nfl/protractor-accessibility-plugin/tree/feature/configAXE I've been pulled off this though and won't have time to get back to it until the new year. This might help you out
@jamsea Great, I will take a look at it!
@sjelin Sure, would be happy to work on this feature.
@sjelin added the feature and submitted PR here: angular/protractor-accessibility-plugin#15 I am wondering once the PR is approved, when will be the next release? Thanks!
I can do a release whenever
0.3.0 released! Thanks for the PR
Note that if you provide both:
axe: {
runOnly: {},
rules: {}
}
rules
is ignored.
I'm trying to disable rules inside protractor.conf.js for aXe but does not seem to work. Please see my code below. Thank you!
Also raised question here: https://github.com/dequelabs/axe-core/issues/267