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

[ckundo]

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>'

[kahunacohen]

HI any word on this? When I do the same I get:

$ ./bin/quail eval http://www.google.com
WORKING_DIR/node_modules/.bin/phantomjs WORKING_DIR/src/js/scripts/phantom_evaluator.js  WORKING_DIR/home/cohenaa/projects/quail/config/config.json 
Unable to open file 'undefined'

I followed build instructions as per the README.

[alefort]

I'm also getting the same errors as kahunacohen.

[WilcoFiers]

Hey guys,
QuailJS is no longer being maintained, and neither is PhantomJS for that matter. I recommend you looking for alternatives. As a possible alternative I would suggest axe-cli, which I am one of the developers of. There are other options out there too. The W3C maintains a list of different accessibility tools out there:

https://www.w3.org/WAI/ER/tools/

[alefort]

Thanks for the update, I hadn't noticed it was deprecated. I'll focus on using aXe-cli.

[kahunacohen]

@WilcoFiers can you tell me if axe-cli allows you to write your own custom tests?

[WilcoFiers]

@kahunacohen Currently not. There's a problem with the --axe-source flag. Once that's fixed you can load in a custom build of axe-core. What are some of the things you are missing? I'd recommend looking at contributing to axe-core if you're looking to expand the existing ruleset. There's some information about this here: https://github.com/dequelabs/axe-core/blob/develop/doc/rule-proposal.md