Detecting accessibility issues on CI with cypress-axe

Unless we check the accessibility of our pages every time we change them, it’s to easy to introduce regressions. Therefore, we should test accessibility during our Continuous Integration (CI) checks.

Cypress-axe allows us to do exactly that, and it’s a good place to do that in Cypress because we already render all the pages in our end-to-end tests and run them during CI.

#Setting up cypress-axe

Install cypress-axe (assuming we already have Cypress installed and configured on our project):

npm install --dev cypress-axe

Import the commands, add to the cypress/support/index.js:

import 'cypress-axe';

Update the plugins file, cypress/plugins/index.js:

module.exports = (on, config) => {
+  on('task', {
+    table(message) {
+      console.table(message);
+      return null;
+    },
+  });
  return config;
};

We need this for printing the results in the terminal.

Add a custom Cypress command, cypress/support/commands.js:

// Print cypress-axe violations to the terminal
function printAccessibilityViolations(violations) {
  cy.task(
    'table',
    violations.map(({ id, impact, description, nodes }) => ({
      impact,
      description: `${description} (${id})`,
      nodes: nodes.length
    }))
  );
}
 
Cypress.Commands.add(
  'checkAccessibility',
  {
    prevSubject: 'optional'
  },
  (subject, { skipFailures = false } = {}) => {
    cy.checkA11y(
      subject,
      null,
      printAccessibilityViolations,
      skipFailures
    );
  }
);

This command runs cypress-axe checkA11y method with a custom violation callback function that prints a list of violations to the terminal, and can be chained to queries.

#Running cypress-axe

To run accessibility checks, we need to do two things:

Inject Axe into the page — we need to do it once, after calling cy.visit.
Run the checks using our checkAccessibility command — we can do it multiple times to check the page in different states.

A test case could look like this:

describe('Our awesome site', () => {
  it('Happy path', () => {
    // Visiting the page to test
    cy.visit('http://localhost:8000');
 
    // Injecting Axe runtime into the page
    cy.injectAxe();
 
    // Waiting for the page to render
    cy.log('Page header is rendered');
    cy.findByRole('heading', { name: /awesome site/i }).should(
      'be.visible'
    );
 
    // Running accessibility checks
    cy.checkAccessibility();
 
    // All the regular end-to-end checks
    // ...
  });
});

If there are any accessibility violations, the test case fails:

And the list of violations is printed in the terminal:

Cypress-axe prints accessibility violations in the terminal

We could also check a particular area of the page, for example, a modal:

describe('Our awesome site', () => {
  it('Happy path', () => {
    // ...
 
    // Click a button that opens a modal
    cy.findByRole('button', { name: /open modal/i });
 
    // Check accessibility only inside the modal
    cy.findByTestId('some-modal').checkAccessibility();
  });
});

Hint cy.findByRole and cy.findByTestId are from Cypress Testing Library, read more about it in my article on Cypress.