Skip to content

Accessibility Testing

What is Accessibility Testing?

Accessibility testing is a process of testing whether an application is easily accessible to people with disabilities such as visual, hearing, mobility, and cognitive impairment

To achieve this, developers and testers thoroughly evaluate the product against established accessibility standards and laws such as WCAG Compliance to solve any accessibility issues.

The objective of accessibility testing is to create an inclusive digital environment by removing any accessibility barriers.

How does INGenious perform Accessibility Tests?

The framework uses aXe as a library to test the accessibiity aspects of a website or specific elements. This feature comes packed into 2 simple actions having all the WCAG standards baked-in, thereby making execution very easy and report analysis easier.

However at any point in time we can include/exclude specific tags during the testing.

Actions

testAccessibility

Description: This function will generate the accessibility report for the entire web page based on the input parameters passed, Report name is mandatory under the input.

ObjectName Action Input Condition Reference
Browser 🟢 testAccessibility @ReportName
Browser 🟢 testAccessibility @ReportName @include tagName
Browser 🟢 testAccessibility @ReportName @exclude tagName
Browser 🟢 testAccessibility @ReportName @include tagName @exclude tagName
Browser 🟢 testAccessibility @ReportName @Options{}

Inputs in the Input column can be either hardcoded (in this case the data is preceded by a "@"), passed from the data sheet (datasheet name : column name) or passed from a variable value (%variable name%).

  axe.a11yCheck(arguments[0], %s, arguments[arguments.length - 1]);

testAccessibilityElement

Description: This function will generate the accessibility report for a particular web element based on the input parameters passed. The input parameters are optional. In case no input parameter is passed the report will be generated for all tags associated with the element, the default name for the report will be the name of the element.

ObjectName Action Input Condition Reference
WebObject 🟢 testAccessibilityElement @ReportName
WebObject 🟢 testAccessibilityElement @ReportName @Options{} 
axe.a11yCheck(arguments[0], %s, arguments[arguments.length - 1]);

Example

Here is an example of how to test the accessibility of all elements in a page.

  • In the framework, the command is as follows :

axe1

  • On running this, a report will be generated which will have the [axe] icon as shown below.

axe2

  • On clicking this [axe] icon, the Accessibility Test report will open up which will show all the Passes as below :

axe3

  • The report will also show all the Violations like this :

axe4

  • In the above example the Report failed as it had the following Violations as seen in the report :

    • aria-label attribute does not exist or is empty
    • aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty or not visible
    • Form element does not have an implicit (wrapped) <label>
    • Form element does not have an explicit <label>
    • Element has no title attribute or the title attribute is empty

  • The report also provides this link for reference, under the [More Info] section.