Shawn Allen

Specifically, 508 tests should cover everything in #578.

Testing 508 stuff with [pa11y](https://github.com/nature/pa11y) is going to be tricky. I tried adding a bare-bones `package.json` and installing pa11y and [PhantomJS](http://phantomjs.org/) as dependencies, but the latter fails because `node-gyp` isn't...

@adelevie yeah, I think that's what we want. Ideally we'd have it running at a URL like `pa11y.18f.us` and write some Python and Ruby bindings for the API.

Or, if we're assuming Travis, then the tests could just assume node and use [pa11y-webservice-client-node](https://github.com/nature/pa11y-webservice-client-node).

On hold while we mull over content tweaks.

For reference, we're discussing this very issue in 18F/web-design-standards#1698. We could combine efforts on this and use the USWDS as a proving ground for different approaches.

Bump! We've prototyped a USWDS scaffolding in the past; see [18F/generator-uswds](https://github.com/18F/generator-uswds). We're doing some [research](https://github.com/18F/18f-cli/projects/1) next to understand whether/how these projects will work together.

Yes! I've had lots of success with [webdriver.io], and I particularly like that it works with mocha's test APIs. It would be really awesome if we could find a way...

Hmmm... Now that I think about it, I'm not sure if that level of abstraction is possible. Browser tests usually involve lots of serial async actions over the Selenium protocol,...

+1 to @ultrasaurus's comment