-
Notifications
You must be signed in to change notification settings - Fork 750
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error during analyse of Website - should report #1532
Comments
I have been getting the same error as well. is what I'm getting |
Thanks for the report. I've narrowed down the problem and should be getting a fix in soon. |
Hi any ETA on this? We greatly rely on aXe-coconut for our testing :) |
Yep. I have a fix ready, just need to tweak it a bit and should have it in within a day or two. |
Leaving a comment so I can track this issue. There are some rules in the newer versions of axe-core that I want to test with the axe-coconut chrome add-on once it is working again. |
The fix was just merged so after a deploy axe-coconut should be working again. Please let us know if you run into any other problems. |
Thanks for letting us know that the extension is still having problems and for your continual patience while we work to resolve it. It turned out that we had a problem with our nightly deploys. We are working on a fix which should go out soon. |
We just deployed the latest version axe-coconut to the Google Chrome store. It seems to be working correctly. Please let us know if you still are experiencing any problems. |
It is working great for me now. Thanks for all the awesome work you all put into this tool! |
works fine for me too :) |
Details following in the text:
Testobject: https://funthomas424242.github.io/honey-toggle-button/
wich contains this webcomponent
https://funthomas424242.github.io/honey-toggle-button/src/components/toggle-button/toggle-button.js
Expectation: I expect a list of accessibillity errors of my webcomponent.
Actual: There is a stacktrace of axe-cocounut addon
Motivation: The stacktrace write i should create an issue
The text was updated successfully, but these errors were encountered: