option for evaluating html fragments

[vegitron]

I'm interested in including an a11y check as part of our continuous integration checks, but on otherwise well-formed templates that aren't a complete document, I get these errors:

✖ The web page should have the content's human language indicated in the markup

html

✖ The web page should have a title that describes topic or purpose

html

While acknowledging that testing fragments of html isn't a complete solution, it would be helpful as a first pass on every commit. Ideally this would be exposed through the a11y command line option, so I could run something like:

a11y */.html --fragment-ok

[addyosmani]

I've been thinking about this for a while. One other possibility is that we allow you to have some sort of a11y config RC file where you can specify which options to relax and which ones to enforce more strictly. Something that would be adhered to by both the CLI and general module use. That said, we'll keep this open in case others think the fragment idea is useful.