Pa11y is an automated accessibility testing tool that helps developers ensure their web applications meet accessibility standards. It can be used to run accessibility tests on web pages and generate reports on any issues found.
Run Accessibility Tests
This feature allows you to run accessibility tests on a given URL. The results will include any accessibility issues found on the page.
const pa11y = require('pa11y');
(async () => {
const results = await pa11y('https://example.com');
console.log(results);
})();Custom Configuration
Pa11y allows you to customize the accessibility tests by specifying standards (like WCAG2AA) and other options such as taking a screenshot of the page.
const pa11y = require('pa11y');
(async () => {
const results = await pa11y('https://example.com', {
standard: 'WCAG2AA',
screenCapture: './screenshot.png'
});
console.log(results);
})();Programmatic API
You can use Pa11y's programmatic API to perform actions on the page before running the accessibility tests. This is useful for testing dynamic content.
const pa11y = require('pa11y');
(async () => {
const results = await pa11y('https://example.com', {
actions: [
'click element #button',
'wait for element #result to be visible'
]
});
console.log(results);
})();Axe-core is a popular accessibility testing engine for websites and other HTML-based user interfaces. It provides a comprehensive set of rules for accessibility testing and can be integrated into various testing frameworks. Compared to Pa11y, axe-core is more focused on providing a robust rule set and is often used as a library within other tools.
Accessibility Insights for Web is a tool that helps developers find and fix accessibility issues in web applications. It provides a browser extension and a CLI for automated testing. Compared to Pa11y, Accessibility Insights offers a more user-friendly interface and additional guidance on fixing issues.
Cypress-axe is a plugin for the Cypress end-to-end testing framework that integrates axe-core for accessibility testing. It allows you to run accessibility checks as part of your Cypress test suite. Compared to Pa11y, cypress-axe is more suitable for developers already using Cypress for their testing needs.
pa11y is your automated accessibility testing pal. It runs HTML CodeSniffer from the command line for programmatic accessibility reporting.
pa11y nature.com
var pa11y = require('pa11y');
pa11y(options, function (error, test, exit) {
test('nature.com', function (error, results) {
/* ... */
});
});
pa11y requires Node.js 0.10+ and PhantomJS to run.
On a Mac, you can install these with Homebrew:
$ brew install node
$ brew install phantomjs
If you're on Linux, you'll probably be able to work it out.
Windows users approach with caution – we've been able to get pa11y running (Windows 7, Node 0.10) but only after installing Visual Studio and the Windows SDK (as well as Git, Python and PhantomJS). The Windows installation instructions for node-gyp are a good place to start.
Install pa11y globally with npm:
npm install -g pa11y
This installs the pa11y command-line tool:
Usage: pa11y [options] <url>
Options:
-h, --help output usage information
-V, --version output the version number
-s, --standard <name> the accessibility standard to use: Section508, WCAG2A, WCAG2AA (default), WCAG2AAA
-r, --reporter <reporter> the reporter to use: cli (default), csv, html, json
-l, --level <level> the level of message to fail on (exit with code 2): error, warning, notice
-i, --ignore <ignore> types and codes of messages to ignore separated by semi-colons
-c, --config <path> a JSON config file
-p, --port <port> the port to run PhantomJS on
-t, --timeout <ms> the timeout in milliseconds
-d, --debug output debug messages
Run an accessibility test against a URL:
pa11y nature.com
Run a test with CSV reporting and save to a file:
pa11y --reporter csv nature.com > report.csv
Run pa11y with the Section508 ruleset:
pa11y --standard Section508 nature.com
The command-line tool uses the following exit codes:
0: pa11y ran successfully, and there are no errors1: pa11y failed run due to a technical fault2: pa11y ran successfully but there are errors in the pageBy default, only accessibility issues with a type of error will exit with a code of 2. This is configurable with the --level flag which can be set to one of the following:
error: exit with a code of 2 on errors only, exit with a code of 0 on warnings and noticeswarning: exit with a code of 2 on errors and warnings, exit with a code of 0 on noticesnotice: exit with a code of 2 on errors, warnings, and noticesnone: always exit with a code of 0The command-line tool can be configured with a JSON file as well as arguments. By default it will look for a pa11y.json file in the current directory, but you can change this with the --config flag:
pa11y --config ./path/to/config.json nature.com
For more information on configuring pa11y, see the configuration documentation.
The command-line tool can report test results in a few different ways using the --reporter flag. The built-in reporters are:
cli: output test results in a human-readable formatcsv: output test results as comma-separated valueshtml: output test results as an HTML documentjson: output test results as a JSON arrayYou can also write and publish your own reporters. Pa11y looks for reporters in the core library, your node_modules folder (with a naming pattern), and the current working directory. The first reporter found will be loaded. So with this command:
pa11y --reporter rainbows nature.com
The following locations will be checked:
<pa11y-core>/reporter/rainbows
<cwd>/node_modules/pa11y-reporter-rainbows
<cwd>/rainbows
A pa11y reporter should export the following methods:
begin(url); // Called when pa11y starts
error(message); // Called when a technical error is reported
debug(message); // Called when a debug message is reported
info(message); // Called when an information message is reported
results(resultsArray, url); // Called with the results of a test run
You may find the following reporters useful:
1.0-json: output test results in the pa11y 1.0 JSON formatInstall pa11y with npm or add to your package.json:
npm install pa11y
Require pa11y:
var pa11y = require('pa11y');
Create a test function by initialising pa11y with some options:
pa11y(options, function (error, test, exit) { /* ... */ });
Within your callback, you can use the test and exit functions to run accessibility tests against web pages or exit PhantomJS:
pa11y(options, function (error, test, exit) {
// Run a test on nature.com
test('http://www.nature.com/', function (error, results) {
// ...
});
});
pa11y(options, function (error, test, exit) {
// Exit PhantomJS
exit();
});
The results that get passed into your test callback come from HTML CodeSniffer, and look like this:
[
{
code: 'WCAG2AA.Principle1.Guideline1_1.1_1_1.H30.2',
context: '<a href="http://example.com/"><img src="example.jpg" alt=""/></a>',
message: 'Img element is the only content of the link, but is missing alt text. The alt text should describe the purpose of the link.',
type: 'error',
typeCode: 1
},
{
code: 'WCAG2AA.Principle1.Guideline1_3.1_3_1.H49.B',
context: '<b>Hello World!</b>',
message: 'Semantic markup should be used to mark emphasised or special text so that it can be programmatically determined.',
type: 'warning',
typeCode: 2
},
{
code: 'WCAG2AA.Principle2.Guideline2_4.2_4_4.H77,H78,H79,H80,H81',
context: '<a href="http://example.com/">Hello World!</a>',
message: 'Check that the link text combined with programmatically determined link context identifies the purpose of the link.',
type: 'notice',
typeCode: 3
}
]
ignore (array)An array of result codes and types that you'd like to ignore. You can find the codes for each rule in the console output and the types are error, warning, and notice.
pa11y({
ignore: [
'notice',
'WCAG2AA.Principle3.Guideline3_1.3_1_1.H57.2'
]
});
Defaults to an empty array.
log (object)An object which implements the methods debug, error, and info which will be used to report errors and test information.
pa11y({
log: {
debug: console.log.bind(console),
error: console.error.bind(console),
info: console.info.bind(console)
}
});
Each of these defaults to an empty function.
page.headers (object)A key-value map of request headers to send when testing a web page.
pa11y({
page: {
headers: {
Cookie: 'foo=bar'
}
}
});
Defaults to an empty object.
page.settings (object)A key-value map of settings to add to the PhantomJS page. For a full list of available settings, see the PhantomJS page settings documentation.
pa11y({
page: {
settings: {
loadImages: false,
userName: 'nature',
password: 'say the magic word'
}
}
});
Defaults to:
{
userAgent: 'pa11y/<version> (truffler/<version>)'
}
page.viewport (object)The viewport width and height in pixels. The viewport object must have both width and height properties.
pa11y({
page: {
viewport: {
width: 320,
height: 480
}
}
});
Defaults to:
{
width: 1024,
height: 768
}
phantom (object)A key-value map of settings to initialise PhantomJS with. This is passed directly into the phantom module – documentation can be found here. You can pass PhantomJS command-line parameters in the phantom.parameters option as key-value pairs.
pa11y({
phantom: {
port: 1234,
parameters: {
'ignore-ssl-errors': 'false',
'ssl-protocol': 'tlsv1'
}
}
});
Defaults to:
{
parameters: {
'ignore-ssl-errors': 'true'
},
port: 12300
}
standard (string)The accessibility standard to use when testing pages. This should be one of Section508, WCAG2A, WCAG2AA, or WCAG2AAA.
pa11y({
standard: 'Section508'
});
Defaults to WCAG2AA.
timeout (number)The time in milliseconds that a test should be allowed to run before calling back with a timeout error.
pa11y({
timeout: 500
});
Defaults to 30000.
Run pa11y on a URL and output the results:
node example/basic
Use async to run pa11y on multiple URLs in series, and output the results:
node example/multiple
Common questions about pa11y are answered here.
Use the page.headers option either in your JS code or in your JSON config file:
pa11y({
page: {
headers: {
Cookie: 'foo=bar'
}
}
});
Use the page.settings option either in your JS code or in your JSON config file to set a username and password:
pa11y({
page: {
settings: {
userName: 'nature',
password: 'say the magic word'
}
}
});
To contribute to pa11y, clone this repo locally and commit your code on a separate branch.
Please write unit tests for your code, and check that everything works by running the following before opening a pull-request:
make lint test
We use JavaScript Code Style to ensure pa11y's source code is clean and consistent. You can check your work against our rules by running:
make jscs-check
If you're using pa11y 1.0 and wish to migrate to 2.0, we've written a Migration Guide to help with that.
It's recommended that you migrate to 2.0 as soon as possible, but 1.0 is still available on the 1.x branch. We'll be providing support for 1.0 for the forseeable future, but there will be no new feature development.
Copyright 2013 Nature Publishing Group.
pa11y is licensed under the GNU General Public License 3.0.
2.0.0 (2015-06-08)
FAQs
Pa11y is your automated accessibility testing pal
The npm package pa11y receives a total of 125,075 weekly downloads. As such, pa11y popularity was classified as popular.
We found that pa11y demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 9 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
A malicious npm package disguised as a WhatsApp client is exploiting authentication flows with a remote kill switch to exfiltrate data and destroy files.
Security News
PyPI now supports digital attestations, enhancing security and trust by allowing package maintainers to verify the authenticity of Python packages.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.