Automated testing using axe-core and PA11Y
Axe-core is an automated accessibility testing tool. It is the same engine which is used in the Axe DevTools Chrome extension. Axe-core needs a browser to work, which is why it’s often paired with Selenium for acceptance tests.
PA11Y is an automated testing tool which you can run from the command line or as part of your test suite. PA11Y uses Puppeteer to run its own headless Chrome browser. It uses HTML Code Sniffer as its default runner, but it can also run axe-core at the same time if you tell it to.
Axe-core and PA11Y combined will find around 35% of accessibility issues. We have published a detailed breakdown of axe-core vs PA11Y.
Single page tests using axe-core and PA11Y
Before you can install PA11Y you will need to install NodeJS to be able to use Node Package Manager (NPM).
To use PA11Y from the command line, first install it globally. Open up the Terminal app and use the following command:
You can then run it from the command line. Make sure you pass in both HTML Code Sniffer and axe-core as runners. If you don’t pass in axe as a runner it will not use axe-core. Although HTML Code Sniffer is the default, once you pass in axe it overrides the default so you must tell it to use both.
Acceptance tests using axe-core and PA11Y
PA11Y and axe-core can be easily integrated into acceptance tests. Because it uses it’s own browser you can run it with little config.
Again, make sure you pass in both HTML Code Sniffer and axe-core as runners. If you don’t pass in axe as a runner it will not use axe-core.
An example automated test using PA11Y and axe-core:
Acceptance tests using axe-core and Selenium
Axe-core needs to be injected into a browser, so it is great if you are already running Selenium as part of your acceptance tests.
If you’re not using Selenium, then it is probably easier to run axe-core with PA11Y as there is less configuration needed.
To run axe-core, pass your driver into the AxeBuilder and await the analysis.
Axe-core returns an object with 3 categories. Passed, incomplete and violations.
Passed is what the tool checked and found to be ok. Violations are what the tool found to be definite issues. Incomplete is when the tool could not reach a decision on whether it was ok or not.
To satisfy the test you should be looking for the number of violations to be 0. However you might want to log out any violations so you know what to fix. For issues in the incomplete category, the user must manually check them. So these are also worth console logging, but you would not want to fail your tests if you had any.
Axe-core uses the same engine as the Axe DevTools Chrome extension. So you can always re-run the tests using the highlight features of the extension to see exactly what the problem is if you get stuck.
An example automated test using Selenium, ChromeDriver and axe-core: