Web accessibility testing

Web accessibility testing is an early access feature and still under development. We can't guarantee full functionality in this or future versions.

Note that to use this early access feature, first you need to enable it.

Web accessibility testing, using Deque axe-core library (opens in new tab), verifies whether your application is easy to use for all users.

You need administrator rights before you can enable this early access feature. To enable accessibility testing, follow these steps:

  1. Open the ToscaCommander.exe.config located in C:\Program Files (x86)\TRICENTIS\Tosca Testsuite\ToscaCommander.

  2. Find the setting EnableAccessibilityColumn and set it to True.

  3. Save your change.

  4. Start or restart Tosca Commander.

    Before you start testing, make sure you meet the prerequisites.

Prerequisites

Before you start testing, follow these steps:

  1. Decide on which level you want to run your accessibility tests:

  1. Make sure you set the following test configuration parameters:

Note that your web accessibility tests only generate results if the Report Successful Execution of setting value differs from TestCases.

Enable and disable the web accessibility testing

To enable the web accessibility testing, add the TCP AccessibilityTesting and configure it according to the following values:

Value

Description

Disabled

To disable the Module Accessibility.

Note that if you don't create the TCP, the web accessibility testing is disabled by default.

AccessibilityModule

To enable the Module Accessibility and run web accessibility tests based on its ModuleAttributes.

EveryInput

To enable web accessibility tests for every TestStepValue that has ActionMode Input. If you set this value, the XBrowser Engine 3.0 generates web accessibility test results for all inputs, even without adding the Module Accessibility to your TestCase.

If you choose to test every input, note the following:

  • A longer ExecutionList may also lengthen your execution time.

Test the user accessibility of your web HTML application

To run web accessibility tests, make sure you meet the prerequisites and choose to either test every input, or use the Module Accessibility.

This Module is part of the standard subset. You can find it under Standard modules->TBox XEngines->Html.

The Module Accessibility doesn't support closed ShadowDOMs.

In this example, the XBrowser Engine 3.0 searches for the open browser window that has a Title starting with Tricentis, https://support-hub.tricentis.com/ as the URL, and a Window Index of 2.

Once it finds the correct browser window, the XBrowser Engine 3.0 runs an accessibility test on it.

Example - Accessibility

Web accessibility test results

Web accessibility testing is an early access feature and still under development. We can't guarantee full functionality in this or future versions.

Note that to use this early access feature, first you need to enable it.

Once you've run web accessibility tests on your HTML application, it's time to work with the results.

Check out the Accessibility column to view the amount of accessibility compliance issues detected, as well as their severity level.

In this example, you have two ExecutionEntries in your ExecutionList:

  1. You execute the ExecutionEntry Sample app 1 on every TestStepValue that has ActionMode Input.

    The execution of the TestCase is successful and returns you the following issues: 0 Critical, 0 Serious, 9 Moderate, and 0 Minor.

  2. You execute the ExecutionEntry Sample app 2 on the Module Accessibility level.

    The execution of the TestCase is successful and returns you the following issues: 0 Critical, 1 Serious, 8 Moderate, and 0 Minor.

In total, the ExecutionList reports the following type of issues:

  • 0 Critical

  • 1 Serious

  • 17 Moderate

  • 0 Minor

Example - Web accessibility test results