TROUBLESHOOTING.md

Troubleshooting

Common Issues

AngularJS

If you're testing against an AngularJS app, you may have trouble testing against the correct page when you make use of ngView to render templates. We recommend using actions to wait until a particular URL fragment has loaded, or for an element to become available on the page.

You could also use a timeout to give your view time to load, but this is unreliable.

Why does Pa11y give different results to the HTML_CodeSniffer bookmarklet?

Pa11y uses Headless Chrome as a web browser to load the DOM content and can only analyze what is provided.

If parts of the DOM are been loaded after the document is first generated, you may get results that differ from the bookmarklet which runs in the browser and can test against the complete DOM.

If you use Pa11y and HTML_CodeSniffer CLI you will find that you get the same results, which will both differ from the bookmarklet, a similar issue was highlighted by HTML_CodeSniffer.

Why does Pa11y give different results each time it runs?

This could be a number of things, but indicates that the content of your page changes in some way on each load. If you include advertising on your page then you can expect to see differing results, and sometimes your JavaScript may not have had time to execute before the Pa11y test runs.

To debug this, you can use the --screen-capture flag or screenCapture option and compare the output for the differing test runs.

Pa11y ignores the contents of iframes

Pa11y doesn't currently support testing against iframe content from a parent page context. Any page that makes use of iframes, e.g. for displaying ads, may show different error, warning, and notice counts in Pa11y compared to the HTML_CodeSniffer browser bookmarklet.

If you do need to test the contents of an iframe, run Pa11y against the iframe source URL directly.

Common Questions

Common questions about Pa11y are answered here.

How do I set cookies on a tested page?

Use the headers option either in your JS code or in your config file:

pa11y('http://example.com', {
    headers: {
        Cookie: 'foo=bar'
    }
});

How can Pa11y log in if my site's behind basic auth?

You can authenticate using basic auth by sending additional headers to Pa11y. This works with the JavaScript API, or on the command line by using a config file:

const credentials = 'exampleuser:supersecretpassword';
const encodedCredentials = new Buffer(credentials).toString('base64');

pa11y('http://example.com', {
    headers: {
        Authorization: `Basic ${encodedCredentials}`
    }
});

How can Pa11y log in if my site has a log in form?

Use the actions option to specify a series of actions to execute before Pa11y runs the tests:

pa11y('http://example.com', {
    actions: [
        'set field #username to exampleUser',
        'set field #password to password1234',
        'click element #submit',
        'wait for path to be /myaccount'
    ]
});

How can I use Pa11y with a proxy server?

Proxy configuration can be passed through from Pa11y to Headless Chrome using the args propery of chromeLaunchConfig option;

pa11y('http://example.com', {
    chromeLaunchConfig: {
        args: [
            '--proxy-server=127.0.0.1:9999',
        ]
    }
});

How can I simulate a user interaction before running Pa11y?

We recommend using actions (if the existing actions don't meet your needs, please let us know).

Does Pa11y test the contrast of link hover states?

Pa11y doesn't check the hover state. Instead, you must test the contrast of the hover state for links manually.

Check to see if the issue has been reported

Check the issue tracker for similar issues.

Create an issue

If all else fails, create an issue and we'll help you.

Please include your Node.js and Pa11y version numbers, as well as your operating system. It may be useful to run pa11y --environment – this outputs all the details we need to know about your machine to help us debug your issue.