This is a
playground to test code. It runs a full
Node.js environment and already has all of
npm’s 400,000 packages pre-installed, including
axe-cli with all
npm packages installed. Try it out:
This service is provided by RunKit and is not affiliated with npm, Inc or the package authors.
Provides a command line interface for aXe to run quick accessibility tests.
Install Node.js if you haven't already. This project requires Node 6+.
Install axe-cli globally:
npm install axe-cli -g
Lastly, install the webdrivers of the browsers you wish to use. A webdriver is a driver for your web browsers. It allows other programs on your machine to open a browser and operate it. Current information about available webdrivers can be found at selenium-webdriver project. Alternatively, you could use Webdriver manager
After installing, you can now run the
axe command in your CLI, followed by the URL of the page you wish to test:
You can run multiple pages at once, simply add more URLs to the command. If you do not specify the protocol, http will be used by default
axe www.deque.com, dequeuniversity.com
Note: If you are having difficulty with the color scheme, use
--no-color to disable text styles.
You can use the
--rules flag to set which rules you wish to run, or you can use
--tags to tell axe to run all rules that have that specific tag. For example:
axe www.deque.com --rules color-contrast,html-has-lang
Or, to run all wcag2a rules:
axe www.deque.com --tags wcag2a
In case you want to disable some rules, you can use
--disable followed by a list of rules. These will be skipped when analyzing the site:
axe www.deque.com --disable color-contrast
This option can be combined with either
A list of rules and what tags they have is available at: https://dequeuniversity.com/rules/worldspace/2.0/.
Results can be saved as JSON data, using the
--dir flags. By passing a filename to
--save you indicate how the file should be called. If no filename is passed, a default will be used. For example:
axe www.deque.com --save deque-site.json
axe www.deque.com --dir ./axe-results/
If you want to only test a specific area of a page, or wish to exclude some part of a page you can do so using the
--exclude flags and pass it a CSS seletor:
axe www.deque.com --include #main --exclude #aside
Axe-cli will look for locally available versions of axe-core. If the directory from where you start axe-cli has an
axe.js file, or has a
node_modules directory with axe-core installed in it. Axe-cli will use this version of axe-core instead of the default version installed globally.
Axe-cli can run in a variety of web browsers. By default axe-cli uses PhantomJS, which is installed as a dependency. But axe-cli is equally capable of testing pages using other web browers. Running in another browser requires that browser's webdriver to be installed. You can find a list of available webdrivers at: https://www.npmjs.com/package/selenium-webdriver
To run axe-cli using another browser, pass it in as the
axe www.deque.com --browser chrome
Or for short:
axe www.deque.com -b c
Axe-cli can be ran within the CI tooling for your project. Many tools are automatically configured to halt/fail builds when a process exits with a code of
-q for short, to have the axe-cli process exit with a failure code
1 when any rule fails to pass.
axe www.deque.com --exit
For debugging and managing timeouts, there are two options available. With
--timer set, axe-cli will log how long it takes to load the page, and how long it takes to run axe-core. If you find the execution of axe-core takes too long, which can happen on very large pages, use
--timeout to increase the time axe has to test that page:
axe www.cnn.com --timeout=120