Automatically detect accessibility regressions

Accessibility

Accessibility

Accessibility

Your guide to automated accessibility regression testing.

Accessibility Testing is one of the most commonly overlooked areas of automation testing.


In this, we'll examine accessibility testing, why it's so important, and how to add lighthouse & pa11y tests to your automation pack.

What is Accessibility Testing?

What is Accessibility Testing?

What is Accessibility Testing?

Accessibility testing detects issues that could limit the experience of some users.


It is illegal to discriminate against people with disabilities online. Accessibility testing will ensure compliance and protect against accidental regression.

Why do Accessibility Testing?

Why do Accessibility Testing?

Why do Accessibility Testing?

Accessibility testing will protect you and help you deliver a better experience for all.


A beautiful side-effect of improving your accessibility is you'll very likely be also improving your SEO.

Pa11y AA Conformance

The Pa11y Node will provide you with an unparalleled insight into your conformance level and will highlight the areas you need to focus on.

Accessibility score is greater than 85

Accessibility score is greater than 85

Google's Lighthouse Accessibility score is great way to monitor your overall accessibility health and is best for protecting against slow regressions.

How to create an Accessibility test

How to create an Accessibility test

Create a new flow in DoesQA
Create a new flow in DoesQA
Create a new flow in DoesQA

Step 1:
Create New Flow

Step 1:
Create New Flow

If you don't have an account yet, create one and come back. From the Flows view click the plus button to create a new Flow.

Tip: For an accessibility test turn off "Stop on first fail".

Step 2:
Configure Open Node

Step 2:
Configure Open Node

New flows start with an Open Node, double-click this to open the edit modal and enter the site you wish to test.

Note: Lighthouse testing will be skipped on FireFox & Edge.

Configure open node in DoesQA
Configure open node in DoesQA
Configure open node in DoesQA
Inserting accessibility nodes in DoesQA
Inserting accessibility nodes in DoesQA

Step 3:
Insert & Connect Accessibility Nodes

Step 3:
Insert & Connect Accessibility Nodes

Locate the Validators from the Node Library on the left. Drag in the Accessibility & Pa11y Nodes into your Flow and connect it to the Open Node.

Step 4:
Configure Nodes

Step 4:
Configure Nodes

Double-click the Acessibility Node to configure the minium allowed value.

The Pa11y Node has a default of AA conformance double-click this Node if you wish to change the level to A or AAA.

Configure Google Lighthouse Node in DoesQA
Configure Google Lighthouse Node in DoesQA
Configure Google Lighthouse Node in DoesQA

Running your Accessibility test

Running your Accessibility test

Running your Accessibility test

Running this simple test will highlight any accessibility issues you have. Make sure to take time to investigate each item uncovered by the Pa11y Node in your test results.

Extending your Accessibility test

Extending your Accessibility test

Accessibility Validations across multiple viewports sizes and devices
Accessibility Validations across multiple viewports sizes and devices
Accessibility Validations across multiple viewports sizes and devices

To perform accessibility check on different viewport breakpoints and emulated devices, we would add multiple Open Nodes.

Accessibility validations on mutliple pages
Accessibility validations on mutliple pages
Accessibility validations on mutliple pages

To perform the accessibility validations on different pages, we can insert Browser Go To Nodes.

Accessibility Checks after login
Accessibility Checks after login
Accessibility Checks after login

To check accessibility after login, we can insert Action Nodes before the Validator Nodes.

Give codeless a go!

"We would never go back!"

Start your no-code automation testing journey now and have more confidence in just a few minutes. Test packs aren't meant to be finished but do need to be started!

Give codeless a go!

"We would never go back!"

Start your no-code automation testing journey now and have more confidence in just a few minutes. Test packs aren't meant to be finished but do need to be started!