Add vagrant for development
Ignore all tmp files
Add an accessibility test case
have travis ci build and test accessibility
also test the accessibility-tests branch
Make sure nodejs is installed
install composer dependencies
Update apt-get before installing other tools

This should fix errors when installing apache2
Don't use sudo to install npm packages
Add a composer.json

Add libraries used during testing
Ignore the vendor directory
use the npm global bin path

This should fix problems on travis-ci.  running `pa11y` failed, because it for some reason, didn't know where pa11y was installed.  the bin path is something like: /home/travis/.nvm/v0.10.25/lib/node_modules/pa11y

 by using `npm bin -g` we will not be subject to problems when that patch changes (for example, a different version of nvm is installed, etc)
Install pa11y locally

for some reason, npm isn't avaiable via the cli at execution time on travis-ci.  Installing pa11y locally allows us to know the exact path to the pa11y executable.
Move the apache install/config to the install step
Don't install things that come pre-installed
Make pa11y work with #!/usr/bin/env node
try to avoid github api rate limits
debug
debug
symlink `node` to a directory in the include path