I had a lofty goal: to get us down to zero test failures on the daily run of Accessibility module against Drupal 8 core.
I knew in my heart that this was an extremely unlikely goal to reach. We faced many obstacles including:
- A broken TestSwarm module for Drupal 8 that prevented our daily test from running.
- A inadequately documented set up process for the Accessibility module, the TestSwarm module and the Quail library.
- A well curated list of issues to work on.
I had hoped we would address these issues early on in the initiative. Because these blocking issues will keep us from making any progress, initiative or not.
Alas, participation in initiative in terms of development was low. There was some, but not enough to get us past the initial set of hurdles. I, personally, was not able to put in as much time as I would have liked.
So what do we do now? Well, we certainly can't cease our efforts to make Drupal more accessible. Indeed, much work to this end has been undertaken and committed to Core in the past two months.
But we must acknowledge that without an automated testing framework, we don't know how far we are from being conformant to guidelines. And we don't know when we introduce regressions to previously supported interactions. In short, we must continue to press ahead in the development of an automated accessibility tool.
Now, I was not completely idle or absent from this effort in the past two months. We (including Kevin Miller, the Quail developers and some outside organizations) are launching a project to improve the Quail library over the next 6 months. It has backing and momentum. I'll be posting an announcement to this group in the next couple days.
With each of these projects, I hope to continue to make it easier to contribute code. That means improving the build and setup tools and improving documentation. I want content experts to feel empowered to improve tests rather than spend time debugging the framework (although that type of involvement is also needed).
So, one ambitious initiative failed and over. Another ambitious initiative on the horizon. We must keep trying because the internet is not going to become more accessible unless we make it easy to build accessible tools and that means making Drupal and our testing tools better.