accessibility-developer-tools | related testing and utility code | User Interface library

I stumbled in the answer in Specify browser location for wct-local test. It is different question (it is regard using gulp) but I noticed something different from my wct.conf.js which I gave a try and it in https://github.com/jimisdrpc/basic-vanilla-webcomponent now unit testing working with wct. What I changed was instead of

You must make sure that your button has a label and an attribute aria-labelledby indicating which element is the label.

You could use the span as label for your button:

Here is my best guess at what's going on:

1. You are launching with the selenium standalone server locally using your ip address and a port that is not 4444. This means that you did not select seleniumAddress: "http://localhost:4444/wd/hub" or directConnect: true. I'll have a code snippet below of what this looks like.

2. If you are launching locally and not on Travis, then Protractor launches by the Chrome browser by default. This also means that you should have downloaded the ChromeDriver.

3. You should upgrade from Protractor 2.5 to the latest. Protractor is strongly coupled with the entire stack: selenium-webdriver, the standalone server, browser drivers and browsers. If you are using an up-to-date browser and Protractor 2.5, then probably webdriver-manager downloaded old binaries that may be incompatible with your browser.

Here is the code snippet:

When the accessibility script is run (axs_testing.js), it checks if each element is visible by calling focus() on each element. The problem occurs when datepicker is focused (opens the dialog), then when a different element is focused on afterwards, the dialog doesn't close.

This is because it has no trigger to close when the field loses focus. If it did, the calendar would disappear as soon as you click on it as the focus would change away from the field and cause that trigger to occur.

A solution to this is to modify the accessibility script so that where it calls focus(), you add a check to see if it's trying to focus on the datepicker then (making sure it wasn't already focused) you close the datepicker dialog afterwards.