quailjs / quail-cli

The Quail command line interface

Deprecation

All projects have a useful lifespan. Quail was born during a time when accessibility testing, as a discipline, was maturing. There were numerous teams building solutions in parallel -- Quail was just one of these. In the end, we were all orbiting around the same general approach. Technology may have been a distinguishing factor a couple years ago, but even these advantages have largely dissolved as solutions have evolved and improved over time.

Given the realities of the market and the limited time that the Quail team can devote to this project, we are initializing deprecation for this project. Folks are welcome to fork it or volunteer to maintain it, but realistically, there are better options out there.

If you are looking for one, we recommend aXe: the Accessibility Engine by Deque Labs.

Quail Command Line Interface

quail-cli's Issues

phantom_evaluator: Unable to open file '/path/to/present working directory'

When I run $ quail eval http://placekitten.com, I expect to see evaluation results, but instead I get an error:

phantom_evaluator: Unable to open file '</path/to/present working directory>'

Cannot find phantomjs binary in project node_modules

When I install the cli via npm and run quail eval twitter.com, I expect to see some messages, but instead get an error:

Error: Cannot find module '/path/to/project/node_modules/phantomjs/bin/phantomjs' at Function.Module._resolveFilename (module.js:338:15)

It looks to me like the cli is looking for phantomjs to be a local dependency, but I'd expect it to use the global phantomjs binary (located in /usr/local/bin/phantomjs on OS X).