axe-core | Accessibility engine for automated Web UI testing | Accessibility Testing library

 by   dequelabs JavaScript Version: 4.9.1-canary.ebb1b95 License: MPL-2.0

kandi X-RAY | axe-core Summary

kandi X-RAY | axe-core Summary

axe-core is a JavaScript library typically used in Testing, Accessibility Testing applications. axe-core has no bugs, it has no vulnerabilities, it has a Weak Copyleft License and it has medium support. You can install using 'npm i eslint-plugin-axe' or download it from GitHub, npm.

Axe is an accessibility testing engine for websites and other HTML-based user interfaces. It's fast, secure, lightweight, and was built to seamlessly integrate with any existing test environment so you can automate accessibility testing alongside your regular functional testing. Sign up for axe news to get the latest on axe features, future releases, and events.

            kandi-support Support

              axe-core has a medium active ecosystem.
              It has 5135 star(s) with 739 fork(s). There are 180 watchers for this library.
              There were 10 major release(s) in the last 6 months.
              There are 244 open issues and 1773 have been closed. On average issues are closed in 112 days. There are 6 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of axe-core is 4.9.1-canary.ebb1b95

            kandi-Quality Quality

              axe-core has 0 bugs and 0 code smells.

            kandi-Security Security

              axe-core has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              axe-core code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              axe-core is licensed under the MPL-2.0 License. This license is Weak Copyleft.
              Weak Copyleft licenses have some restrictions, but you can use them in commercial projects.

            kandi-Reuse Reuse

              axe-core releases are available to install and integrate.
              Deployable package is available in npm.
              Installation instructions, examples and code snippets are available.
              It has 12300 lines of code, 0 functions and 1281 files.
              It has low code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi has reviewed axe-core and discovered the below as its top functions. This is intended to give you an instant insight into axe-core implemented functionality, and help decide if they suit your requirements.
            • Builds rules .
            • Checks the current orientation lock for a document .
            • Determine if the text node is an icon .
            • create schemas
            • determine if node is dataTable .
            • Creates a new Color .
            • Tests whether the current node matches the input text .
            • Determines whether the z - element is in the stack position .
            • Configure audit .
            • Checks if an element is visible .
            Get all kandi verified functions for this library.

            axe-core Key Features

            No Key Features are available at this moment for axe-core.

            axe-core Examples and Code Snippets

            axe-crawler,Configuration,Command Line Options
            JavaScriptdot img1Lines of Code : 52dot img1License : Permissive (MIT)
            copy iconCopy
            --depth d
                Specify how many levels deep you want the crawler to scrape for new links.
                Default: 5.
            --ignore regex
                Specify a regular expression that identifies URLs you wish to ignore.
                Overridden by whitelist regex if both are specified  

            Community Discussions


            An unhandled exception occurred: The requested module 'sourcemap-codec' does not provide an export named 'decode'
            Asked 2022-Mar-03 at 14:48

            On Upgrading, to angular 13, My build step on pipeline is failing. My initial version was 11, on upgrading to 12 the build worked fine but on upgrading from 12 to 13, it started giving me this error on pipeline. The build is running fine on local but failing on pipeline.

            I have also added the package.json file code and dependencies and also added the image that displays error.



            Answered 2022-Mar-03 at 14:48

            I was facing the same issue which is why I stumbled across this post.

            My issue was I was using the wrong node version. I faced a similar issue after upgrading to Angular 13 but I was using node version v14.2.0.

            I changed the node version to v14.15.0 and it worked.

            nvm use v14.15.0

            PS: NVM manages multiple nodejs versions.



            How to configure accessibility rules for wcag2aa in com.deque.html.axe-core for selenium java
            Asked 2021-Jul-09 at 10:51

            I need to analyze the web driver with wcag2aa.
            I'm using the below dependency.



            Answered 2021-Jul-09 at 10:51

            As per my understanding the result.getViolations() and result.getInapplicable() are two different things and both yield a different result.

            It might happened that the violation is not present but there are some rules for which no matching elements were found on the page.

            Results Object The callback function passed in as the third parameter of runs on the results object.

            This object has four componentsa passes array, a violations array, an incomplete array and an inapplicable array.

            1) The passes array keeps track of all the passed tests, along with detailed information on each one. This leads to more efficient testing, especially when used in conjunction with manual testing, as the user can easily find out what tests have already been passed.



            @testcafe-community/axe does not report violations that other tools do
            Asked 2021-Jun-07 at 09:51

            I am exploring tools I can use for automated Accessibility Testing and wanted to try axe-core with TestCafe. I am an advocate of TestCafe, I love that is a lightweight tool and doesn't have dependencies on WebDriver. The docs are great and the scripting is easy.

            I have however found that @testcafe-community/axe and its predecessor axe-testcafe do not report all violations while axe-core with selenium and axe-webdriverjs do. For example, running with axe-webdriverjs, I have the following code and resulting output showing the violations of a localhost page I am checking -




            Answered 2021-Jun-04 at 16:42

            The documentation for axe-core states that you need to specify which rules you intend to test against using options.

            Landmarks are discussed in WCAG 1.3.6., which is a "Level AAA" item. It appears that axe-core is only capable of testing against "Level A" and "Level AA." In your example, the item is not listed by the tool as a WCAG failure, but rather a best-practices recommendation. This may be why it isn't showing up in your other tools.

            If you can easily implement this recommendation, then I'd say go ahead and do it. If not, I wouldn't let something like this stop my code from going into production. Landmarks are nice-to-have, but it's far more important that you meet all "Level A" requirements and as many "Level AA" requirements as you reasonably can.

            It's worth noting that any automated accessibility testing tool is nothing more than a starting point for manual evaluation. These tools often generate tons of false positives (and sometimes miss important things!) because it's often not possible to algorithmically determine whether something is genuinely useful to human visitors.

            I've also seen pages/apps that pass automated tools with no errors (Wave, Axe, etc.), but they are completely impossible to use with assistive technology.



            Angular 11 is not running ngcc
            Asked 2021-Apr-19 at 19:46

            I have an old Angular application, which I have upgraded from Angular 9 to Angular 11. (It had many stable upgrades throughout the years, starting from Angular 2)

            My problem is, that the ngcc is not running ng build:



            Answered 2021-Feb-03 at 14:10

            My problem was that an another tsconfig file was overwriting the root's definitions, and turned off ivy and ngcc altogether.




            How to resolve @typescript-eslint/no-var-requires error. Error while adding @axe-core/react
            Asked 2021-Feb-14 at 19:00

            I have added axe-core/react into my project by:



            Answered 2021-Feb-14 at 19:00


            Issue with Cypress e2e after package updates
            Asked 2021-Jan-21 at 19:52

            I have a project where I have updated all of the packages.

            Before the update all e2e tests functioned as expected.

            After the update, The product itself compiles and runs as expected.

            However, the e2e tests are showing unexpected issues both in the IDE and at run time.

            For example,



            Answered 2021-Jan-21 at 19:52

            Finally figured out a solution after visiting the NPM page for axe-cypress.



            Getting error "org.openqa.selenium.JavascriptException: javascript error: eval is disabled" while trying to do accessibility testing using Axe-Core
            Asked 2020-May-16 at 07:40

            I am trying to do accessibility testing using Axe-Core tool using Java as the Programming language. I was able to get the result from many pages in my application but for one of the page, I am getting error as



            Answered 2020-May-16 at 07:40

            My suspicion is that you are getting this error as the site you are testing has a content security policy

            A Content Security Policy (CSP) allows a website owner to protect their end users by ensuring no malicious third party JS, CSS images etc. are injected into the site. Anything included in the CSP is allowed, anything not included is blocked.

            Within a CSP it will block JavaScript eval function, which is required in your programme.

            The site owner would have to explicitly allow eval on their site (as it is blocked by default if you have any JS rules in your CSP) by adding unsafe-eval as one of the rules on their CSP.

            Taken from the page I linked on CSP:-


            Allows the use of eval() and similar methods for creating code from strings. You must include the single quotes.

            The only way you could fix this is by asking the owner of the site to add that to their CSP or by changing whichever function is injecting eval into their site.

            If you want another site to test to confirm it is CSP that is blocking your script you can try mine as my CSP is very strict.

            Update after conversations

            It appears I got the problem correct but not the cause.

            This was being caused by the website overriding window.eval to throw an error (basically disabling it). The following fiddle demonstrates this behaviour in it's most basic form.


            Community Discussions, Code Snippets contain sources that include Stack Exchange Network


            No vulnerabilities reported

            Install axe-core

            First download the package:.


            The axe-core API fully supports the following browsers:. Support means that we will fix bugs and attempt to test each browser regularly. Only Firefox, Chrome, and Internet Explorer 11 are currently tested on every pull request. There is limited support for JSDOM. We will attempt to make all rules compatible with JSDOM but where this is not possible, we recommend turning those rules off. Currently the color-contrast rule is known not to work with JSDOM. We can only support environments where features are either natively supported or polyfilled correctly. We do not support the deprecated v0 Shadow DOM implementation.
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries

            Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link