The Contrast advisor
Enabling users with visual impairments to access digital content is an urgent priority for many companies. The need to comply with legislation that mandates compliance with standards such as the Web Content Accessibility Guidelines (WCAG) prompts a key question: How can you accurately and efficiently test whether your content meets the guidelines?
The Applitools Contrast advisor functionality supports accessibility validation, focusing on the standards that define minimum contrast ratios for text and graphics:
- You can specify which level and version of the standard you want to use for a test.
- If the Contrast advisor is enabled, then during the course of a normal test run, Eyes automatically identifies the type of each element of a checkpoint (e.g. textual or graphical), measures the contrast ratio, and reports elements with contrast ratios that are below the minimum specified for that type of element.
- When the test is complete, you can easily view all checkpoints that have elements whose measured contrast ratio is below the minimum specified by the WCAG standard you chose.
- If required, you can override the automatic detection of element type and specify the element type explicitly or define that contrast ratios should not be tested for a given element or region.
This article has the following sections:
- Minimum text contrast ratio (WCAG 1.4.3 AA)
- Enhanced text contrast ratio (WCAG 1.4.6 AAA)
- Graphical objects contrast ratio (WCAG 1.4.11)
Validating contrast ratios differs from standard Eyes visual testing in that Eyes does not compare the checkpoint image to a reference baseline image that defines the expected results. Instead, Eyes identifies the various elements on the page and their type (e.g. graphics or text), measures the contrast ratio between the foreground and the background of these elements, and compares the contrast ratio to the minimum contrast ratio defined by WCAG for that type of element. If the measured contrast ratio of any part of an element is less than the minimum defined by WCAG, then a contrast ratio violation is flagged for that element. Both the range of measured contrast ratio values and the expected contrast ratio are displayed in the Step editor and Test editor.
The Eyes vision algorithm that measures the contrast ratio has a number of advantages over other DOM-based techniques:
- Only visible UI elements are reported. Elements that appear in the DOM but are not visible (and therefore do not need to conform to the standard) are not reported.
- The text contrast ratio is measured when text appears in an image as well as in HTML text.
- The contrast ratio is measured for icons.
- It is possible to test the contrast ratio of non-DOM content such as mobile applications.
The main steps to validate contrast ratio are outlined below. Click the links for full details:
- Enabling contrast ratio measurement: You enable contrast ratio validation for all checkpoints in an Eyes test by calling the SDK method
class$configuration$setaccessibilityvalidationwhen setting up the test. You pass this method the required accessibility level (AA or AAA) and version of the guidelines (WCAG_2_0 or WCAG_2_1) that you want.
- After the test has run, you can see the test results in the Test manager Test results page, and you can view the details and images of a particular step in the Step editor and Test editor.
- Filtering by contast ratio validation status: You can use the filter on the Test results page, applying the Accessibility criteria to choose which results you see - the options and tests and steps that passed, failed, or not validated.
- Viewing contrast ratio validation result status: You can see the contrast ratio validation results in the Accessibility status column in the Batch details view . The value displayed in this column tells you the contrast ratio validation results of each test. This status is independent of the visual test result status column, which indicates the status of the standard visual validation.
The Accessability status on a row will have a value of Passed if all steps passed the contrast ratio measurement and Failed if any steps failed. The column will be blank if contrast ratio was not tested.
- Viewing contast ratio validation status of a step: Steps that failed a contrast ratio measurement are flagged with the icon in the step thumbnail displayed in the various Test results page views. Hovering over the thumbnail displays the validation level used (AA or AAA).
- Viewing detailed checkpoint contrast ratio validation results:
Within the Step editor and Test editor, you can enable accessibility mode by clicking on the button in the tool bar. In this mode, there is only a checkpoint image pane.
Areas that fail to meet the minimum contrast ratio criteria are highlighted in red. For example, in the screenshot below, there are four highlighted areas:
Hover over any point in the checkpoint image to bring up a dialog box that displays the classification of the region, the passed or failed status, and the actual and expected contrast ratios:
In some cases, the actual contrast ratio is displayed as a range of values (e.g. 1.37 - 2.09) . This reflects the minimum and maximum ratios found between neighboring pixels in the element. The contrast ratio validation will fail if the measured minimum value is less than the required minimum (i.e. if any portion of the element did not meet the minimum contrast ratio requirements).
- Managing contrast classification regions with Test manager: In addition to the automatic element type classification done by Eyes, you can also explicitly define the classification of elements and regions to be, for example, Normal text or Graphics. You can also specify that the contrast ratio of a particular region or element should not be measured by Eyes. In these explicitly defined regions, Eyes uses the classification you provide and measures the contrast ratio accordingly, or ignores that region if that is what you specified. You can define such contrast classification regions within the test using the SDK method
class$checksettings$accessibility, or you can specify the regions in the Eyes Test Manager after a test run and Eyes takes them into consideration in future tests after you save to the baseline.
The sections below provides more details on the various Test manager and SDK tools that are available to help you achieve a smooth contrast ratio validation work-flow.
The Accessibility status column in the Batch details view contains a Passed indication if all the checkpoints in the test passed the contrast ratio validation. It contains a Failed indication if any checkpoint violated the contrast ratio limits. The column is empty if contrast ratio was not validated in the test run.
If the Accessibility status column is not visible in the test results table, click in the table header and then:
- Find and click on Accessibility status in the Hidden columns list on the left.
- Click on the move selected items to the right button .
- Click on the or buttons to place the column in the required position.
- Click on Apply.
You will now see the Accessibility status column in the test table.
You can use the Accessibility criteria of the filter test results tool to limit the steps displayed to those that have a status value selected from the following list:
- Not checked
By default, only steps that meet one of the selected filter values are displayed. If you select the Show entire tests checkbox in the filter dialog, then all the steps of a test are displayed if at least one step in the test meets the filter criteria.
You can view detailed contrast ratio validation results for a specific checkpoint in the Step editor or the Test editor. The diagram below shows a screenshot of the Test editor with key contrast ratio-related functionality annotated (not all failed areas are annotated).
In the figure you can see that all regions in which violations have been detected are shaded in red. The other accessibility related features are:
- Use this button in the toolbar to enable and disable accessibility mode. In accessibility mode, only the checkpoint image is visible, and the toolbar is populated with contrast ratio validation related tools.
- The contrast ratio violation icon is the most immediate indication that there are contrast ratio violations on the page. The icon appears in the editors and the step thumbnails.
- Click this button to highlight the contrast ratio area with an animation.
- Use these buttons to zoom into each failed element in turn. You can also use the shortcut keys , and . to move to the previous/next failure respectively.
- In the accessibility results summary you can see the accessibility level and version at which the test ran, as well as the number of violations found. If you have changed the level or version from within the Test manager (see next item) it also shows you what level and version are currently being displayed.
- Use the level and version buttons to rerun the contrast ratio measurement on the current step at the desired accessibility level or version. Selecting the level or version in this way allows a quick assessment of the contrast ratio measurements you can expect. The state of these buttons does not impact the test status or how the test is run in the future. See Enabling contrast ratio measurement to see how to set the accessibility level for the test.
- Use this button to add a contrast classificiation region. You can override the automatic element classification done by Eyes, or mark regions that should be ignored. Eyes will take these regions into account on subsequent test runs after you save the baseline . After you add a contrast classificiation region, Eyes immediately re-evaluates the contrast ratio of the current step using the currently selected accessibility level . However, this will not impact the results of the test. See Adding a contrast classificiation region using the editors for more information.
Viewing the test contrast ratio validation status
If you hover over any region that is shaded to indicate a violation, Eyes will display a dialog box with information about the contrast ratio measurement for that region. In the screenshots below you can see an example where the cursor is hovered over a text element that has passed and another example where the cursor is hovered over a graphic object element that has failed:
The dialog box displays:
- Classification: The classification of the element is defined automatically by Eyes or you define it explicitly using the SDK or the Test manager. Possible classifications are :
- Regular Text
- Large text
- Bold text (if defined explicitly)
- Graphical object
- Status: Whether the element Passed or Failed the contrast ratio validation.
- Actual contrast: The contrast ratio measured by Eyes. This may be provided as a single value or as a minimum - maximum range of values. A region will be flagged as Failed if any portion of the element has a contrast ratio less than the minimum acceptable contrast ratio (i.e. if the minimum value in the range is less than the acceptable contrast ratio).
- Expected contrast: The minimum acceptable contrast ratio at the current accessibility level. By default, the current accessibility level is the level used in the test. If you change the level using the or buttons in the tool bar, then the expected contrast ratio and the passed/failed status in the dialog box will reflect the change, although the step and test accessibility status will not be affected.
Eyes Test Manager provides operations that allow you to manage the classification of elements in a given region. Each of these is described in more detail in the following sections:
You can add a new contrast classificiation region in the Step Editor and Test Editor when in accessibility mode, as follows:
- Click on the tool.
- Mark a rectangular region using the cursor.
- In the menu, choose how the region should be classified:
- Regular text
- Large text
- Bold text
- Graphical object
- If you want this region to be applied to similar checkpoints using Automated test maintenance, click on Apply to other steps in scope. Otherwise, click outside the dialog to close it and create the region.
Eyes re-evaluates the contrast ratio of the checkpoint, taking into account the newly defined region to provide immediate feedback. However, this does not affect the accessibility status of the current step or test.
Once you have saved the baseline, on subsequent runs, Eyes first classifies regions based on all explicit classification you have provided, and then automatically classifies any other parts of the image.
Note that you can also add contrast classificiation regions using the SDK as described below in the Adding an contrast classificiation region with the SDK section. The advantage of using the Eyes Test Manager is that you can see the rectangular region that you are marking, whereas the advantage of using the SDK is that you can specify a particular element using a selector which remains well defined even if that element changes size or position.
Viewing contrast classification regions
You can add contrast classification regions to a checkpoint in the Step editor or Test editor as described in Adding a contrast classificiation region using the editors, or in the SDK as described in Adding an contrast classificiation region with the SDK. You can view regions of either type in the Step editor or Test editor. As you can see in the screenshot below, the regions are marked differently in order to distinguish between them:
Selecting what contrast ratio information to view
You can select the elements you see on the checkpoint image by clicking on the layers menu .
The available options are:
- Violations: Regions that failed the contrast ratio validation.
- Remarks & issues: Regions that were annotated by a user using the or tools.
- Baseline regions: Regions that were added by a user in the Step editor or Test editor.
- Code regions: Regions that were added by a user using the SDK.
- Viewport: The bounding rectangle of the viewport.
Changing contrast classification regions
If you click on a contrast classificiation region added to the baseline, then you can adjust the bounding rectangle, change the classification, or delete the region. If you click a code region, you will see the basic information about the region (i.e. the bounding rectangle and the region classification that was set), but to change these values you need to make the necessary changes in the code where it was defined.
To delete a contrast classificiation region added to the baseline:
- Click on the region you want to delete.
- Click on .
- Eyes then opens a dialog box that asks if you want to apply Automated test maintenance. Click No to delete only the current region and Delete in Scope to apply Auto maintenance.
You cannot delete regions added using the SDK using the Eyes Test Manager - you need to make the necessary changes in the code where it was defined.
To copy a contrast classificiation region created using Test manager to another step:
- Click on the region you want to copy.
- Click on or do a Cntrl/Command C.
- You can now do a Cntrl/Command V on a different step and an identical region will be created at the same position in that step.
You cannot copy regions added using the SDK using the Eyes Test Manager.
The following snippet shows how contrast ratio validation is enabled, and the accessibility level and version are set using the
class$configuration$setaccessibilityvalidation method. The level and version you set using this method applies for all checkpoints in the test and cannot be changed for a specific checkpoint.
The following snippet shows how the
class$eyes$check fluent interface
checksettings$accessibility method can be used in various ways to define manual contrast classification regions. When a region is defined explicitly, either in the SDK, as shown here, or by Adding a contrast classificiation region using the editors, Eyes will not try to classify the pixels in the region, and will evaluate the acceptability of that region based on the classification type that you specified.
Using the SDK to retrieve contrast ratio validation results
You can use the SDK to retrieve the overall results of the contrast ratio validation results validation. The example below shows how to use the
class$testresults$getaccessibilitystatus$morp method to retrieve the pass/fail status of each test run in the current Runner session.