nightwatch-axe-verbose

Verbose error reporting for axe accessibility rule violations to use in NightwatchJS

This fork of nightwatch-axe is more verbose in that it will report each passing rule run and how many elements it was run against. In addition, each rule failure will be counted individually against each failing element so downstream failures are not hidden.

Nightwatch.js custom commands for aXe allowing Nightwatch to be used as an automated accessibility testing tool.

Installation instructions

NOTE: If you are using Nightwatch 2.3.6 or greater this is now pre-included as a default plugin in the Nightwatch installation so you can skip this install section

1npm install nightwatch-axe-verbose --save-dev

Plugin Install (Recommended method for Nightwatch >= 2.0)

In nightwatch.conf.js add nightwatch-axe-verbose to the plugins property array.

nightwatch.conf.js

1{
2  // See https://nightwatchjs.org/guide/extending-nightwatch/adding-plugins.html
3  plugins: ['nightwatch-axe-verbose'];
4}

If you are using an older Nightwatch version or prefer the prior custom_commands_path option that will still work instead, but the path has changed from src/commands to nightwatch/commands as shown below. You must update the path or use the plugin pattern above starting with v2 of nightwatch-axe-verbose.

1"custom_commands_path": ["./node_modules/nightwatch-axe-verbose/nightwatch/commands"]

axeInject()

Injects the axe-core js library into your test page

axeRun(options)

Analyzes the current page against applied axe rules

Example test

AxeRun takes as a first parameter the selector of the element you want to run the axe test against. If you do it on a larger containing element such as the body all the inner elements will be scanned.

1module.exports = {
2    '@tags': ['accessibility'],
3    'ensure site is accessible': function (browser) {
4     browser
5            .url('https://dequeuniversity.com/demo/mars/')
6            .axeInject()
7            .axeRun('body', {
8                rules: {'color-contrast': { enabled: false }}
9            })
10            .end();
11    }

Example output

Passes

1√ Passed [ok]: aXe rule: aria-hidden-body (1 elements checked)
2√ Passed [ok]: aXe rule: color-contrast (62 elements checked)
3√ Passed [ok]: aXe rule: duplicate-id-aria (1 elements checked)

Failures

1× Failed [fail]: (aXe rule: button-name - Buttons must have discernible text
2        In element: .departure-date > .ui-datepicker-trigger:nth-child(4))
3
4× Failed [fail]: (aXe rule: color-contrast - Elements must have sufficient color contrast
5        In element: a[href="mars2\.html\?a\=be_bold"] > h3)
6

Default Run Settings

If no parameter inputs are supplied to .axeRun() it will default to the html context (scan all elements on the page) and run with all the default rule options from axe.

Global Configuration

axeRun can read the selector context and/or run options from the Nightwatch globals collection so that they don't need to be passed in during each test if you have a globally applicable customized non-default scanning preference. These settings are expected under axeSettings and can contain context and/or options properties containing axe-core context and option settings respectively.

If a selector context is passed in to axeRun by the test it will override, take precedence over, the global setting. Global option properties not supplied by the test will be merged together with the ones provides by the test. The test-supplied value will be used in the case of same-named properties.

1// nightwatch.conf.js
2test_settings: {
3    default: {
4        globals: {
5                axeSettings: {
6                        context: 'html',
7                }
8        }
9    }
10}

The above example sets these on the default global configuration. If you set these in the non-default test settings you can have multiple different axeSettings per environment configuration if you prefer.

Given this example global configuration one could expect the following.

Example 1

.axeRun() ➡️ Run against all page elements except for ones with or inside the .ad-banner class applied. Use all rules except color-contrast.

Example 2

.axeRun('body') ➡️ Run against all page elements contained inside the body element. Use all rules except color-contrast.

Example 3

1.axeRun('body', {
2        rules: {
3          'nested-interactive': {
4            enabled: false,
5          },
6          'select-name': {
7            enabled: true,
8          },
9        },
10})

➡️ Run against all page elements contained inside the body element. Use all rules except nested-interactive. Note, this overrides the global setting against color-contrast since both provide a value for rules and the one supplied from the test takes precedence.

Example 4

.axeRun('body', { otherValidAxeSetting: { something: true }}) ➡️ Run against all page elements contained inside the body element. Run with the rules settings supplied from the global configuration (disable color contrast), since the rules setting was not supplied by the test, and additionally include/use otherValidAxeSetting supplied by the test.